Zugg Software :: View topic

Newbie Joined: 05 Apr 2005 Posts: 8

I have a "scan" alias that enables a Scan class which includes a number of triggers for parsing "scanned" information. I have setup a second trigger which will disable the Scan class once the room scan has completed. These things work properly, however I have noticed that sometimes the Scan class is not enabled or disabled fast enough, causing the Scan triggers to either fail or trigger when they are supposed to be deactivated.

Here is an example of the MUD output as a result of my SCAN alias.

< 1603h/1508H 283v/284V Pos: standing >SCAN
You quickly scan the area.
A Barbarian who is not far off to your north.
A Half-Elf who is not far off to your north.
A Half-Elf who is not far off to your north.
A Human who is not far off to your north.
A Human who is not far off to your north.
A Human who is not far off to your north.
A Grey Elf who is not far off to your north.
A Centaur who is not far off to your north.
A Grey Elf who is not far off to your north.
A Human who is not far off to your north.
A Grey Elf who is not far off to your north.
< 1603h/1508H 283v/284V Pos: standing >

My alias and trigger are:
alias {sc}{#T+Scan;SCAN}
trigger {< (*)h/(*)H (*)v/(*)V Pos: (*) >}{#T- Scan}

Just to clarify this setup does work correctly, it is just the timing that is sometimes the issue. Any thoughts?

Thanks

Wizard Joined: 17 Jun 2006 Posts: 1201

Is that #T+SCan how you have it in your script because there is no space.

Newbie Joined: 05 Apr 2005 Posts: 8

It has a space in the real alias, typo on my part.

Wizard Joined: 22 Mar 2007 Posts: 2320

I don't see how it is possible for there to be a problem as you describe it. In your alias for sc, the #T+ has to complete before running the SCAN command. The #T+ does not start a separate thread; the SCAN cannot run until #T+ finishes. Can you describe what you see happening in more detail? Are there any other triggers or aliases which affect this class?

I can see two possible issues regarding turning off the class. First, double check that the trigger is set to Trigger on Prompt, instead of Trigger on Newline. Second, perhaps there are other triggers with a higher priority which catch the prompt before this trigger turns off the class. Changing the priority would fix that.