That's great! Can't even remember how often I had to do the song and dance of "do you have exceptions enabled" - "no I didn't even know what that was" - "then I cannot help you but please turn it on in case of future errors" because of this.I never understood the idea behind hiding python errors. If there is an error, then people will notice something if wrong, error message or no error message. Even worse, the default is to hide the errors and sometimes the ini file resets itself to hide (related to crashing game? switching active mod?).
I changed it to always be active after I missed a bug due to the hiding setting having reset itself without telling me. I added the following:
Add the last line to the DLL and your mod will never again suffer from having the python errors hidden, regardless of user settings.PHP:DllExport bool CvXMLLoadUtility::LoadPlayerOptions() { if (!CreateFXml()) return false; gDLL->ChangeINIKeyValue("CONFIG", "HidePythonExceptions", "0");
This game was released in the time of boxed DVD releases where the idea of reporting errors online and rolling out frequent patches wasn't really accepted yet. I assume they just decided to hide error messages from the user to make their product appear more functional because it was a lot less expected for users to see error messages and they didn't have a mechanism to act on those user reported errors anyway. Typical corporate decisionmaking.