Quote:
... but its sort of odd if I need to change something in the world file and save it, only to get a whole list of, "unable to create the plugin save state file blablabla-state.xml", errors for every installed plugin ...
OK, let's work this one through. First the error message should have given a full pathname. Does that path actually exist? Something like:
C:\mushclient\plugins\state\03c761d33c14fbd2d442f040-fba8f08ebbdd03bcae94ab05-state.xml
In this example, confirm the directory 'C:\mushclient\plugins\state\' exists.
When MUSHclient saves a state file it creates the pathname like this:
- Plugins directory - print (GetInfo (60)) - to see what this is. If this string is empty - failure.
- Append: 'state\'
- Append: world ID - print (GetWorldID()) - to see what this is. If this string is empty - failure.
- Append a hyphen.
- Append the plugin ID (see inside plugin for what this is).
- Append: '-state.xml'
It then attempts to create and open this file for writing, writes the plugin variables to it, and closes it. If it cannot open the file (or create it) you will get that error message:
Unable to create the plugin save state file: (file name as above)
Quote:
If I "manually" save the world file I get the same error on "every" installed plugin.
This is a bit of a puzzle, except that maybe somehow the plugins directory is changing midstream if you manually save the world. I would check what it is from GetInfo (60) and see if a different value ends up in there after a manual save compared to an automatic save.
Maybe check under Global Preferences -> Plugins, to see what value is there for the Plugins directory.