Infiniteye
BANNED
I know there's a way and my buddy was telling me about it, but I have no idea how to set it up, is it done in holy shits? I'm using muleassist ihczerker kiss and mq2heals on my toons as far as macros and plugins go.
-
Hail, we're RedGuides. We want you to play six (yes, 6!) EverQuest characters at once. We have scripts and a friendly community to help, please join our playstyle and say hello! 👋
Question - How do I auto duck for things like the new mission that takes place in Kael?
- Thread starter Infiniteye
- Start date
What!? Sounds like a fantastic anti-boxer mechanic.
Sum1
Warriors are inferior (read: crybaby) tanks
it’s exactly what the raid does.
Ironically its the boxers on my server that succeeds. Somehow ducking is out out people's ability.
godsfshrmn
Well-known member
I plan to setup a gina trigger for this -- on a trigger you can copy something to your clipboard. So you would set it up as /bct {A} //keypress X. So each time an emote fires, you just hit your paste combo and you never need to leave your screen. Can probably work out something to stand --- holyshit to auto stand after 10 seconds?
If you have sathir's tomb raid triggers for the clues, you probably have an example there you can go by.
If you have sathir's tomb raid triggers for the clues, you probably have an example there you can go by.
Like a plugin that stores all the stuff for events like this Wish we could, I have not learned how to use the event thingie yet. I bet it would be powerful.
I played around with it for announcing CC, worked pretty good. Does anyone have the exact text for the initial emote and also for the all clear emote x seconds later ?
Something like
Code:
#event DuckOn "#*#The ice encrusted Avatar of War shouts that #1# must bend the knee!#*#"
#event DuckOff "#*#The Avatar of War nods, accepting the subservience of those that gave it.#*#"
Sub Event_DuckOn(line, player)
/if (!${Defined[duckOn]}) /declare duckOn int outer 0
/if (${player.Equal[${Me.Name}]}) {
/varset duckOn 1
}
/if (!${duckOn}) {
/doevents flush DuckOn
/return
}
/while (${duckOn}) {
/if (!${Me.Ducking}) /keypress duck
/delay 1
/doevents
}
/doevents flush DuckOn
/return
Sub Event_DuckOff
/if (!${Defined[duckOn]}) {
/declare duckOn int outer 0
} else {
/varset duckOn 1
}
/doevents flush DuckOff
/return
Last edited:
Where do I put this, I will be more then happy to test it!
INI:
[kaelduck]
trigger="The ice encrusted Avatar of War shouts that #1# must bend the knee!"
command=/if (${Me.CleanName.Equal[${EventArg1}]}) /multiline ; /mqp on; /stopcast; /gsay ducking is for living beings; /target ${Me.Name}; /attack off; /timed 20 /keypress duck;
[kaelstand]
trigger="The Avatar of War nods, accepting the subservience of those that gave it."
command=/if (${Me.Ducking}) /multiline ; /stand; /gsay phew still got my head.. checking!; /mqp off;
INI:
[kaelduck]
trigger="The ice encrusted Avatar of War shouts that #1# must bend the knee!"
command=/if (${Me.CleanName.Equal[${EventArg1}]}) /multiline ; /mqp on; /stopcast; /attack off; /timed 20 /keypress duck;
[kaelstand]
trigger="The Avatar of War nods, accepting the subservience of those that gave it."
command=/if (${Me.Ducking}) /multiline ; /stand; /mqp off;
Last edited:
for events ? mq2events
- Commits
- 191
multiline is a lil finnicky.
Code:
/multiline ; /mqp on; /stopcast; /gsay ducking is for living beings; /target ${Me.Name}; /attack off; /timed 20 /keypress duckAfter /multiline you need a space before and after ; after that, all lines need to end with ; without a space after the command, and have a space following the use of ;
Your spacing on the above command is all over the place. After /mqp on ; you have two spaces, and there is a space after the mqp on. Same with your /timed command, it has two spaces prior to the command.
Also, you have a lot of fluff in the multiline. That should work provided it gets cleaned up.
Cleaned up, took out fluff. how is the review score now ? Don't think the mqp is needed either ?
Should not hurt either as I don;t know what others will be running
- Commits
- 191
the /mqp may be needed, since this is a plugin driven event system using the mqp will assist with group members running a macro like KA.
so the key to this event, in addition to following the emotes, is to go slow dps on the boss and kill adds as they spawn. Adds spawn approximately every 5% and boss has low hp so it's easy to get overrun. However, the boss does an AOE that does 25% damage to all nearby adds. So he helps you, in a way, there's even an achieve for letting the boss kill all of his own adds.
Addict
Well-known member
For the unducking, I think this should work with only a small change:
Why not just go the simple route and do this:
Or do the macros/plugins discussed here have a check for invalid combat states and automatically unduck if it is detected, thus forcing a while loop to wait?
Code:
/if (!${duckOn}) {
/if (${Me.State.NotEqual[STAND]}) /stand
/doevents flush DuckOn
/return
}
....
Sub Event_DuckOff
/if (!${Defined[duckOn]}) {
/declare duckOn int outer 0
} else {
/varset duckOn 0
}
/doevents flush DuckOff
/returnWhy not just go the simple route and do this:
Code:
#event DuckOn "#*#The ice encrusted Avatar of War shouts that #1# must bend the knee!#*#"
Sub Event_DuckOn(line, player)
/if (${player.Equal[${Me.Name}]}) {
/if (!${Me.Ducking}) /keypress duck
}
/doevents flush DuckOn
/return
#event DuckOff "#*#The Avatar of War nods, accepting the subservience of those that gave it.#*#"
Sub Event_DuckOff
/if (${Me.State.NotEqual[STAND]}) /stand
/doevents flush DuckOff
/returnOr do the macros/plugins discussed here have a check for invalid combat states and automatically unduck if it is detected, thus forcing a while loop to wait?
Last edited:
You're right here. A bit of a copy n paste kind of error. The Duck Off was setting Duck to be on, not off:-
For the simple route you suggest I don't think it would work, I suspect most macro's will un-duck you to cast spells etc as soon as you exit the DuckOn sub routine. So you'd probably duck, then unduck almost immediately, hence why the loop.
So for copy and paste-ability:-
For the simple route you suggest I don't think it would work, I suspect most macro's will un-duck you to cast spells etc as soon as you exit the DuckOn sub routine. So you'd probably duck, then unduck almost immediately, hence why the loop.
So for copy and paste-ability:-
Code:
#event DuckOn "#*#The ice encrusted Avatar of War shouts that #1# must bend the knee!#*#"
#event DuckOff "#*#The Avatar of War nods, accepting the subservience of those that gave it.#*#"
Sub Event_DuckOn(line, player)
/if (!${Defined[duckOn]}) /declare duckOn int outer 0
/if (${player.Equal[${Me.Name}]}) {
/varset duckOn 1
}
/if (!${duckOn}) {
/doevents flush DuckOn
/return
}
/while (${duckOn}) {
/if (!${Me.Ducking}) /keypress duck
/delay 1
/doevents
}
/if (${Me.State.NotEqual[STAND]}) /stand
/doevents flush DuckOn
/return
Sub Event_DuckOff
/if (!${Defined[duckOn]}) {
/declare duckOn int outer 0
} else {
/varset duckOn 0
}
/doevents flush DuckOff
/return
Last edited:
Corrected- it should be in the duckOn sub though, after it exits the waiting-for-duckOff loop.
Interim solution whilst you guys create the real deal
I set up 5 hotkeys for my toons that I control from my main;
Kissassist toons:
/bct (name) //mqp
/bct (name) //keypress ESC
/bct (name) //keypress D [or whatever duck key you have assigned]
Press key again when safe after successful emote.
MQ2 berserker - make sure auto stand on duck is switched off!
/bct (name) //Zerk mode 0
/bct (name) //keypress ESC
/bct (name) //keypress D [or whatever duck key you have assigned]
Press key again when safe after successful emote and then use /bct (name) //zerk mode 1 key to ré-engage!
Good luck!
I set up 5 hotkeys for my toons that I control from my main;
Kissassist toons:
/bct (name) //mqp
/bct (name) //keypress ESC
/bct (name) //keypress D [or whatever duck key you have assigned]
Press key again when safe after successful emote.
MQ2 berserker - make sure auto stand on duck is switched off!
/bct (name) //Zerk mode 0
/bct (name) //keypress ESC
/bct (name) //keypress D [or whatever duck key you have assigned]
Press key again when safe after successful emote and then use /bct (name) //zerk mode 1 key to ré-engage!
Good luck!
0ptic
Member
Now the toons duck and un duck and duck and unduck. Then Die
Just tested
Same here, they won't stay ducked.