World file won't open

I'm not sure if this is a bug, it could very well be my own newbiness.

I just upgraded from 4.37 to 4.40 and lost all my triggers, aliases and timers when I logged into my world. The plug-ins weren't loaded, but at least they can be easily reloaded.

My understanding is trigs and aliases are saved in the world.mcl file, so I'm confused how an upgrade would touch those files. I'm also positive the world file was saved as I'm using the auto-save timer.

Did I do something wrong?

I am not sure why that would happen. Global plugins not loading I can somewhat imagine if the settings in in the registry didn't transfer over properly to the new sqlite prefs database. But the other things really confuse me. Did you get any error messages? ('cannot load whatever.xml' or something like that)

After the discussion in that other thread about the current directory, I can't help but think the startup directory might have changed, causing some files not to be loaded properly (relative paths and all).

No, no error messages at all, although after launching the client and opening my world it hung. I had to force a connection through quick-connect.

First, if you "force a connection through quick connect" you have made a different world file, haven't you? That wouldn't have any of your earlier triggers in it.

The original world file, if it still exists (that is, if you haven't overwritten it), should still have everything in it. I would open that up in a text editor and see if you can see heaps of things after <triggers> in the world file.

There was a recent discussion about someone who had MUSHclient hang upon opening.

http://www.gammon.com.au/forum/?id=9399

It was a problem with a trigger matching an empty string. You can edit the world file with a text editor and disable triggers temporarily (as described in that thread), which might help.

The world was overwritten when I put the auto-save timer back in :/

The only thing I can think of that relates to that other article for target/variables is that I used the "target" trigger (FAQ 21 and 22 I think). Such a simple trigger. One would assume it would save the variable as the last target specified and not leave it empty?

I'll try to recreate it.

Edit: Findings so far.

Note - I changed the subject title as it has nothing to do with the upgrade as I originally thought.

Couple of things so far. First, I found the world file with all the triggers/aliases, etc that I wanted. Interestingly enough I found it in;

E:\Program Files\MUSHclient\worlds\plugins
instead of the directory above it
E:\Program Files\MUSHclient\worlds

I stumbled across this when I created a new 'test' world and saved it, noticing it defaulted to the plugins directory. In the test world I only recreated the target trigger and it opened fine again afterward, so that can't be it.

Next, I followed the instructions in the article above, I copied the original file back into the worlds directory, opened it in Notepad and changed the enable_aliases, enable_triggers, enable_scripts, enable_timers to "n".

It still won't open. I go to Open World, select that file and nothing happens, it doesn't even open and hang any more. There's no error messages anywhere.

I'm not sure what to look for next.

That sounds really odd. Can you upload the file (sanitized, no passwords but still showing the symptoms!) to a pastebin or some online file storage facility so we can download it and look in it? Right now, it's all guesswork...

What is the world file's filename?

Maybe it opened but is not visible? Try going to Window menu -> Cascade.

Or, once it is opened can you press Alt+Enter to bring up the configuration?

No, the window isn't hidden. I already cascade as I usually have a couple of different worlds open at a time.

BUT! I solved the problem, in a twisted roundabout way.

The existing file name was Fury Newest2.MCL. (Fury<space>Newest2, cause you can't quite tell here). I changed the file name to Fury_Newest2.MCL to upload it here;

http://fury.jelly-wars.com/Fury_Newest2.MCL

Feel free to take a look, there might be other things wrong with it.

Anyway, I took a chance and opened world Fury_Newest2.MCL and it opened!!

I don't believe the file name was the problem, as I also have Fury Newest.MCL that I use for my Imm char that opens just fine.

So, any guesses? :)

If you copy it and name it the filename that didn't work, is it still broken?

Yes, it's still broken if I rename it back.

The reason I asked about the filename is that, I recall from years ago, with some world file names, if you tried to open them, the "file open" dialog box would fail, and thus MUSHclient thought you had tried to open the file, and clicked on Cancel.

This is, naturally, not behaviour I coded in myself, but I found with some operating systems (Windows 98 perhaps) that certain characters in a filename caused this behaviour. I didn't think space was a problem, but I suggest you work around it by not using spaces in your filenames.