Problems with plugins

I have managed to get the AINSI_log plugin onto my MUSH Client, which is the 3.32 version, and when i go to click 'add' to my list of currently running plugins, i get a message telling me that there is an error. Then there is a displat line of something along the lines of:
line X: Plugin requires MUSH Client version 3.32 or above in order to run AISI_log.
This is just the gist of what the line says. I definitely have version 3.32 installed, and can't run the plugin, do you know why this might be?

It is saying it needs version 3.35 to run, because it uses some features that were introduced in that version. The latest version is 3.42 - see the downloads page. I suggest you get that version.

OK Nick, i have now downloaded the new mush client, onto my older one, but i am having problems with it. I think that it is my aliases that are not compatible in the new mush client, for example, if i have an alias of 'tbr' which would be 'travelto bree' and then the mud would take me on a journey, the client interrupts the command sequence, and stops my travelto. This doesn't happen if i have a set of directions or commands aliased, like do 3n,2e,4n.etc, but i do get a message at the end from the mud, saying 'what?'
This leads me to believe that the client aliases are now trying to do something during the alias itself, or just aftwer, which they shouldn't be doing, do you have any idea what thios could be, or how i could solve it?

I don't quite understand all of that.

What do you mean "the client interrupts the command sequence" - in what way?

The newer versions should be compatible with older ones - I hope you backed up the old world file first - I could look at it and see what the differences are.

Not sure what you mean by "This doesn't happen if i have a set of directions or commands aliased, like do 3n,2e,4n.etc, but i do get a message at the end from the mud, saying 'what?'" - does it work and then you get the 'what', or does it not work at all?

When the client sends an alias, it sends the alias command as well as the text. ie, i have aliased 'trb' to travelto bree, yet when it type in 'trb', it sends 'travelto bree' as well as 'trb', which is why i am getting the 'what?' message

It might echo it (so you can see it) but it won't send it. That would be pretty useless.

I know it sounds stupid, but i am pretty sure that i am getting a send of the alias, and the garble that i name it after it, which interrupts the alias itself. Kinda stupid i know. I am also having trouble colouring particular words whenever i see them, for some it works, for others it doesn't seem to.

Can you copy and paste the alias here? And the trigger that isn't working. Just select it in the alias list and click the Copy button, then paste the results here.

Also paste some example output the trigger should be matching on.

First, the trigger. Say i want to colour top level thieves, i type in the trigger on box 'Crime Lord', and have the enabled, and regular expression checked, along with a colour selected. This sometimes works, but not all the time.
The main problem is with my aliases.ie.

<aliases>
<alias
match="tbr"
>
<send>travelto bree</send>
</alias>
</aliases>

What happens here, is i start off on my little jounrney to bree, then after i move a few rooms, i am stopped by the 'tbr' command, which interrupts the traveto sequesnce. With other aliases such as:

<aliases>
<alias
match="ada"
enabled="y"
>
<send>do 2e,2s,2e,2n,ne,e,request healing</send>
</alias>
</aliases>

I do all the directions, then the command kicks in at the end of them,(the command being ada, which is a nonsense command used as an alias) and so i get a message of 'what?'
As for the triggers, an example of this is:

<triggers>
<trigger
custom_colour="7"
enabled="y"
match="(Demonic)"
regexp="y"
sequence="100"
other_text_colour="black"
other_back_colour="black"
>
</trigger>
</triggers>

This is a trigger which works all the time for me, and always colours (Demonic) in red.

<triggers>
<trigger
custom_colour="9"
enabled="y"
match="Archmage"
regexp="y"
sequence="100"
other_text_colour="black"
other_back_colour="black"
>
</trigger>
</triggers>

This one however, never works, and never colors the Archmages that i see. I don't know why this is.

Isn't this similar to another thread we couldn't figure out, where the alias was evaluated causing infinite loops? Maybe it's an obscure bug? It never happened to me...

For one thing, the "tbr" alias is not enabled, so it will send "tbr" to the MUD.

As for the trigger that doesn't match, I suspect that you have another trigger that is matching, and that is stopping your other one from matching as well. Try colouring each trigger so you know if they match, and set "keep evaluating" where relevant if you want more than one match.

Are you sure it is sending "ada" to the MUD? Try turning on "packet debug" to confirm exactly what is being sent. It could be anything that is causing a "huh".

..funny seeing what different muds send when they don't understand a command, such as "huh?" in the above case.
The mud I play has a good one:
"Arglebargle, glop-glyf!?!"

I disabled the tbr alias, because it wasn't working

An obscure command, yet many muds have it (particularly LPC type muds): "history"

This will show you a list of your most recent commands. You may want to investigate, see if your mud supports it.

On the Game menu you can turn on "Trace" so you can see what aliases match. You can also go to the Edit menu and turn on "Debug Packets".

I pasted your alias, enabled it, did the above steps, and then typed "tbr". This is what I say ...


TRACE: Trace on
TRACE: Matched alias "tbr"
travelto bree
Huh?


This is what I expect, because this MUD doesn't recognise the travelto command. But did it also get the "tbr" command sent? Looking at the debug packets window (a separate window opens) I see this:



You see there is no "tbr" sent. You can try for yourself.

There is a bug in MUSHclient where it reports the current version as the required version rather than the version that is actually required. You can find that out by looking inside the plugin file. That is fixed in version 3.43.

Nick, i think that the problem is occuring with the aliases when the ainsi log plugin is on. My aliases work fine when i remove the plugin, but when the ainsi log plugin is on, the aliases are matching on the ainsi log or something:

TRACE: Matched alias "ada"
do 2e,2s,2e,2n,ne,e,request healing
TRACE: Matched alias ansi_log
ada
TRACE: Executing alias script "LogCommand"
Do: starting commands.
TRACE: Matched trigger ansi_log
TRACE: Executing trigger script "LogOutput"
(HP:220 EP:119) Inside the West Gate of Bree(e, w and n)
TRACE: Matched trigger "EP\:\b((1[01234]\d)|([89]\d))\b"
TRACE: Matched trigger "HP\:\b((2[012]\d)|(1[56789]\d))\b "
TRACE: Matched trigger ansi_log
TRACE: Executing trigger script "LogOutput"
.
.
.
.TRACE: Matched trigger "EP\:\b((1[01234]\d)|([89]\d))\b"
TRACE: Matched trigger "HP\:\b((2[012]\d)|(1[56789]\d))\b "
TRACE: Matched trigger ansi_log
TRACE: Executing trigger script "LogOutput"
(HP:220 EP:119) Do: Commands completed.
TRACE: Matched trigger "EP\:\b((1[01234]\d)|([89]\d))\b"
TRACE: Matched trigger "HP\:\b((2[012]\d)|(1[56789]\d))\b "
TRACE: Matched trigger ansi_log
TRACE: Executing trigger script "LogOutput"
(HP:220 EP:119) What?

this means nothing to me, maybe it would mean something to you? any feedback would be great! Also, whilst i am here, is it possible to change the colour of the text that shows your commands from the reddish colour that it is atm?