StaggerInfinite Command Breaks the Game

[Wozenbelt]

Making a CPU perform the 'Stagger infinite' command using the PlayerCommandTrigger breaks the game in separate ways depending on which way you load up the map. If done in regular play (e.g. hosting a game), SFD will simply crash.
It gets more interesting in the map editor; if done in the map editor (e.g. the 'Test Map' feature), the map will freeze ~3 ms and everything will be frozen but for the spinning, airborne CPU. After that, all you can do is exit the test run. However, you cannot test run any map once the bug is performed. You can delete the broken CPU, delete the broken map, and even test an official map. It simply won't work; your game will freeze immediately and you'll have to return to edit mode. Even if you exit the map editor, go into regular play (which will function properly), and come back, test runs will still be broken. The only true solution is to restart the game entirely.

But don't take my word for it! Try the map yourself!
SFDMaps Link here
(If the map hasn't shown up yet, it's because it hasn't been approved. Give it some time, or forget the map and take my word for it.)

[Gurt]

Thanks for the detailed report. Fixed after Alpha v.1.3.3.
It turns out that the stagger infinite command revealed an old and nasty bug.