 |
Logun0 Newbie
Joined: 27 Jun 2003 Posts: 3 Location: Canada
|
Posted: Thu Aug 14, 2003 9:04 pm
Detecting Trigger Loops |
I am writing a bot script. Farily simple, it involes a few different classes of triggers in this order:
1)move into position to begin next script
2) enable fight script. - move one left, if specific mob is there, fight, else cycle through spell casting script. When mana depleted sleep regenerate, wake and move west to continue cycle.
3) Cannot move west anymore, disable 1st fight script (fightguard), move into position to begin the 2nd fight script (fightstudent)
4)enable fightstudent, same basic script as (2)
5) when you can't move anymore, recall and begin step (1) again.
Works great, however, I will get the occassional Trigger Loop Detected error. But I will never get this when I am around. My script will actually run for days at a time and then break. Sometimes it will run for days, but other times hours..
Is there anyway to set up a log to record the final few commands before this error happened? |
|
|
|
 |
TonDiening GURU

Joined: 26 Jul 2001 Posts: 1958 Location: Canada
|
Posted: Sat Aug 16, 2003 5:07 pm |
Something a la
#CAP History
#VAR HistoryLine {0} {0}
#ONINPUT {^(*)$} {#VAR LastOnInput %expand(%1, 1);#ADD HistoryLine 1;:history:@HistoryLine @LastOnInPut}
The idea is to capture things sent to the mud and show them in window or write them to a file. |
|
|
|
 |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|