Same story in Internet Explorer and in Firefox. I’ve loaded the FMudClient from scratch several times now.

If you’re using a different browser, I could try that one. But I’m getting somewhat consistent results.

When I create a new alias, and use an asterisk for pattern matching, it works as expected. But if I export and import, it doesn’t work. If I go back in and edit the Alias *Pattern* box, (even if I type in exactly the same thing) it doesn’t work, and if I quit out, and log back in, it doesn’t work.

Maybe, even if you can’t duplicate the problem, you could still see if there is any difference in the subroutines for reading in a new alias (which seems to work well) vs. {modifying an old alias, importing an alias, loading an alias}. Just to see if it is exactly the same subroutine or not.

Thanks,
Jonathan

A couple of things you can try:

1. Clear your browser cache to make sure you have the most up to date version of the client.
2. Strip the alias down to the bare minimum so it just sends echo(this[1]) for example and try recreating the problem.

First, I upgraded from Flash 10,0,22,87 to Flash 10,0,42,34. This did NOT seem to have the desired effect. The problem continued.

Next, I tried copying the code, deleting the alias, and re-creating the alias from scratch (pasting in the old code.) THIS WORKED! However, it looks like I will have to do this copying and pasting every time I log in to the game.

I’m curious if you log off and log back on again, and try the alias again, does it still work? If not, maybe it is another issue on the IRE server side? Are they storing unseen character strings? Or are there two separate compilers depending on whether it compiles the code when you log in, or if it compiles the code when you type it into the alias box?

My sense is that if I edit an old alias, I can’t get the this[1] keyword to work, but if I create a new alias, the this[1] keyword works just fine. (I’m not 100% sure about this, though)

I like using your client, and I hope that this is helpful to you–I guess if you’re not having these issues there’s not much you can do. But I still appreciate your prompt reply.

Thanks,
Jonathan

Alias: cfa *

execute:
echo(this[1]);
send(”cast firelash at “+this[1]);
send(”st kill “+this[1]);

The first time I ran it, this[1] became the proper target. Then later, I found that this[1] was null, and this[0] was cfa.

I’m sure I didn’t switch anything–all that happened was I quit and came back later. Any idea what is going on–if there is any work-around?

Oh, and I also noticed that the system doesn’t store backslashes between runs. This actually happens in your demonstration video when you quietly type them in after they disappeared.