- This topic has 19 replies, 10 voices, and was last updated 6 years, 8 months ago by
Ragùneraxe.
-
I keep ironskin always and usually have 1-2 extra to purify after lash/shatter. It doesnt remove much of a stagger tho in BfA.
-
My appologies way ahead, since I feel I will mess up the quotations.
Any special reason? Might be easier to focus on adds cleanup instead since the second trash spawn is supposed to be the hard one, not the third group.
The reason why people aim to push the boss to the second phase to minimize add management, eventhough the third spawn isn’t as tricky as the second one. Since it was mentioned that our DPS might be a bit low I assumed that we are aiming to go for the third add group skip, otherwise our DPS seems fine to deal with the third add group.
Tried swapping tanks, so that Rag is taking that overlap instead?
Not yet. We can try though.
Should be possible to drag boss from the regular tank spot closer to one end of the room for the Surging Darkness/Roiling Deceit overlap when there’s no big add spawn coming in, or even with the adds, but CC all three. Also surviving the Surging Darkness hit should be possible with 50% damage reduction cooldown. Or even outright sacrifice the person running out instead of getting extra adds that will fuck you over much worse.
The problem with Roiling Deceit is that if the target dies that player is out of the game permanently. On quite a few of our tries if a target dies while having Deceit and drops it a battle res will mean that the ressed player will activate Deceit and we get an add. Since not many classes have 50% damage reduction (I assume the majority of classes work with around 30% DR) an immunity or a personal+external CD is the solution.
If you check the video you can see what I mean with the positioning: The boss is in the middle of the three markers, and with that 2 out of 3 circles of the Surging Darkness free spots reach the wall, minimizing the RNG it has on the fate of the target of the first Deceit. If we tank it at the middle area only one, the external circle, reaches the walls so the first target of Deceit will have a hard time dropping it in a desired position without dying.
The video also says adds management is hardest part of the fight, so it should be the part to focus on. Including fixing things related to adds management like who dps’es what and when.
Yes, I think we just need to set down who does what (in this case all we need is melee to stay on the silithids) and we should be fine.
Brewmaster’s strength is smooth damage intake, and they require constant healing. This is a tradeoff, i dont die to big hits and you heal me all the time. If monk not getting healing, that means we as a raid not using brewmaster at its full potential. Look at methos’s kills, they using 2x brewmasters, their health yoyos like mad and they getting constantly bombed with heals, otherwise heavy stagger will kill them. I am not telling that i cannot play better, i absolutely can, but i cannot enter combo on Zek with 20-50% HP as it routinely happening on our tries. When i start taking it at the start of the fight, healers not moving and i am topped, i can take it with zero issues. I am also thinking that healers got maybe little bit too comfortable with Rag and DK self healing. We can split combo (taunt atfter shatter), in that case 2 tanks will have 50% healing reduction for a period of time instead of 1 tank having 100% healing reduction. That is something we should try and agree on, which is better for our team. Also i would like to apologize to our healers for last raid, i was not feeling well and got angry over dying all the time. I did not mean anything malicious. I am sorry if i was rude.
I think the problem here stems from your defensive, Stagger. Until we get to the point where the Surging Darkness is cast your HP is fine, moves between 80% and 90% from the replays I have checked. Do keep in mind that by this time your Stagger is most likely hovering between yellow and red which the healers can handle while they are stationary. During this Darkness however we are getting eye-beams too. Healers not only need to move, but also spread out because of the beams. Some might not be in range to heal you, and without multiple healers chipping in and most likely throwing a stronger CD like AW from Kodis into the mix. Most will have time to fire off a spell and an instant while moving between the rings.
Either we can try swapping after shatter, or maybe we can try with you starting tanking. That way Rag will be tanking on the problematic overlap, which should be a good safety net in case the out of range healer problem hits in. Alternatively I should try and pay more attention and make sure I top you up with Lay-on before the combo hits, if not you can try calling it out. I am also not sure if the talent Guard can help on this situation. It has a 30 second CD, and should ignore about 80K damage at your itemlevel (not sure of the exact number, my monk is only 110.)
-
When i start taking it at the start of the fight, healers not moving and i am topped, i can take it with zero issues. I am also thinking that healers got maybe little bit too comfortable with Rag and DK self healing.
Not necessarily, I cannot speak for other healers but being a slow tower healer there is a few things that in general is borking me over when it comes to healing the tanks:
- My spot healing is not great (got two instants and those don’t heal for a huge amount)
- Positioning as I mentioned, I often find myself needing to be away from the tanks (because people run to the back of the room and require healing). Not wanting to bite into our DPS but if you got some self healing please use it when you move out with Deceit cause often you will be out of our healing range and force me to reposition often to deal with that.
I do plan to change up my talents a bit for more tank healing and shift my focus on general raid healing to Tank healing and positioning better.
-
I tried Guard on several tries. Tradeoff is i have to give up High Tolerance which is vary big survivability increase.
Problem is not combo itself. Problem is that i am entering combo low on HP, at this point cooldowns will not do much.
-
I’ve read over the suggestions and feedback from everyone on this thread. Thank you for taking the time to post and comment on this thread and to do your parts to try and overcome the boss together as team. More minds are better than one, as they say.
As of right now, changes to the fight this weekend following certain suggestions in this thread will be as follows:
- Bragfist will be tanking the boss for the entirety of each Might of the Void combo, taking both Void Lashes and the Shatter each time. I will be tanking the boss for the majority of the fight and will never tank a combo. As per Chi’s suggestion, we can do the fight this way by maximizing the usage of both of our tanks’ toolkits – Monks incredibly ability to stagger a lot of damage in a small window and BDK’s ability to take a constant beating and always heal up from it but without too much of a spike like the combos give.
- We said this last weekend, but it will be official this time: in the 2nd add phase + Surging Darkness pools overlap we will be focusing on burning down the entirety of the small adds and the 1 Voidweaver under the boss before the pools come in. During Surging Darkness we avoid all the void zones and unload all damage onto the boss while the other 2 adds remain CC’d. We swap and kill them in same order (Purple > Orange) once the pools stop spawning.
- The boss will be positioned on Skull in the middle of the room prior to each Surging Darkness by the active tank to make sure the pools spawn in a predictable and consistent location each time, regardless of the phase or overlap we’re in.
Changes to your builds, talents and other finer details you will need to look into yourselves and make sure you’re running the optimal build for this fight relevant to your spec. We will need to find a balance between Boss damage & Add damage and hopefully we can get him in to Phase 2 at 40% with only 2 add phases as this is the ideal way to go.
Thanks again everyone and lets kill this bug(ger)!
You must be logged in to reply to this topic.