 |
Anaristos Sorcerer
Joined: 17 Jul 2007 Posts: 821 Location: California
|
Posted: Mon Feb 04, 2008 8:01 am
Garbage added to room script box after script is deleted. |
After deleting a room script so that there is no script for that room, the word "ALL" will appear as the scritpt once the room information is saved. Needless to say that the mapper thinks this is a script and will try to execute it next time one walks into the room. I've gotten around the problem by entering a blank and then saving the room data.
CMUD2.18 (and CMUDpro2.18) under Vista. |
|
|
|
 |
Fang Xianfu GURU

Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Mon Feb 04, 2008 11:21 am |
How are you deleting the room scripts?
|
|
|
|
 |
Arde Enchanter
Joined: 09 Sep 2007 Posts: 605
|
Posted: Mon Feb 04, 2008 12:09 pm |
I reported this kind of bug in 2.03 and Zugg had fixed it in 2.04 (see version history). Looks like the bug is back again... I just wonder did you see this bug right after installing 2.18 or it have start to appear only recently?
|
|
|
|
 |
Anaristos Sorcerer
Joined: 17 Jul 2007 Posts: 821 Location: California
|
Posted: Tue Feb 12, 2008 2:30 am |
I can't really tell you if the bug was 1.34 or not. My map database predates CMUD. I decided to remove the room scripts because some of them were causing the mapper to crash. Then I started noticing that on occasion the MUD would try to execute an "ALL" command. I found the command logded in the room script box of rooms from which the script had been removed. Further test proved that "ALL" was being inserted whenever the data in the room script box was removed. So one must keep at least one blank character to keep this from happening. BTW the reason the mapper was crashing was because it was trying to execute a #TRIGGER directly inserted into the script box. If this was replaced by adding the #TRIGGER via the settings or on the command line, the mapper would work fine. The #TRIGGER bug is is predictable.
|
|
|
|
 |
|
|
|