[bug] Creeps crash sometimes and don't recover.
Closed this issue · 10 comments
I've observed a creep crashing multiple times. No error's visible in the console, yet the creep stops doing his job and never recovers. It solves itself when the creep dies, but that's not the expected behavior.
Types i observed this with is: Miner & Hauler. In the miners case it was stuck on top of a container and stayed there, blocking other miners. In the case of the haulers (multiple), they were waiting next to a fully filled spawn, but not continued doing anything after the spawn was empty.
Currently imagining a creep driving a car and crashing, then recovering in the hospital.
Was this after an upgrade? We changed the cluster naming scheme recently, so if you upgraded to the new scheme all the existing creeps before the upgrade would no longer be controlled.
I have setup auto deploy after PR #144, if that merge happened after that, it might be the case.
Just witnessed it again, it seems the program stops running at some point, in this case it was a starting room and the fillers stopped. Which automatically means the end of the room, unless the spawn fills up over time and it spawns a filler. Which it should do, but this is a loss of 1000+ ticks.
Has this come up again?
Experienced it again on my 3 rooms, all creeps stopped working only new made ones work
Had you made any changes? Was there a code upload right before hand? Any details at all would help.
I been looking at my changes, I made some changes to city.js, those changes caused a syntax error, I uploaded a fix and the creeps died.
If your broken code causes the processes to die, and new processes took their place, then the new processes would not be able to associate with old creeps. That isn't something that would happen "naturally" though.
That could be the case then, thanks