Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mirrored on Nova: NovaSector/NovaSector#1884
Original PR: tgstation/tgstation#82415
About The Pull Request
If the occupant of a mech has their mob changed -- mutation, polymorph, admin fuckery -- or if a mob somehow enters a mech without becoming an occupant -- the above, or a chestburster in said mech pilot -- then they don't get added to the occupants, only the contents. All contents are hard-deleted if a mech is destroyed. This fixes that, and ejects any mobs inside mechs who are technically inside the mech but not an occupant.
Why It's Good For The Game
Fixes #82395 and any similar case
Changelog
Being inside a mech when it's destroyed should no longer delete you, even if you ended up in that mech in an odd way.
🆑 Bisar
fix: Mechs will no longer delete their living non-occupant contents when destroyed.
/:cl: