Zugg Software :: View topic

Beginner Joined: 24 Aug 2002 Posts: 14 Location: USA

all i need to do is set a trigger to send the room vnum to the auto mapper for it is in my prompt looks like this vnum <the vnum>

GURU Joined: 10 Oct 2000 Posts: 1116 Location: USA

You can use the teleport command, something like:

#trigger {^~<%d/%dH %d/%dM %d/%dV ~<(%d)~>~>} {#teleport %1}

Iljhar

Beginner Joined: 24 Aug 2002 Posts: 14 Location: USA

I am not attempting to teleport just send automapper the vmum so my rooms do not cross in the mapper

Beginner Joined: 24 Aug 2002 Posts: 14 Location: USA

here is an example of what a room would look like in my mud.
Omnipresent Being's Office Complex
The air here is thick with the sounds of creation. The Supreme Beings
do much of their Galactic building in rooms adjoining this one. In all,
there are four seperate offices accessable from here, along with the
Reality Control center, which is directly above this room. North leads
back to the hub of the complex.
Obvious exits:
North - Omnipresent Being's Monitering Room
East - An empty home
South - Scarecrow's Do Not Enter
West - An empty home
Up - The Omnipresent Mail Room
Down - An empty home
Northeast - An empty home
Northwest - An empty home
Southeast - An empty home
Southwest - An empty home
Durgas Wormhole is here folding reality into new dimensions.

vnum: 106

GURU Joined: 26 Jul 2001 Posts: 1958 Location: Canada

Look into using #TAG to flag it. Once you use #TAG you need to reconfigure your map.

An example from the help files:

quote:

#TRIGGER {(*) ~[(*)~] ~#(%d)} {#TAG name,exit,vnum {%1} {%2} {%3}}

Ton Diening

Beginner Joined: 24 Aug 2002 Posts: 14 Location: USA

but what do all the ~ and * mean and how would i configure triggers and tags to do so i just do not seem to understand? I sapose some might be in the online help but i have no java support to use it.

GURU Joined: 15 Jun 2001 Posts: 654 Location: USA

If you are mapping this for the first time, look into #TAG as TonDiening suggests. The ~ and * are special symbols used in zMUD triggers. See here and here for more information.

If, as I suspect (you didn't specify), you have a map already made and wish to assign VNums to it now, you'd use something like:

#TRIGGER {vnum <(%d)>} {#NOOP %roomnum(,%1)} "" {prompt}

This will update the current room on the map with the VNum from your prompt. Note, this does not have any error checking so if your mapper position and MUD position don't match, you'll end up setting the wrong room's VNum.

- Charbal

Beginner Joined: 24 Aug 2002 Posts: 14 Location: USA

First of all let me thank all of you for the help i have recived. I do not already have maps made i am assuming that getting all of the information into the automapper room names, desc, exits and vnums will help solve alot of my cross over problems with making the maps for the areas already install(stock area's) and the areas my builders are working to complete. ie when you come a full circle and the mapper assumes that the room meets another at a join but realy you area in a structure of some sort and yor rooms get crossed.

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

You don't need to use the Online Help Files. The Online Help Files are a duplicate of the same helpfiles found in zMUD itself. Just click the Help menu at the top of zMUD, then click Contents in the menu, and go from there.

LightBulb
Senior Member

Beginner Joined: 24 Aug 2002 Posts: 14 Location: USA

I have read over the help files that come with zmud but i still do not understand what i need to do? I had thought that the online ones were more up to date. It still does not change the fact that i can not figure out what i need to do!

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

From the Special Characters page:
Quote Char

Used to escape other special characters. To send any special character to the MUD without parsing it, precede it with this character. Default is ~

From the Pattern Matching page:
* match any number of characters or white space

LightBulb
Senior Member

Enchanter Joined: 10 Oct 2000 Posts: 656 Location: USA

Try

#TR {^vnum~:%s%d} {#tag vnum {%1}}

I think this should work for you.

As mentioned, rerun the auto-config after you create the above trigger.

Talahaski
Processor PIII 1000
Memory 265MB
Video NVIDIA 64MB
Windows XP
Zmud Version 6.34
Zmapper Version 1.10

Beginner Joined: 24 Aug 2002 Posts: 14 Location: USA

i entered the triger as you stated and reconfigured the mapper but it still does not inter the correct vnum into the automaper. what is parsing?

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

Two things to remember when using #TAG:

Every time you change/create a trigger that uses #TAG you need to Reconfigure the mapper so that the mapper notices the #TAG.

If you use #TAG on the room name, description, exits, etc. you must also always tag your prompt

Thus, aside from having the trigger that uses #TAG for the vnum, you need to also have another trigger that matches your prompt and does:
#TAG prompt

Afterwards, you must reconfigure the mapper so that it takes these #TAG's into account.

If the mapper still doesn't store the vnum when creating a new room after doing this, try e-mailing Zugg about it, as I think I have seen the mapper not work with respect to this before.

Kjata

Beginner Joined: 24 Aug 2002 Posts: 14 Location: USA

ok the protion of the sample room above
"vnum: 106" is the prompt would this cause some of the problem i am having?

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

It shouldn't be a problem. But it would be best if you #TAG the vnum and the prompt (even though they are the same line) in separate triggers, with the one that #TAG's the prompt firing second.

Kjata

Beginner Joined: 24 Aug 2002 Posts: 14 Location: USA

ok I have changed my prompt to look like this "< vnum: "the vnum" > and added the trigger
#TR {^<~>} {#TAG prompt} and still do not get the actual vnum in the mapper

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

Well, the pattern:
^<~>

won't actually match your prompt. Perhaps a pattern of:
^~<*~>

and make sure that the Trigger on Prompt option for that trigger is enabled.

If it still doesn't store the vnum when creating a new room, then, like I said, contact Zugg about this because I'm not really sure if there is a bug where the mapper simply won't capture the vnum.

Kjata