-
You've discovered RedGuides, an EverQuest multi-boxing and scripting community 🧙♀️⚙️. We want you to play several EQ characters at once, come join us and say hello! 👋
Question - Raid - High Priest Yaran
- Thread starter Mikey02
- Start date
Right now whenever I get 8
Thanks, didn't realize all the mechanics were hp based. Was getting overwhelmed with adds and mechanics.
- Joined
- Feb 9, 2017
- RedCents
- 1,377¢
Keep at it. Practice makes almost perfect.
Many_Whelps
WoW was the first MMO
- Joined
- Jul 22, 2018
- RedCents
- 762¢
Positioning the flying adds is extremely important. They do a frontal AE, 180 degree arc, very long range that dots everyone it hits and it is brutal enough that it will kill characters outright without massive AOE healing going down. If you let that hit your entire raid force, you're most likely already wiped.
Then the boss has to be turned front to back on a specific cadence all fight long. He does a frontal 180 AE and then follows it up with a rear 180 AE a few seconds later. He repeats that cycle every 60-70 seconds or so. We put the boss into the corner facing a wall. The tank would flip the boss when the rear AE was about to land and then reposition the mob to face the corner again. Until you're geared up on ToB raid gear, any missed mechanic is almost a guaranteed wipe. If you're doing this in LS raid gear, you basically have to be perfect.
Then the boss has to be turned front to back on a specific cadence all fight long. He does a frontal 180 AE and then follows it up with a rear 180 AE a few seconds later. He repeats that cycle every 60-70 seconds or so. We put the boss into the corner facing a wall. The tank would flip the boss when the rear AE was about to land and then reposition the mob to face the corner again. Until you're geared up on ToB raid gear, any missed mechanic is almost a guaranteed wipe. If you're doing this in LS raid gear, you basically have to be perfect.
I’d say this fight is arguably harder with new lvl, gear and higher dps, especially if you have a lot of dots classes like bst and necro. Everytime im working on the adds, the dot push the boss to threshold and all the sudden 1/3 of my raid is running for cure, or my tanks has to interrupt their kiting loop to cure. The mechanics are unforgiving when they overlap.
I just don’t see any benefit farming this raid once I get my achievements. The fight is long and usually wipe tends to happen when the messenger comes. Still have yet to come up with a good solution to mez those messenger to get my achievement.
I just don’t see any benefit farming this raid once I get my achievements. The fight is long and usually wipe tends to happen when the messenger comes. Still have yet to come up with a good solution to mez those messenger to get my achievement.
Couple things. First, turn DoT'ing off for all classes. Sure you lose some DPS, but who cares, its all about control, not speed.
Second, this is a quick, unoptimized, horribly written LEM event that works "good enough." It really should be toggling through nearest spawns,, storing ID's and doing a whole bunch of other optimized stuff, but I'm not spending anymore time on that raid. I've done it with as few as 2 chanters with this. I put a low level, low mana cost DoT in Gem 5. To make this work, my runaways return my enchanters, and any priest in the enchanter group to a spot over by the door once HP is 40% or lower. This of course only works on the 39% runaway, so I move them manually if I'm doing kill the body. They get there on their own if not doing kill the body.
Code:
cmV0dXJuIHsKIFsidHlwZSJdID0gImNvbmRpdGlvbnMiLAogWyJsb2FkIl0gPSB7CiAgWyJhbHdheXMiXSA9IGZhbHNlLAogIFsiem9uZSJdID0gIiIsCiAgWyJjbGFzcyJdID0gIiIsCiB9LAogWyJjYXRlZ29yeSJdID0gIk91dGVyIEJyb29kIiwKIFsibmFtZSJdID0gIk1lc3NlbmdlcnMiLAogWyJjb2RlIl0gPSAiYkc5allXd2diWEVnUFNCeVpYRjFhWEpsS0NkdGNTY3BDZ3BzYjJOaGJDQm1kVzVqZEdsdmJpQmpiMjVrYVhScGIyNG9LUW9nSUNBZ2NtVjBkWEp1SUcxeExsUk1UeTVPWldGeVpYTjBVM0JoZDI0b0owMWxjM05sYm1kbGNpQnVjR01uS1M1TWFXNWxUMlpUYVdkb2RDZ3BJR0Z1WkNCdGNTNVVURTh1V205dVpTNVRhRzl5ZEU1aGJXVW9LU0E5UFNBbloybHNaR1ZrYzNCcGNtVmZjbUZwWkNjS1pXNWtDZ3BzYjJOaGJDQm1kVzVqZEdsdmJpQmhZM1JwYjI0b0tRb0piWEV1WTIxa0tDY3ZaVzVqSUdOaGJYQnlZV1JwZFhNZ01TY3BDZ2xwWmlCdGNTNVVURTh1VTNCaGQyNG9KMDFsYzNObGJtZGxjaUJ1Y0dNbktTNUlaV0ZrYVc1bktDa2dQVDBnSjBVbklHOXlJRzF4TGxSTVR5NVRjR0YzYmlnblRXVnpjMlZ1WjJWeUlHNXdZeWNwTGtobFlXUnBibWNvS1NBOVBTQW5VeWNnZEdobGJnb0pDV2xtSUcxeExsUk1UeTVPWldGeVpYTjBVM0JoZDI0b0owMWxjM05sYm1kbGNpQnVjR01uS1M1TmIzWnBibWNvS1NCMGFHVnVDZ2tKQ1cxeExtTnRaQ2duTDJWdVl5QndZWFZ6WlNCdmJpY3BDZ2tKQ1cxeExtTnRaQ2duTDJWeGRHRnlaMlYwSUcxbGMzTmxibWRsY2ljcENna0pDVzF4TG1SbGJHRjVLRFF3TUNrS0NRa0piWEV1WTIxa0tDY3ZZMkZ6ZENBekp5a0tDUWtKYVdZZ2JYRXVWRXhQTGxSaGNtZGxkQzVFYjNSMFpXUW9LU0E5UFNCdWFXd2dkR2hsYmdvSkNRa0piWEV1WkdWc1lYa29NelV3TUNrS0NRa0pDVzF4TG1OdFpDZ25MMk5oYzNRZ05TY3BDZ2tKQ1dWdVpBb0pDV1Z1WkFvSlpXNWtDZ2xwWmlCdGNTNVVURTh1VTNCaGQyNG9KMDFsYzNObGJtZGxjaUJ1Y0dNbktTNUlaV0ZrYVc1bktDa2dQVDBnSjBVbklHOXlJRzF4TGxSTVR5NVRjR0YzYmlnblRXVnpjMlZ1WjJWeUlHNXdZeWNwTGtobFlXUnBibWNvS1NBOVBTQW5VeWNnZEdobGJnb0pDV2xtSUcxeExsUk1UeTVPWldGeVpYTjBVM0JoZDI0b0owMWxjM05sYm1kbGNpQnVjR01uS1M1TmIzWnBibWNvS1NBOVBTQm1ZV3h6WlNCMGFHVnVDZ2tKQ1cxeExtTnRaQ2duTDJWdVl5QndZWFZ6WlNCdmJpY3BDZ2tKQ1cxeExtTnRaQ2duTDJWeGRHRnlaMlYwSUcxbGMzTmxibWRsY2ljcENna0pDVzF4TG1SbGJHRjVLRFF3TUNrS0NRa0piWEV1WTIxa0tDY3ZZMkZ6ZENBMUp5a0tDUWxsYm1RS0NXVnVaQW9KYlhFdVpHVnNZWGtvTXpVd01Da0tDVzF4TG1OdFpDZ25MMlZ1WXlCd1lYVnpaU0J2Wm1ZbktRcGxibVFLQ25KbGRIVnliaUI3WTI5dVpHWjFibU05WTI5dVpHbDBhVzl1TENCaFkzUnBiMjVtZFc1alBXRmpkR2x2Ym4wPSIsCn0=
Lua:
local mq = require('mq')
local function condition()
return mq.TLO.NearestSpawn('Messenger npc').LineOfSight() and mq.TLO.Zone.ShortName() == 'gildedspire_raid'
end
local function action()
mq.cmd('/enc campradius 1')
if mq.TLO.Spawn('Messenger npc').Heading() == 'E' or mq.TLO.Spawn('Messenger npc').Heading() == 'S' then
if mq.TLO.NearestSpawn('Messenger npc').Moving() then
mq.cmd('/enc pause on')
mq.cmd('/eqtarget messenger')
mq.delay(400)
mq.cmd('/cast 3')
if mq.TLO.Target.Dotted() == nil then
mq.delay(3500)
mq.cmd('/cast 5')
end
end
end
if mq.TLO.Spawn('Messenger npc').Heading() == 'E' or mq.TLO.Spawn('Messenger npc').Heading() == 'S' then
if mq.TLO.NearestSpawn('Messenger npc').Moving() == false then
mq.cmd('/enc pause on')
mq.cmd('/eqtarget messenger')
mq.delay(400)
mq.cmd('/cast 5')
end
end
mq.delay(3500)
mq.cmd('/enc pause off')
end
return {condfunc=condition, actionfunc=action}I actually had to turn off the dots below 75% to make the fight more manageable.
I hadn’t thought about using DOT to break the mez. Currently i have a bard meleeing the messenger and mezzing them. This seems like it’ll be more reliable since I am not checking for extra conditions to get them off of the fleeing messengers. Appreciate it.
I hadn’t thought about using DOT to break the mez. Currently i have a bard meleeing the messenger and mezzing them. This seems like it’ll be more reliable since I am not checking for extra conditions to get them off of the fleeing messengers. Appreciate it.
I see you said you are doing via kiting, we don't kite in our setup. we have 4 spots evenly spaced around the boss all within range of healers but all > 150 apart, when the adds come the tanks tag and move to position causing all adds to be pointed away from each other and boss. we then just kill from bottom up and return to boss.
for the messengers we pretty much do the same thing as Darkwynd3's lem above, except we use all bards and enchanters, if your using all them you can turn the add almost immediately. Also Enchanters have 2 mezzes that overwrite and can be cast very fast counting as 2 of the 3 hits.
for the messengers we pretty much do the same thing as Darkwynd3's lem above, except we use all bards and enchanters, if your using all them you can turn the add almost immediately. Also Enchanters have 2 mezzes that overwrite and can be cast very fast counting as 2 of the 3 hits.
At the time i wrote my script, my tanks were severely under geared so kiting was my best option. I may revisit it but for now kiting works for me.
I think once I solve the messenger issue, the fight will be trivialized. Really appreciate the feedbacks and tips.
I think once I solve the messenger issue, the fight will be trivialized. Really appreciate the feedbacks and tips.
Why bother spacing out the flying mobs? You can stack them on each other since their AE is a frontal DOT, both flying mob tanks will only get 1 DOT on them.
This way you have less running around and able to do some AE dmg => more overall dps.
We only have 2 drivers, 1 is 100% busy with controlling the boss. the other is the MA for the entire raid. The OT's are fully automated, and when the adds come in they don't come the exact same order every time. so we found it easiest and safest to just spread them out and never have an issue. if you have drivers to actually control the tanks, this raid would be one of the easiest in the expansion to do. (we just don't have that)
Yeah, this raid with 5 people would be cake. We do it with two. OT’s on a button, boss flips automated.
I have a button that sends my OT’s rather than a script. Hence, OT’s on a button.
What kind of a hotkey? Just a /dtell toonname /nav loc?
Yeah, sets them mode 0, sends them to mob, turns attack on, casts an aggro ability, then pulls the mob to its location - lengthy multiline. One key has all 4 OT's on it.
No. You get just the two rectors alone at 40%. You need to really manage DPS as cures occur at 39%.
Correct - cure/run-aways. You obviously don’t want that 39% cure happening while the rectors are up.
Priest %
99 - 2 flying acolytes + 1 rector
81 - 2 ground acolytes + 1 rector
75 - cures (11 to each spot)
69 - cures (11 to each spot)
63 - cures (11 to each spot)
59 - 4 acolytes
57 - cures (11 to each spot)
51 - cures (11 to each spot)
51 - 4 acolytes
45 - cures (11 to each spot)
43 - 4 acolytes
40 - Messengers start (Rectors if doing Kill the Body)
39 - cures (11 to each spot)
35 - 4 acolytes
33 - cures (11 to each spot)
27 - cures (11 to each spot)
27 - 4 acolytes
21 - cures (11 to each spot)
19 - 4 acolytes
15 - cures (11 to each spot)
11 - 4 acolytes
9 - cures (11 to each spot)
3 - cures (11 to each spot)
3 - 4 acolytes
Amazing! Thank you for writing this out.
Maybe in 5 expansions with an SK?