It seems that at the current state it is necessary to protect sending stats/ending game from multiple execution, as that can happen if you e.g. fail a mission more than once in the same tick (e.g. destroying two essential crates at the same time) Otherwise you can get a blank / stuck frontend (e.g. when using deagle to shoot the two last crates at the same time)! the best approach might be to never call the function that sends stats and ends game from any event handler directly, but instead have a flag 'isFailed' that is set to true when any of the possible fails happen and to check that flag every tick to send stats and end game if true

* turned out the no-flight zone is also a no-climb-and-progress zone * also changed it to not completely nullify velocity (otherwise cliffjumpers can get stuck in midair), just make sure dy is not negative

some more campaign string tweaks

string tweaks and whitespace fixes

german translation updates

don't allow autocamera to mess with targetting when e.g. spamming air-attacks in inf attack mode

fix buggy win conditions and stats in death01

- Special rooms which stay even when last player quits. Not useful for now, and can't be removed at all. - Define default value for SCRIPT in room config - Allow server admins to join 'registered users only' room

here have some lua love: make parameter count error messages more helpful to lua devs (also: some whitespace cleanups)

lua call SetAmmoDelay(ammotype, delay). note: as the engine does not yet support per-clan/team/hog ammo delay values, lua scripters will have to keep track of individual delays and set them accordingly before a hedgehog's turn (if they want usage cool-down behavior)