Crash

Ok, these are kinda wierd situations, I'm using 4.01 I think. Anyway, one crash happened when I was trying to enable MXP with Test Trigger, on a dummy world. Maybe it was trying to enable it, maybe it was because it wasn't connected, I don't know.

Another situation(I don't think it crashed, but it wouldn't let me open the world file) might of been with a previous version. I play on a game that has an extended character set, and I copied and pasted a gag trigger that had extended characters in it, it all worked fine, until I saved and tried to reopen the next day. I was able to fix it by editing the world file and replacing the extended character(s) with wildcards. I'm guessing you use a signed char to read the file, or you made it that way on purpose. I've had trouble with signed chars in other programs, which is why I guess that's the problem. Anyway, it's not a huge problem, but maybe you should have it either warn the user if they enter extended characters that would cause an error when it reads the file, fix it so it'll read the extended characters as is, or escape the extended characters.

It would help in both cases to post the actual trigger that causes the problem.

I have tried a trigger that matched on something with the high-order bit set (ie. > 127) and it loaded OK.

That would be a problem since I no longer have that particular trigger, it happened several months ago, so maybe you fixed it in a newer version, I guess it doesn't matter unless somebody else happens upon it.

Oh well, I think we will consider this bug report closed.

For things that don't work, or cause crashes, a reproducable example is very helpful. MUSHclient is generally very reliable. The recent example of a trigger that had a thousand alternatives inside a single regexp, is a good example of something that hadn't been tried before, and caused a crash. The fix was even in code that I didn't write.

If you - or anyone - can reliably reproduce a problem, like a crash, or a file that won't load, don't discard it, post the details here so it can be fixed. Please specify the exact version you used, if possible the trigger (or whatever) that causes the problem, and the exact error message.