Currently when the game binary crashes for any reason, it just displays a generic dialog without any additional information about the cause. If the game runs inside debugger, more details can be gained that way but we can't expect users to run such programs.
When we have multiple patches running simultaneously (Thinker, PRACX, etc), it becomes even more important to identify the actual cause of the crash if some user experiences it. Long term goal might be to enable some kind of exception handling in the main binary so that it could at least display the contents of registers if any crash occurs. Needs more investigation how to accomplish this.
Currently when the game binary crashes for any reason, it just displays a generic dialog without any additional information about the cause. If the game runs inside debugger, more details can be gained that way but we can't expect users to run such programs.
When we have multiple patches running simultaneously (Thinker, PRACX, etc), it becomes even more important to identify the actual cause of the crash if some user experiences it. Long term goal might be to enable some kind of exception handling in the main binary so that it could at least display the contents of registers if any crash occurs. Needs more investigation how to accomplish this.