|
Sir1l Wanderer
Joined: 01 Oct 2005 Posts: 54
|
Posted: Sun Jun 24, 2007 11:45 pm
On top.... |
i can't think of an easy way of doing this, or making it nice, but here it goes....
i want to stay on top of the mobs, but when the area repops the mobs are ahead of me in battle so it's like this.
Hitpoints: 564 Mana: 300
The hideous dragon hits you with atomic severity.
Your attack hits the hideous dragon with annihilating brutality.
Prompt again.....
And what I want is me on top and if Im not on top it will relog....The best way I was thinking is set a varialbe that checks after each prompt and checks it each time... |
|
|
|
Fang Xianfu GURU
Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Mon Jun 25, 2007 10:55 am |
So you want to check if the "Your attack..." line follows a prompt, and it doesn't, #con to log back into the game? How about this?
#trig {Hitpoints: (%d)%sMana: (%d)} {} "" {prompt|nocr}
#cond {^(*)$} {#if (!%begins(%1,"Your attack")) {#connect}} |
|
|
|
Sir1l Wanderer
Joined: 01 Oct 2005 Posts: 54
|
Posted: Tue Jun 26, 2007 3:18 pm |
Oh tnak you!!!!!
|
|
|
|
Sir1l Wanderer
Joined: 01 Oct 2005 Posts: 54
|
Posted: Wed Jun 27, 2007 3:44 am |
Hmm, actually I'm having a little problem, I want it to reconnect only if this shows
%1 attacks strike you with terminal brutality!
I can't get this to capture with changing the Your attack to this :( |
|
|
|
Fang Xianfu GURU
Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Wed Jun 27, 2007 9:06 am |
Yes, that's because it's checking if the line DOESN'T start with "Your attack". Just add it to the pattern of the trigger:
#trig {Hitpoints: (%d)%sMana: (%d)} {} "" {prompt|nocr}
#cond {attacks strike you with terminal brutality!$} {#connect} |
|
|
|
Sir1l Wanderer
Joined: 01 Oct 2005 Posts: 54
|
Posted: Wed Jun 27, 2007 3:39 pm |
Hmmm, this is really word, now it's like reconnect on everything after the prompt :(
|
|
|
|
Fang Xianfu GURU
Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Wed Jun 27, 2007 3:48 pm |
Make sure you delete the first trigger - the first one will fire on everything that doesn't start with "your attack" and so is the most likely culprit.
Oh, and I also forgot to mention - the condition in the trigger I posted above should be a Within Lines trigger and have the parameter set to 1. |
|
|
|
|
|