Aliases

I'm just curious as to why the name of the alias now shows up after everything goes through. I find it just a little strange that it never happened before. Maybe one of the plugins I put in is doing it? No real big deal, just a minor annoyance.

I think there might be a bug where if you have "keep evaluating" checked that each alias that matches echoes the alias to the window - if this is what you mean.

I know what he means by this. It happens to me to, but it does actually affect what i am doing. There is another post of mine, explaining this problem. It is as if the client sends to the world the alias, and the codename for the alias. For example.

Let sp2inn = do 4e,n

i type sp2inn
i get:

sp2inn
do 4e,n
(doing directions)(e)
(doing directions)(e)
(doing directions)(e)
(doing directions)(e)
(doing directions)(n)
what? <-------- It is this line that interferes with any aliases that require the MUD to perform part of the command. Keep evaluating is not ticked in these cases, and it has only occured since using the new MUSH Client, 3.42.

Precisely what I mean. It goes through all the commands and then it reprints the alias name itself for some odd reason. Does the same thing when I'm using the plugins too.

In the thread you are referring to:

http://www.gammon.com.au/forum/?bbsubject_id=3086

I suggested you turn on "packet debug" to confirm that the alias was in fact being sent to the MUD. This is something that I can't reproduce. The appearance of "what?" does not guarantee the alias word was sent, it might be something else.

However you have not responded to that suggestion at this point.

