Zugg Software :: Search

No dice. I think the problem is larger than just the command prompt since MXP is breaking for the entire game. The prompt was just an example of what I am getting. Items in a room and players/mobs are ...

Indeed. I will talk to them and see if they are willing to experiment with changing the variable name to something else.

Yes, the error occurs when I create a brand new, blank character session with the only setting being the new trigger that executes #show. Another member on these forums also PM'd me and was easily abl ...

I'm having a difficult time buying that the game has anything to do with it. MXP works perfectly fine for every other client that supports it. CMUD is the only client having issues. They did update so ...

I can literally create any trigger I want and insert the code #show Hello and it will break MXP. I am manipulating no variables or doing anything but triggering off any expression whatsoever and execu ...

Any code at all. #show Hello will do this. I can create a trigger that fires on my character's name and executes the command: #show Hi

That trigger alone causes MXP to malfunction.

In an effort to try to further narrow this down, I place MXP in debug mode and checked the prompt text before and after the trigger firing. The result is as follows. Before:<<V Hp>1709</V& ...

Afternoon, all. My MUD recently updated to a new "version," and ever since that change any trigger that executes the #show command is causing MXP to malfunction until I reconnect to the MUD. It does n ...

Good afternoon!

I tried searching a bit but wasn't having a lot of luck.

Is it possible to use long exit names when using the open command during speedwalking/mapping?

The mapper has to be co ...