Errors and warnings are spat out when for various reasons when you’ve been a naughty developer. These seem to come in two flavours; ERROR and WARNING. Some examples:
ERROR:GAMESYS
ERROR:SCRIPT
ERROR:GAMEOBJECT
WARNING:RENDER
WARNING:DLIB
WARNING:PARTICLE
WARNING:GRAPHICS
WARNING:GAMEOBJECT
WARNING:SOUND
WARNING:ENGINE
WARNING:RESOURCE
Two questions:
-
Is there a hard and fast rule as to which of these warnings or errors cause a hard crash (game shuts down) and which ones cause a soft crash (allowing the game to continue, but limping badly, usually towards a cliff edge). My guess is that errors always cause a hard crash and warnings never do.
-
I use sys.set_error_handler() for crash reporting. Have all errors from this callback already caused a crash, or does it also report soft crashes? If so, is there a way to distinguish between soft and hard crashes?