 |
Erestar Newbie
Joined: 14 May 2001 Posts: 2 Location: USA
|
Posted: Thu Apr 17, 2003 9:55 am
More meaningful use of the #describe function? |
'ello all,
I'm new to ZMud programming... I have a goal I'd like to acomplish, so first I state that, then I'll write some possible ways I might be able to come about it.
I'm trying to get the infromation provided with the #describe command. Currently, it just prints the information about the room to the screen. I would like to take this information and use it in a more productive way. When I enter a room, I'd like to look up the exits of the room and display them, so that regardless of what the room was showing, I would always see the availiable exits because my mapper knows them.
Is there a way to redirect what is sent to the client window into a variable that I would disect? Is there a way to access the mapper data directly (without putting all of the information into a database?) What's the best way to do this?
Thanks ! |
|
|
 |
Vijilante SubAdmin

Joined: 18 Nov 2001 Posts: 5187
|
Posted: Thu Apr 17, 2003 11:04 am |
ZMud scripting 101: things that start with # are commands, things that start with % are functions. Commands do stuff like: send text to the mud, display text on the screen, and create settings. Functions return values for use in settings variables, being displayed to the screen, sent to the mud, and conditional testing.
So what you want is a function. Looking on the Function Reference page in the help you will find a section with about 30 functions for working with the Automapper. An example of displaying exit information from the mapper would be
#SHOW %roomexit() |
|
|
 |
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|