Zugg Software :: View topic

Beginner Joined: 28 Nov 2012 Posts: 16

Hi,

I'm gonna sounds terribly stupid here but I have been reading and experimenting for hours now and i just nt getting anywhere.

My mud the autoconfigure inst working so im trying to add #tag commands.

Here is my mud output..

Wizard Joined: 22 Mar 2007 Posts: 2320

Yes, that trigger should work. It would set the entire line as the Name field for the room. You are not as confused as you fear.

If you wanted to get rid of the "-=" and "=-" at either end of the name, you could try this:

Posted: Wed Dec 05, 2012 4:51 pm

that looks about right.

although @aura in a pattern will be looking for the value of your aura variable to be in the string the trigger is matching on
if you need a literal @ symbol you should quote it out with a tilde ~@

a trigger is merely a coded attempt to match strings, to perform an action

just remember to reconfigure the mapper after each #TAG trigger, you may not need to tag everything, just the stuff it has trouble understanding

Beginner Joined: 28 Nov 2012 Posts: 16

Thanks both, that's really helpful. I made the changes you suggested rahab and it pucks out the room name but puts the exits as the description. Ill have to try to find some examples from other people on how to add the description and exits.

i am not sure i understand about the prompt, i just added that in the mud so it would have something easy to latch onto but i cab rrmkve that. Do you think that would be better having the prompt start as "Aura xxxx"?

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

That is basically right, but there are a few considerations to think about.

1)* matches anything your keyboard can print, with the obvious exceptions being keys like backspace, delete, enter, and the various other cursor-control characters. In all cases, you can use [] as a replacement with any wildcards or literal characters between the [] that you want to match on. For example, room names typically only have letters, spaces, and perhaps a very limited set of punctuation (ie, ,.?!-) so such a pattern would be[%w%s,.?!-] (note that because - has a special function inside [] it has to be the first or the last character listed.)

2)make use of ^ and $. These will prevent players from spoofing lines, as well as simply preventing your triggers from firing on stuff innocently show on channels or other speech locations.

3)Some games wrap room names in some sort of unique text to better allow triggers to identify them. This unique text is typically not included in other game features and player abilities that display room names, so it'll be unnecessary to include them in your map info. The way to exclude them is to surround the wildcard portion of the pattern in parentheses and then reference the appropriate %1...%99 variable in your #tag command: #tag name %1.

4)@ is a special character meaning that what follows is a variable name. You probably have an Aura variable, but I'm betting you want your prompt trigger to match on the literal word of "@Aura:". Use ~ (the quote character) to literalize it.

5)room info tends to come in a specific pattern, so you may want to look into the use of multistate triggers. Multistate triggers are basically just a whole set of individual triggers that are locked into a group, with CMud automatically controlling when each state gets activated. They can make matching on several lines easier and cleaner, since you don't have to worry about using commands like #T- and #T+ AND you can use %t1...%t99 to refer to captured elements from previous trigger states (it's almost like being able to reference local variables across separate settings objects).

Beginner Joined: 28 Nov 2012 Posts: 16

This is all great into thanks guys, especially the bits on the @ sign in the prompt.

i will now research multistate triggers to try to sort out the exits now.

i also guess that i need to do a new configuration in the mapper so it can forget old config and use the new tags

Posted: Wed Dec 05, 2012 7:08 pm

dont forget to make sure your prompt trigger has 'trigger on prompt' checked and not newline

Beginner Joined: 28 Nov 2012 Posts: 16

im gonna give up on this, i cant find a way to match the room names without the -= =- despite the tips, i cant match the multiline description - all the mapper pics up for the description is the exits and the exits i dont even know how to start finding a multistated trigger int he options. I think ill have to make do with a crappy workign mapper and leave the tinkering to you guys.

Was interesting though but too complex for me.