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
I confirm this issue is not an exploit. (Required)
BYOND Version
515.1647
Issue Description
I am unable to get an exosuit out of maintenance protocols. I am following the correct procedure: swiping my ID card and selecting "Initiate/stop maintenance protocol" on the mech UI, but it has no effect while in maintenance protocol.
What did you expect to happen?
I expected the exosuit to exit maintenance protocol and be useable as normal.
What happened instead?
The exosuit remains in maintenance protocols, and cannot move or use modules.
Why is this bad/What are the consequences?
Exosuits are made to be used.
Steps to reproduce the issue.
Build an exosuit
Swipe an ID card over it
Select "Initiate maintenance protocol"
Select "Initiate/stop maintenance protocl"
When did the problem start happening?
This has been a constant issue over the 3 months I've been playing on Paradise.
Extra information
No response
Relevant log output/runtime error
The text was updated successfully, but these errors were encountered:
Exploit Reports
BYOND Version
515.1647
Issue Description
I am unable to get an exosuit out of maintenance protocols. I am following the correct procedure: swiping my ID card and selecting "Initiate/stop maintenance protocol" on the mech UI, but it has no effect while in maintenance protocol.
What did you expect to happen?
I expected the exosuit to exit maintenance protocol and be useable as normal.
What happened instead?
The exosuit remains in maintenance protocols, and cannot move or use modules.
Why is this bad/What are the consequences?
Exosuits are made to be used.
Steps to reproduce the issue.
When did the problem start happening?
This has been a constant issue over the 3 months I've been playing on Paradise.
Extra information
No response
Relevant log output/runtime error
The text was updated successfully, but these errors were encountered: