Zugg Software :: View topic

Beginner Joined: 01 Sep 2003 Posts: 19 Location: USA

I searched the forums and found info about VARs being created in the wrong class, but I have an alarm doing it.

I have this alarm not in any class:

#TR {exit|exits} {#ALA +0.5 {#OK}}

However, the ALA is being created in one of my classes. I didn't realize this because it was working fine...until I disabled that class.

I use the ALA to prevent spamming directions while speedwalking via the mapper. Imperian doesn't like spam. But, I hadn't used speedwalk in a while, so I didn't notice any problems.

I later accessed that class via the Editor to drag out some TRs and too my surprise there were over 200 copies of this ALA waiting to fire! Very Happy

So, why was the ALA being created in that class? Is it the same reasoning as the VAR problem?

NOTE: The original TR was created via the Editor. I deleted it and recreated it via the command line. The ALA is no longer created in that class.

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

Sounds like you found the solution.

Temporary alarms are automatically assigned an ID unless you specify one. This is to allow different triggers to make one-time alarms with the same pattern (+1 for instance) but different start-times and actions. It has the side-effect that you can accumulate large numbers of these alarms if they aren't allowed to finish processing and delete themselves. I don't know why yours were being made in that class, it's probably something in the code for the #CLASS default-class option.

You should note that the shortest time allowed in version 6.62 is .501

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

You can always specify what class you want to alarm to go into.

#TR {exit|exits} {#ALA +0.5 {#OK} classname}