|
Vorax Apprentice
Joined: 29 Jun 2001 Posts: 198 Location: USA
|
Posted: Fri Jan 14, 2005 5:28 am
#VERBATIM bug? |
Quote: |
VERBATIM
Syntax: #VERB [value]
Toggles the parsing mode. If value is specified, then it is used to set the parsing mode. Parsing is on if the value is non-zero.
VERBATIM example
#VERB
Same as selecting the Parse option from the Settings menu. |
Ok, I tried #VERB and it did turn parsing off. However, after paring is off, #VERB 1 doesn't do anything. The command is sent to the mud instead of being interpreted by zMUD and therefor does not turn parsing back on. Parsing has to be manually turned back on either by clicking the parsing icon or by selecting it in the menu. |
|
|
|
LightBulb MASTER
Joined: 28 Nov 2000 Posts: 4817 Location: USA
|
Posted: Fri Jan 14, 2005 6:32 pm |
This isn't a bug. When parsing is turned off, everything in the command line is sent directly to the MUD without processing. That's what 'parsing off' means! Since nothing in the command line is processed, that includes #VERB 1. It would be a bug if this DID turn parsing back on.
#VERB 1 is for use in scripts, which aren't affected by the Parsing On/Off setting. |
|
_________________ LightBulb
Senior member
Most scripts in this forum are written for Command Line entry.
Don't even open the Settings Editor unless its use is specified or obvious. |
|
|
|
Vorax Apprentice
Joined: 29 Jun 2001 Posts: 198 Location: USA
|
Posted: Sat Jan 15, 2005 12:17 am |
Ok, just wanted to make sure that it was working the way it was supposed to be. It just seemed a bit odd to me that parsing couldn't be turned back on the same way it was turned off from the command line.
|
|
|
|
|
|