Fixes not all escape pods arriving to escape pod shuttle at round end #11566
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.
About The Pull Request
a new escape pod shuttle was introduced with #11150, however the ids of the escape pod docks in it were not tweaked to match those of their respective escape pods (had
pod_2_away
instead ofpod2_away
for example); this PR changes just thatthis caused multiple identical runtimes (
Runtime in docking.dm,4: Cannot read null.docked
) becausenew_dock
argument would be null (fromSSshuttle.getDock("pod2_away")
which could not find said dock and returned null), and these should now be solvedWhy It's Good For The Game
allows more than one escape pod to make it to escape pod shuttle (and probably counts towards escape objective)
fixes #11374
Testing Photographs and Procedure
Screenshots&Videos
tested on Meta Station with 3 escape pods
Changelog
🆑 Aramix
fix: all escape pods should now properly arrive to the escape pod shuttle at end of round
/:cl: