Setting up MUSHclient on the cloud

I'm using OneDrive, but my hope is to eventually have my own webserver at home. I know a lot of people use services like DropBox.

It seems that I can install MUSHclient on such a drive, but, upon running, it also sets itself up in Program Files.

I tried uninstalling it, in case an old install was causing issues. However, even when uninstalled, when I opened it from OneDrive, it kept trying to reference files from Program Files, making it difficult to save and use profiles that are stored on OneDrive.

Is there a way that I can do this?

It shouldn't. It should look for configuration files in the install directory, which can be anywhere.

That's very strange. Is there anything I can do to show the behavior?

Post what version you're using so Nick can investigate =)

Sounds a bit (just a bit) like my problem (minus the cloud). My very first install of MUSHclient was to C:\MUSHclient (luckily I read about not installing it to the program files folder since it's read-only, although that can be changed).

Then every install after that, whenever you go to load a world or anything, it defaults to showing the first install folder rather than the one I'm currently running.

Hasn't really bothered me enough to post about it though. Just a small inconvenience.

Only posting it now cause it's sounds a bit similar. I'm using v4.94

5.2. I believe that's the latest version. Hence no version posted.

5.02 you mean.



It doesn't "set itself up" anywhere, when it is run. I went to quite a bit of effort to make the client work regardless of where it is installed. The world configuration is stored in a SQLite3 database (mushclient_prefs.sqlite) in the same directory as the executable.

Can you please describe in greater detail what is happening to you?

I think what happened is that the old db files weren't getting deleted. I had removed the old Program Files folder, but there were a lot of sqlite db files in the onedrive folder. So, when I uninstalled it again, I backed up "worlds" and got rid of everything leftover from the previous MUSHclient install and that seemed to fix the problem.