I have an alias on a MUD I play called 'Town to Ranger'. It speedwalks me from the town to the ranger camp and this is the output:
31n 9w 10n 16e s
enter camp
town to ranger
(I figure you don't want me posting the FULL directions as that means 41 Ns, 9 Ws, 16 Es and an S.)
And after doing the directions, it promptly goes 'What?' because for some reason the MUD thinks the Town to Ranger is part of the alias.

Can you copy the actual alias (select it in the alias list and copy it). Then paste it here. You can't have an alias that literally does that because you are mixing a speed walk with "enter camp". I will guess you have done this:



Now before typing "town to ranger" I turned on "debug packets" under the Edit menu. This is what I got ...



My point is that is *all* it sends. There is no "town to ranger" sent. Thus, I can't reproduce this. I think the presence of "what?" doesn't prove MUSHclient sent the alias itself, it would be mad to do that, and my tests show it isn't.

I am asking you both to turn on debug packets and see for yourself what is sent.

Maybe what is happening is that the speedwalk sends too fast, you don't actually end up where you think you do, and the "enter camp" triggers a "what?" because you are not at the camp. Try moving one direction away from the camp and typing "enter camp" and see what happens.

You can enter a speedwalk delay to slow the speedwalks down. Also, maybe the speedwalk is simply wrong - you have too many of a direction there. When it stops, and you get the "what?" are you actually at the place where you expect to be?

Alias: town to ranger
Send: 31n 9w 10n 16e s (enter camp/out)
Exact output:
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
n
w
w
w
w
w
w
w
w
w
n
n
n
n
n
n
n
n
n
n
e
e
e
e
e
e
e
e
e
e
e
e
e
e
e
e
s
enter camp
town to ranger
What?

Or another alias

Alias: sc
Send:
skin corpse
gut corpse
carve corpse
put all in sack 2
put all in sack

Actual Output:

skin corpse
gut corpse
carve corpse
give meat to max
put all in sack 2
put all in sack
sc
You have 98 hps, 113 sps, and 519 gold coins.

sc on Ancient Anguish is a short form of the score command but about a month ago, it would never pop up with the short score command.

This is the debug I get:
Sent packet: 194 (3 bytes)

n.. 6e 0d 0a

Sent packet: 195 (3 bytes)

n.. 6e 0d 0a

Sent packet: 196 (3 bytes)

n.. 6e 0d 0a

Sent packet: 197 (3 bytes)

n.. 6e 0d 0a

Sent packet: 198 (3 bytes)

n.. 6e 0d 0a

Sent packet: 199 (3 bytes)

n.. 6e 0d 0a

Sent packet: 200 (3 bytes)

n.. 6e 0d 0a

Sent packet: 201 (3 bytes)

n.. 6e 0d 0a

Sent packet: 202 (3 bytes)

n.. 6e 0d 0a

Sent packet: 203 (3 bytes)

n.. 6e 0d 0a

Sent packet: 204 (3 bytes)

n.. 6e 0d 0a

Sent packet: 205 (3 bytes)

n.. 6e 0d 0a

Sent packet: 206 (3 bytes)

n.. 6e 0d 0a

Sent packet: 207 (3 bytes)

n.. 6e 0d 0a

Sent packet: 208 (3 bytes)

n.. 6e 0d 0a

Sent packet: 209 (3 bytes)

n.. 6e 0d 0a

Sent packet: 210 (3 bytes)

n.. 6e 0d 0a

Sent packet: 211 (3 bytes)

n.. 6e 0d 0a

Sent packet: 212 (3 bytes)

n.. 6e 0d 0a

Sent packet: 213 (3 bytes)

n.. 6e 0d 0a

Sent packet: 214 (3 bytes)

n.. 6e 0d 0a

Sent packet: 215 (3 bytes)

n.. 6e 0d 0a

Sent packet: 216 (3 bytes)

n.. 6e 0d 0a

Sent packet: 217 (3 bytes)

n.. 6e 0d 0a

Sent packet: 218 (3 bytes)

n.. 6e 0d 0a

Sent packet: 219 (3 bytes)

n.. 6e 0d 0a

Sent packet: 220 (3 bytes)

n.. 6e 0d 0a

Sent packet: 221 (3 bytes)

n.. 6e 0d 0a

Sent packet: 222 (3 bytes)

n.. 6e 0d 0a

Sent packet: 223 (3 bytes)

n.. 6e 0d 0a

Sent packet: 224 (3 bytes)

n.. 6e 0d 0a

Sent packet: 225 (3 bytes)

w.. 77 0d 0a

Sent packet: 226 (3 bytes)

w.. 77 0d 0a

Sent packet: 227 (3 bytes)

w.. 77 0d 0a

Sent packet: 228 (3 bytes)

w.. 77 0d 0a

Sent packet: 229 (3 bytes)

w.. 77 0d 0a

Sent packet: 230 (3 bytes)

w.. 77 0d 0a

Sent packet: 231 (3 bytes)

w.. 77 0d 0a

Sent packet: 232 (3 bytes)

w.. 77 0d 0a

Sent packet: 233 (3 bytes)

w.. 77 0d 0a

Sent packet: 234 (3 bytes)

n.. 6e 0d 0a

Sent packet: 235 (3 bytes)

n.. 6e 0d 0a

Sent packet: 236 (3 bytes)

n.. 6e 0d 0a

Sent packet: 237 (3 bytes)

n.. 6e 0d 0a

Sent packet: 238 (3 bytes)

n.. 6e 0d 0a

Sent packet: 239 (3 bytes)

n.. 6e 0d 0a

Sent packet: 240 (3 bytes)

n.. 6e 0d 0a

Sent packet: 241 (3 bytes)

n.. 6e 0d 0a

Sent packet: 242 (3 bytes)

n.. 6e 0d 0a

Sent packet: 243 (3 bytes)

n.. 6e 0d 0a

Sent packet: 244 (3 bytes)

e.. 65 0d 0a

Sent packet: 245 (3 bytes)

e.. 65 0d 0a

Sent packet: 246 (3 bytes)

e.. 65 0d 0a

Sent packet: 247 (3 bytes)

e.. 65 0d 0a

Sent packet: 248 (3 bytes)

e.. 65 0d 0a

Sent packet: 249 (3 bytes)

e.. 65 0d 0a

Sent packet: 250 (3 bytes)

e.. 65 0d 0a

Sent packet: 251 (3 bytes)

e.. 65 0d 0a

Sent packet: 252 (3 bytes)

e.. 65 0d 0a

Sent packet: 253 (3 bytes)

e.. 65 0d 0a

Sent packet: 254 (3 bytes)

e.. 65 0d 0a

Sent packet: 255 (3 bytes)

e.. 65 0d 0a

Sent packet: 256 (3 bytes)

e.. 65 0d 0a

Sent packet: 257 (3 bytes)

e.. 65 0d 0a

Sent packet: 258 (3 bytes)

e.. 65 0d 0a

Sent packet: 259 (3 bytes)

e.. 65 0d 0a

Sent packet: 260 (3 bytes)

s.. 73 0d 0a

Sent packet: 261 (12 bytes)

enter camp.. 65 6e 74 65 72 20 63 61 6d 70 0d 0a

Sent packet: 262 (16 bytes)

town to ranger.. 74 6f 77 6e 20 74 6f 20 72 61 6e 67 65 72 0d 0a

But it appears to drop some of the commands because it seems to blank out when it reaches a certain point even though it continues on.

Like was said before. You may be suffering from a buffer issue. Most muds have a buffer limit of X commands. If it recieves too many in a row it can lose which ever ones hit at that time. This is usually not the ones at the very end, but something in the middle of the list.

This used to happen all the time on the mud where I play until they adjusted the buffer size to handle longer sequences. Had it only effected single players, they probably would have never done anything about it. However, it tended to happen when there was a party of 3-4 people all auto-following one of the players in the group. On a long movement, like >10 rooms one of them would find themselves in the dust behind everyone else. This was even more true if the characters involved had summoned helpers along with them, like an orb, familiar, undead or woodland apprentice. Until the admin expanded the buffer, the only way to move such long distances without it effecting parties was to slow down the rate 'you' entered the direction commands.

This has a high probability of being why you are getting a problem. It isn't an issue with Mushclient, merely a problem with the mud not being fast enough, or having enough room to keep track of everything you are telling it to do. On Ages of Despair, the fixes to improve parties following allow single players to get by with feeding the mud 20-30 moves in under a second. Most muds will simply overflow and ignore some of your commands.

The missing directions isn't the problem. It's the fact that the aliases names keep getting posted on the game. I already figured that the little blip was no big deal. I just wanna know why it goes 'What?' after an alias goes through properly. I just thought I'd add that little notation because the debug packet doesn't have all the commands in it even though doing the alias does.

Can you please copy the actual, whole, alias? Select it in the alias list and click the "copy" button. Then paste it here. You should see some XML code like in my earlier post.

Also, which plugins do you have installed? Try removing them and seeing if the problem goes away.

I found out what was causing it. The ansi log plugin.