State file location randomly moving

This is probably simpler than I would think...but here's the deal. Between yesterday morning when everything worked fine, and yesterday afternoon when I went through a few machine reboots, my state file location decided to move from MUSHClient/worlds/plugins/state/ to MUSHClient/state/. And I don't believe I had anything to do with it.

But you can imagine it. When I turned everything on, all my plugins wanted to reinitialise (and the few -I- wrote sent the client into a loop due to 'these world variables you want are not being found so let's try again and give the same error').

What could have been the cause for this? Is there an option in the global settings? I couldn't see one myself..and I don't go in there often enough, so I know that I didn't touch anything. All I know is that I closed all the connections, exited out of the client, rebooted, played around with something else, rebooted again and what I would call the pointer to the state location had changed.

The state file location is now stored in the preferences database "mushclient_prefs.sqlite" in the MUSHclient executable directory.

Sounds like you somehow changed it (hard to say how, unless maybe you fiddled with the plugins folder). But possibly the "current directory" changed.

You can download the GUI SQLite3 browser from:

http://sourceforge.net/projects/sqlitebrowser/

Use that to open the database mushclient_prefs.sqlite, switch to the prefs table, and look for "StateFilesDirectory". You can then edit that to be the correct place and commit it back to the database. I would remove the "." personally and put in a full pathname. That should permanently fix it.

Straaange. For some reason it IS set as a full pathname right now, and in the new location (C:\Program Files\MUSHClient\state\). However I think I know what -might- have caused it.

I got to experimenting around with some server called Diaspora...and in the setup it needed to set up some MySQL stuff. It may be that somehow it...no this really does not make sense, though it's probably the most probable thing.

Well, since it IS a full path, I probably won't have any more problems with it. It's just be nice to know what in the world happened. Oh well.

Thanks for pointing this out. Besides knowing THAT, I also know now how to fix world windows that might get stuck on a second monitor or something lame like that.

Now to make backups...

MySQL and sqlite are totally different SQL libraries, though. MySQL runs a server process which you connect to in order to make queries, while sqlite is part of your program. I would be very surprised if Diaspora messed up the settings, because not only would it need to use sqlite, it would need to open that specific sqlite file.

Very true. I totally agree that it probably wasn't the MySQL stuff, but it seems the only likely thing, since it happened all of a sudden, and MySQL was the only thing that was doing any sort of database manipulation at the time that it occurred.