-----------------
poster: Baer
subject: echoing text
date: Wed Feb 7 03:12:09 2001
If you have a trigger for example, to say tock when you get a tock,
replace the trigger action with
#sh tock
This will ensure the message only goes to your screen, not to the
mud to spam us.
Also remember to put a ! in front of other triggers like reporting
from a new round.
Extracted below is #sh and #sa from zmud help.
----------
SAY
Syntax: #SA text
Same as the SH command. Echoes the specified text to the screen
without sending it to the MUD. A Newline is added to the end of the
string. To put a newline in the middle of the text, use the %{cr}
function.
SAY example
#SA You have @gold coins
Prints You have nnnn coins to the screen where nnnn is the current
value of the @gold variable.
#ACTION {aura fades} {#SA SANC IS OUT!!!!;#COLOR red}
If the string aura fades is received from the MUD, the string SANC
IS OUT!!!! is displayed to your screen and colored red.
-------------------
SHOW
Syntax: #SH text
Same as the #SAY command. Echoes the specified text to the screen
without sending it to the MUD. The difference between #SAY and
#SHOW is that #SHOW processes the text just as if it was received
from the MUD. This means text for #SHOW must be in Telnet format,
which means %{crlf} should be used for newlines instead of just
%{cr}.
SHOW example
#SH You have @gold coins
Prints You have nnnn coins to the screen where nnnn is the current
value of the @gold variable. Any trigger set up for this type of
pattern will get triggered.
-----------------
poster: Hierokliff
subject: automapper.
date: Fri Feb 9 07:53:36 2001
In ver6.15 the automapper is too good to be true, is it just me that
feel it's almost cheating to use it in muds? but the problem is with
this mud, it refuses to configure, or is it just me and my bad luck
and short tempere?
//Hierokliff the mapper who needs a clue.
-----------------
poster: Zifnab
subject: >automapper.
date: Fri Feb 9 13:13:12 2001
On Fri Feb 9 07:53:36 2001 Hierokliff wrote post #2:
> In ver6.15 the automapper is too good to be true, is it just me that
> feel it's almost cheating to use it in muds? but the problem is with
> this mud, it refuses to configure, or is it just me and my bad luck
> and short tempere?
> //Hierokliff the mapper who needs a clue.
Not sure what you mean by 'refuse to configure'. I have looked
at Zmud's MXP protocol sparingly (since i feel portal is dead)
and Zmud's protocol is open, so those that use other clients
could use it without the hassle that portal gave us.
Anyway the MXP protocol has hte mud send tags to ZMUD that
control the mapper, is that what you are referring too?
-----------------
poster: Hierokliff
subject: >>automapper.
date: Fri Feb 9 20:08:16 2001
On Fri Feb 9 13:13:12 2001 Zifnab wrote post #3:
> On Fri Feb 9 07:53:36 2001 Hierokliff wrote post #2:
> > In ver6.15 the automapper is too good to be true, is it just me that
> > feel it's almost cheating to use it in muds? but the problem is with
> > this mud, it refuses to configure, or is it just me and my bad luck
> > and short tempere?
> > //Hierokliff the mapper who needs a clue.
> Not sure what you mean by 'refuse to configure'. I have looked
> at Zmud's MXP protocol sparingly (since i feel portal is dead)
> and Zmud's protocol is open, so those that use other clients
> could use it without the hassle that portal gave us.
>
> Anyway the MXP protocol has hte mud send tags to ZMUD that
> control the mapper, is that what you are referring too?
Well was mostly whining about that i didnt get the 'autoconfig' in
zmud to work, but after i did make a new settings file in zmud
without all triggers it wasnt a problem.
Zmud triggers on exits and roomname to create a small map while you
are exploring, another question is if its ok to publish these ?
since they do def contain quest material if u make maps of those
areas...
And with the ability to create triggers for specific rooms/areas
when enter them, oh hmm i dont need to play soon *kicks zmud and
goes back to telnet*
//Hierokliff
-----------------
poster: Zifnab
subject: >>>automapper.
date: Fri Feb 9 20:55:36 2001
> > could use it without the hassle that portal gave us.
> >
> > Anyway the MXP protocol has hte mud send tags to ZMUD that
> > control the mapper, is that what you are referring too?
> Well was mostly whining about that i didnt get the 'autoconfig' in
> zmud to work, but after i did make a new settings file in zmud
> without all triggers it wasnt a problem.
> Zmud triggers on exits and roomname to create a small map while you
> are exploring, another question is if its ok to publish these ?
> since they do def contain quest material if u make maps of those
> areas...
> And with the ability to create triggers for specific rooms/areas
> when enter them, oh hmm i dont need to play soon *kicks zmud and
> goes back to telnet*
> //Hierokliff
Yeah go ahead and publish them, if a quest is totally reliant
on a map I think we have other problems that need to be
addressed. (and quests are not as exploitable as they once were)
I am still tossing around the idea of using Zmud's MXP (then you
woudlnt have to make your own triggers).
My concerns with it are that it seems overly coplex, fairly easy to spoof,
and that we have 2 other things we are using now, portatl and
RDMP (although limited) we reallly need to decide on one
and go with it.
**