-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crew can leave with an active resonance cascade #5790
Comments
I mean you hacked it?, sounds like sabotage and not nonsense, its like hacking through a door and releasing a virus. The door was supposed to stop the virus, but you hacked it defeats the purpose of the door, but should. not a bug will ask for a second opinion |
Looking at code holy shit done in the worst way possible, this is 100% not intended can be fixed with a single registerHostileEnvironment instead of the shit SM stop shuttle proc. However question is do we count it a feature because I see no issue literally hacking it. |
the Portals it open also exist, gonna get feedback from admins, calling this a feature if no else |
wait, what exactly happened? is ripperpond on github? |
Actually, think I now understand it. Holy hell I can't read. |
Reporting client info: Client Information:
BYOND:515.1647
Key:ripperpond
Round ID:
9756
Testmerges:
Reproduction:
the crew is allowed to leave when there is a cascade if you use a emag witch i nonsense and defeats the purpouse
The text was updated successfully, but these errors were encountered: