 |
Craivus
Novice
Joined: 24 Jan 2001
Posts: 47
|
|
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
 Posted: Fri Apr 18, 2003 11:55 pm
|
quote:
The topic says it all... how do you do it best ?
With triggers--specifically, state triggers.
li'l shmoe of Dragon's Gate MUD |
|
|
|
|
Craivus
Novice
Joined: 24 Jan 2001
Posts: 47
|
Posted: Sat Apr 19, 2003 12:46 am
|
OK, guess I wasn't descriptive enough, as I did not elicit a helpful response.
I want to trigger on the next line received from the mud, no matter what the line contains, as a form of lag compensation. How exactly do I do this? |
|
|
|
|
LightBulb
MASTER
Joined: 28 Nov 2000
Posts: 4817
Location: USA
|
Posted: Sat Apr 19, 2003 1:23 am
|
#COND
The Wait type would probably be a good choice.
LightBulb
Advanced Member |
|
|
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Sat Apr 19, 2003 3:46 am
|
quote:
OK, guess I wasn't descriptive enough, as I did not elicit a helpful response.
I want to trigger on the next line received from the mud, no matter what the line contains, as a form of lag compensation. How exactly do I do this?
Well, I imagine a simple * pattern in the #CONDITION statement (these are the states of your triggers, after the initial state provided for in the #TRIGGER command) would work nicely to match any line in the MUD.
li'l shmoe of Dragon's Gate MUD |
|
|
|
|
|
|
|
