Zugg Software :: View topic - [2.13 Pro] Freeze when using zmapper commands

Beginner Joined: 07 Nov 2006 Posts: 22

I'm not sure this is a bug or me doing something wrong, but I read cmud pro is supposed to handle zmapper commands so I tried it. If I execute:
#echo %map.getroom(5).x
(5 is a real room on my map)
CMUD freezes until I press esc, then it prints:
<COMObject>.x

SubAdmin Joined: 18 Nov 2001 Posts: 5182

I also had a lockup in my mapping scripts with the regular version of CMud 2.13 and current zMapper. I hadn't traced it to a specific command yet, but there are enough similarities that I will say confirmed.

Posted: Mon Nov 26, 2007 5:20 pm

Are you doing this in an alias, or a trigger, or just on the command line?

Beginner Joined: 07 Nov 2006 Posts: 22

That one was just on the command line, I tried it in an alias and in a trigger as well now, and get the same behavior in all. I fired the trigger using #ECHO.

Some more detail after more testing:
After pressing esc, the string <COMObject>.x is actually sent to the mud server as well as being echoed locally.
Pressing backspace a number of times between executing the command and pressing esc changes the behavior, and the number of times you press backspace matters.
0 presses: Actually prints out "<COMObject>" and sends it to the mud (no ".x")
1 or 2 presses: Prints out "<COMObject>.x" and sends it to the mud
3 or more: Echoes "<COMObject>.x" locally but does not send to the mud

This is what usually happened, but not always. A few times after running all these things, and messing with backspace and esc, the aliased version stopped freezing completely and printed "<COMObject>.x" immediately, but I couldn't remember how I got that to happen. I then did something else (I think I ran the triggered version), and that froze; after that, the alias began freezing again and I couldn't repeat what happened.