Admin-spawned ERTs don't spawn after the Almayer has crashed into the planet

[cm13-issue-bot]

Testmerges

#12174: 'Yautja Armor Sets' by realforest2001 at commit 90c66798ed
#11698: 'SHARP Resharpening: Design Improvements' by MPhonks at commit ecd26ee406
#12480: 'Sneaky Hijack Edgecase + Transmute Fixes' by Drulikar at commit d76bf3732d
#12519: 'Revert turf signal preservation + open_space tweaks' by Drulikar at commit 6d6bd7f31f
#12542: 'Xeno defensive grab' by Drulikar at commit c23567b747
#12585: 'stops traps going under jungle bushes' by realforest2001 at commit cf176673f7
#12573: 'Opensearch query builder' by fira at commit b9777a1272
#12626: 'Refurbished Combat Information Centre (2) - USS Almayer' by Steelpoint at commit f8b8a4e0dd
#12627: 'Tyrargo Rift (2) - Various Alterations' by Steelpoint at commit bbe6ae5efc
#12464: 'LV1021: Operation Falcon's Fury - Ground Map' by Steelpoint at commit 5f5536b583
#12646: 'Fix: Not being able to immediately retract open a broken chest/head' by MistChristmas at commit df6b917372

Round ID

35291

Description of the bug

Admin-spawned ERTs wont spawn mobs on their shuttle or at current location after the Almayer crashes.

What's the difference with what should have happened?

ERTs should spawn

How do we reproduce this bug?

Crash the Almayer
Spawn in an ERT via Distress Beacons verb
Watch the mobs not spawn

Attached logs

N/A

Additional details

• Author: novacypher
• Admin: the novacypher
• Note: None

[MistChristmas]

The only real issues I have with the Distress Beacons at the moment is that they fire off before they check if they even can initially. And they lack feedback saying it was cancelled because it can't spawn during ftl or crash.