Zugg Software :: View topic

Newbie Joined: 17 Feb 2004 Posts: 6

For quite some time now I've had a problem with random classes appearing with names of things I've recently typed. [:I] I assume this is a basic error within my settings, caused most likely by a stupid typo somewhere... But, any help, such as a command besides #class to be searched for within my settings - I already searched for every #c used within my triggers, nothing that would do this was to be found - would be greatly appreaciated.

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

This is usually caused by not using the proper delimiters when creating triggers, aliases, variables, or other settings. This is especially true when you make these settings with a trigger using * or other multi-word wildcards.

The syntax is:
#TRIGGER [id] pattern command [classname] [options]
#ALIAS [aliasname] [string] [classname]
#VARIABLE [variable] [value] [defaultval] [classname]
As you can see, all these commands allow you to assign the setting to a particular class, and they will create that class if it doesn't already exist.

So, a trigger such as:
#TR {(*) hits you hard!} {#VAR target %1}
will work fine with a one-word assailant, such as LightBulb. However, if there are two words, such as Light Bulb, the value will be Light and Bulb will be the default-value. With three words, such as LightBulb the Illuminary, you not only get an undesired default-value (the) but also an undesired class (Illuminary).

To prevent this, just use the appropriate delimiters, usually braces {}.
#TR {(*) hits you hard!} {#VAR target {%1}}