> Well, best solution would be to get rid of this limit entirely I suppose :P
No, the limit is important. Removing it, we could risk SIGSEGVs, extreme lag,
and other problems. However making the error non-fatal seems much better imo.
Now, aren't there the 'volatile' obstacle? When level is respawned, these
obstacles are deleted. Why don't - if we detect the error - we force a volatile
deletion first and after that see if we really need to show the warning?
The best solution, obviously, would make dead bots run a timer and when the
timer finishes (after, like, 30 seconds), delete the dead bot obstacle and
respawn that one bot.