[2.0.66] Crash MilitaryTarget registered in wrong chunk after Transport Drones removal
Posted: Sat Dec 06, 2025 6:28 pm
Sorry for the below- I've been having ChatGPT guide me through how to determine the problem and fix the longest save I've ever worked on:
This save crashes at engine level during Map::checkConsistency with an invalid MilitaryTarget registration.
A small-biter is physically in chunk [65,114] but registered on chunk [0,-1].
Behavior:
- With Transport Drones enabled: the map loads, but destroying enemies or loading the affected area crashes.
- With Transport Drones disabled: the game crashes immediately during “checking consistency.”
- Teleporting near ~{2080,3648} and moving east reliably triggers the crash.
This is a hard C++ assert in MilitaryTarget::unregisterOnChunk / Unit::onDestroy.
No Lua error is involved.
Save, log, crash dump, and mods are attached.
My goal is simply to eliminate Transport Drones and continue.
For space considerations, I deleted some inactive mods like krastorio.
Thank you!
This save crashes at engine level during Map::checkConsistency with an invalid MilitaryTarget registration.
A small-biter is physically in chunk [65,114] but registered on chunk [0,-1].
Behavior:
- With Transport Drones enabled: the map loads, but destroying enemies or loading the affected area crashes.
- With Transport Drones disabled: the game crashes immediately during “checking consistency.”
- Teleporting near ~{2080,3648} and moving east reliably triggers the crash.
This is a hard C++ assert in MilitaryTarget::unregisterOnChunk / Unit::onDestroy.
No Lua error is involved.
Save, log, crash dump, and mods are attached.
My goal is simply to eliminate Transport Drones and continue.
For space considerations, I deleted some inactive mods like krastorio.
Thank you!