Zugg Software :: View topic

Wanderer Joined: 06 Jan 2006 Posts: 70

Blugh. So I corrupted my settings awhile ago, tried the migration process, corrupted them again. -sob- Im thinking of trying a diagnostic to see what exactly is corrupting my settings? Maybe just use some perl expressions to search the zMUD settings for syntax errors or summat. Trick is, I have no idea what is corrupting it in the first place? Any references on common ways to corrupt your settings? I get access violations from time to time, mostly dealing with the map I believe. I first I thought #tag was causing me problems but now it seems to be working regardless. I notice it when my zMUD starts to slow down, I close zMUD, get 1-2 error beeps but no message, restart, sometimes it tells me my settings are corrupted, sometimes it doesn't. Then it's fine! I'm confuzzled.

Posted: Tue Feb 14, 2006 9:02 pm

First, are you using version 7.21? The newer versions corrupt the settings a lot less than the old versions.

The way settings get corrupted is that the settings file is just a dump of memory. So if memory gets messed up, like via an Access Violation, and then you have the AutoSave option enabled, then when zMUD exits it can write the corrupted memory to your settings file.

So, one way to avoid corrupted settings is to turn off the AutoSave option and then only save your settings manually after making a change to them.

Also, if you have a bad trigger or script that is causing the Access Violation, fixing or disabling the trigger or script can stop the error which is causing the memory to get corrupted in the first place.

Wanderer Joined: 06 Jan 2006 Posts: 70

Im pretty sure it's a trigger that is corrupting it. I'll do some tests and try and find it. Thanks for the tips though!

Wanderer Joined: 06 Jan 2006 Posts: 70

Hmm, I think this all started happening after I converted some triggers to PERL expressions. Any know issues with that?