 |
Aleron
Wanderer
Joined: 01 Aug 2005
Posts: 76
|
 Posted: Tue Mar 13, 2007 12:29 am
Problems with commands in CMUD
|
I'm experiencing some very strange behavior from CMUD. I've got a pretty simple script running, and occasionally when it hits and alias or a line of text to send to the mud, it will append a number to the end before it does so. This even happens while I'm slow walking with #SLOW and #STEP. Below is an example of the way it just happened a few minutes ago.
<1085hp 232e 58969310xp 227mv [] NES>n 1
The portion in bold is what was sent to the MUD from CMUD (it was in yellow) when a #STEP was executed. If I'm not mistaken, I've even seen this happen with an alias, but I might be mistaken about this. This has happened numerous times in the past 10 minutes. The code block below shows the code that the example above occurred in, for what it's worth. Say the word and I'll post the compiled code as well.
| Code: |
#WAIT 500
#IF (@hitPoints > 600) {
#IF (%numitems(@mobsInRoom) > 0) {
kill %item(@mobsInRoom, 1) & berserk
#SAY ~[BOT~] Killing mob..
} {
#IF (@botState = 1) {
switchGear
}
#STEP
}
} {
#IF (@botState = 2) {
#STEP
} {
#VAR isSleeping 1
sleeph
}
} |
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Tue Mar 13, 2007 12:32 am
|
The most likely cause is that the AutoAppend option is on. Turn it off.
|
|
|
|
|
Aleron
Wanderer
Joined: 01 Aug 2005
Posts: 76
|
Posted: Tue Mar 13, 2007 12:37 am
|
Ok, so I turned that off for those aliases. I can see how that behavior would explain what was happening, but I still don't know WHY numbers were being appended. I can see every single place in my script where those aliases were being executed, and none of them were passed any parameters. Have any ideas about that?
|
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Tue Mar 13, 2007 1:19 am
|
It's a bug with the auto-append option. The aliases it affects are ones it probably doesn't need to be on for, so simply turning it off normally fixes it.
|
|
|
|
|
Aleron
Wanderer
Joined: 01 Aug 2005
Posts: 76
|
Posted: Tue Mar 13, 2007 1:21 am
|
Ah. Well just to reiterate in case Zugg missed it above, it also affects the #STEP command. Quite the bug.
|
|
|
|
|
Arminas
Wizard
Joined: 11 Jul 2002
Posts: 1265
Location: USA
|
Posted: Tue Mar 13, 2007 3:17 am
|
Aleron, the numbers you are seeing are not being actually SENT to the mud. They just appear where you can see them. Very strange indeed, but benign.
|
|
_________________
Arminas, The Invisible horseman
Windows 7 Pro 32 bit
AMD 64 X2 2.51 Dual Core, 2 GB of Ram |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Tue Mar 13, 2007 3:51 am
|
Please post what version of CMUD you are using whenever you make a bug report. This sounds like a bug that was fixed in the 1.25 update, but make sure you are running the 1.26 version.
|
|
|
|
|
Aleron
Wanderer
Joined: 01 Aug 2005
Posts: 76
|
Posted: Tue Mar 13, 2007 4:27 am
|
I am using version 1.26 (07-Mar-2007) Zugg.
|
|
|
|
|
Aleron
Wanderer
Joined: 01 Aug 2005
Posts: 76
|
Posted: Tue Mar 13, 2007 10:18 pm
|
| Arminas wrote: |
| Aleron, the numbers you are seeing are not being actually SENT to the mud. They just appear where you can see them. Very strange indeed, but benign. |
That is incorrect. It's actually being sent to the mud when that option is turned on. Take this example as proof:
| Code: |
look ancient.double-bladed.axe.+3 0
Nothing matching '0' found on an ancient double-bladed axe +3. |
|
|
|
|
|
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
Posted: Wed Mar 14, 2007 11:08 am
|
If you can reproduce it with an alias 100%, I suggest posting the compiled code too.
|
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Wed Mar 14, 2007 2:45 pm
|
I don't see anything in your example above that would send the "look" command to the MUD. I thought your example was about the #STEP command, which would only send directions. So you need to show us more detail on the exact alias and script that is running. So far I haven't been able to reproduce this problem.
|
|
|
|
|
Aleron
Wanderer
Joined: 01 Aug 2005
Posts: 76
|
Posted: Wed Mar 14, 2007 2:52 pm
|
The 'look' example was from something else in the script that happened right before I posted it, it wasn't a part of the original post. The look comes from this alias:
| Code: |
#TI 0
#IF (@isSleeping = 1) {
#VAR readyForNextRun 1
} {
look @mainHand
#WAIT 1500
#IF (@weaponCondition > 9) {
#SAY ~[BOT~] Weapon condition threshold reached~; not continuing.
quit
} {
#VAR expGained 0
#VAR isSleeping 0
#VAR readyForNextRun 0
#VAR botState 1
#IF (@groupMode = "on") {
gt up
#WAIT 3000
}
#VAR startTime %ctime
north
}
} |
I'm only seeing this happen when auto-append is turned on, btw. And again, sometimes stuff is being appended to text being explicitly sent to the mud by my code, sometimes it's not explicit (the case of #STEP doing it). If I get some time tonight, I'll try to reproduce this behavior with a simple script.
In case it helps, this script was imported via a .mud file. I went through and turned off the auto-append option on all the aliases however (there are only 3-4 aliases total), and I don't experience this behavior now (unless I turn it back on). |
|
|
|
|
|
|
|
