You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lua errors should lead into a crash, since anything else could even lead into savegame corruption.
plain pd2 and blt4w behaves like that, only blt4l does not.
i still think that an optional just-log debug mode is useful and legit for devs though.
The text was updated successfully, but these errors were encountered:
Okay, I've got basic support for generating a crash.txt file and exit()ing the game when an error occurs.
This can be disabled by setting BLT_CRASH to CONTINUE, in which case it will act as it does currently, only it also prints the Lua stacktrace to the log.
lua errors should lead into a crash, since anything else could even lead into savegame corruption.
plain pd2 and blt4w behaves like that, only blt4l does not.
i still think that an optional just-log debug mode is useful and legit for devs though.
The text was updated successfully, but these errors were encountered: