MAM Enhancer 1.9.0: Debug Mode won't turn off
Hey, all. Turned on MAM Enhancer's Debug Mode a bit back to test out some basic mod making, getting recipe paths and such to modify. Didn't take any other steps than is normal - going into the savegame config, turning on the Debug mode, and doing what I needed to. I think I forgot to turn it off before I headed off for the night, but I remembered to turn it off by my next play session. During that session, it didn't turn back on - until I relaunched the game, and it was turned right back on. I then tried to turn it off and do a manual save, but even that manual save loaded with the debug mode on.
Not exactly sure what to do here. I'll send the usuals - savegame, SCIM debug and mod profiles - but I'm not sure what I can really do from here.
5 Replies
Automated responses for pantsmode (204690344808284160)
Key Details for SMMDebug-2025-09-29-01-11-51.zip
Outdated mods found!
Kyris Private Code Library can be updated to
3.2.2
Update these mods, there may be fixes for your issue in doing so.-# shhhhhhh Fred
It's been happening since even before that update got released.
Also, the -ddlog and -ddnewconsole flags are dummy ones for me to easily readd the actual flags to my launch options should the need arise.
If they do cause any issues, I'll nuke them, but I don't know what they would realistically be doing other than just returning null flag values.
I remember someone else ran into this as well and I think they used an editor to remove it from the save header
I'm not sure why it doesn't save as being off correctly, it should be a standard mod savegame setting
I am on the fence between removing the savegame setting and just using the config one because having it as a savegame setting makes testing with the launch script more difficult
IMO, if the savegame option is causing issues, you'd probably be better off just using the mod config setting
but i'm also not knee-deep into modding, so that might cause issues atp now that the system's been introduced
Worth mentioning that I think I turned it on some time before then and it did successfully turn off afterward, but the second(?) time it was turned on, this happened.
Can't confirm, vague memory at best.
The point of it being a savegame setting was to be per-save and also prepare for multiplayer stuff but I'm trying to take it a different direction and and make it work just client side