You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you're connecting a logic item (buttons, gates, et cetera.) to an airlock, then the access is denied. However, if you connect an airlock to a logic item, the ui pops up, but you cannot do logic on the airlock.
Reproduction
Both require engineering IDs to work (recommended is chief engineer ID).
Connect a logic item (buttons, gates, et cetera.) to an airlock.
Connect an airlock to a logic item and try to do some logic on them.
Expected behavior
Connecting a logic item (buttons, gates, et cetera.) to an airlock will result in an "Access Denied" message.
Connecting an airlock to a logic item and trying to do some logic on them will result in an "DoorStatus refused the connection!" message.
Additional context
I suspect it has something to do with ID or the resolution requires a wizden cherry-pick, because doing the same on a wizden codebase does not result in this error.
The text was updated successfully, but these errors were encountered:
Description
If you're connecting a logic item (buttons, gates, et cetera.) to an airlock, then the access is denied. However, if you connect an airlock to a logic item, the ui pops up, but you cannot do logic on the airlock.
Reproduction
Both require engineering IDs to work (recommended is chief engineer ID).
Expected behavior
Additional context
I suspect it has something to do with ID or the resolution requires a wizden cherry-pick, because doing the same on a wizden codebase does not result in this error.
The text was updated successfully, but these errors were encountered: