You hide what boss your talking about by using their real names. Orbus is famous for giving names that I can for the life of me not couple to a picture of the enemy. Its too cryptic.
I read it but apparently not well enough. Reading it again I see it xD (And its obvious too that you mention boomerangs multiple times)
Oddly enough, I actually find it easier to talk about bosses by name. I get confused sometimes when people just talk about them by number (calling them Boss 1/Boss 2), but maybe thatās just me lol.
I still can understand where youāre coming from wrt Tothmaugās design, even though I didnāt think the fight was that bad. I mean heās a dragon for crying out loud, why is his only real attack some goofy boomerangs with apparently an RNG element to their punishment? Let the guy breathe fire on us or something cool like that.
I just had an idea that might make Sand Storm better. It would give us time to appreciate the animation and wouldnāt encourage us, or even allow us, to avoid it altogether:
What if it wasnāt interruptible, and instead of him just wandering mindlessly around the arena, heād fly up high into the air & become invincible during its duration? Instead of the blue orbs, there could be adds during the phase that we have to kill in order to get out of it/break his invincibility so that we can damage him again.
Also I wanted to tag @Jake_E to make sure he sees all this, before it gets drowned in responses.
No worries, Iām taking notes.
There are some definite ones that I want to address first that are more on the technical side like the collision issues with the stunning rocks on Mordoken or the unintended penalty trigger.
As for design changes on the Tothmaug, Iāll go through again and see what we can do but I donāt want to make too many drastic changes just yet. Although after seeing people play it I agree that the sandstorm is way too short (which is sad because Iām quite proud of how that looks. 
)
Anyway Iāll keep everyone informed on any changes made and when they are active.
Not sure if it a fault of the musky but maybe a mechanics bugm As I had the debuf triger on me alone when 100% sure not hitting it on the wrong phase. But that was only once and didnt take the time to test this further.
How does the bounce heal mechanic work with respects to enemies within range of the bounce. Do they get a log line in the parse for 0 damage (-0 damage cause heal) and thatās how the boss dot is triggered?
been spam bouncing renew with a group and no fire stacks
Update:
Shaman frost and lava totem pulses should not trigger penalty on Chief Mordoken.
That is live in new dungeon instances.
I have also been doing some testing on this as well. Healing orb ābouncesā only register on friendly entities. But another good way to confirm this (if you want) is before starting the fight, place your turret or another player close enough to the boss. Shoot your orb at your turret or other player and see if the bounce begins the fight. This is just to show that the bounce has no effect, specifically for triggering the penalty -The only time it would matter is if it was a direct hit.
For the dragon boss I think it would be cool to make it once it reaches 50% health or something it then casts sand storm but it canāt be interrupted bringing you into like a new phase you would probably have to turn off the virus that comes with it but buff his attacks and introduce a new mechanic maybe like chaos lightning or something that takes away a certain percentage of all the players health if not interrupted but also deletes all the boomerangs making it high risk high reward and also solves the āto many boomerangā problem. Having different boss phases is always cool and it would be fun to look at the storm for much longer during the fight.
Tested the boss a bit more. If you hit the boss at the very end of a Booga phase it can already register as an Oogy phase (if the next phase is Oogy). This is probably what is confusing alot of people thinking they didnāt hit it in the Oogy phase. So it probably needs a delayed mechanic switch, instead of other way around. Its doing the same with the stun/heal AeO. It already heals on 80% of the interrupt bar. Should be other way around. That only after the interrupt bar is done, should the boss check if it has been stunned on time.
weird, must have been something else that I wasnāt noticing, thenā¦
Small tweak before the weekend:
Reduced damage over time from pool created by āRattleā attack from Basilikos.
Planning on having another update next week with various improvements and changes based on the feedback weāve received already.
@Jake_E So we figured out last night that on Tothmaug the number of boomerangs on the field increase the amount of interrupts it takes to handle the sandstorm castbar. the only problem I, you cant break the boomerangs without killing your team in the process. it would be nice for them to be able to be destroyed with damage, or make the affliction stack target the person hit with the boomerang, not the person the boomerang is locked onto. at least then it could be handled with a decurse mage or musky over healing the person running into boomerangs. but as it stand the boomerangs overrun the arena, and make sandstorm completely uninterruptable.
It is similar with the bolts on the first boss. The player who gets hit by the bolt gets the affliction DoT, but it also kills the player who was initially targeted by it. I think it would be better if it only affects the person who gets hit, or at least change the visuals so it is more obvious why people die.
There is also the way to get to the dungeon, like, a few steps before getting in, between the boulders. There is no way to get past if not skipping/hopping.
Not that it is a problem. Not at all.
It is justā¦ well, just doesnāt make sense, as the space you have to walk around looks wider.
Speaking of where itās at anyone else find it a bit funny that the portal appeared right next to the people who have been trying to make a portal for the past like 4 years. Now the msq makes less sense because why help them build the portal if thereās literally one 50 feet away!
And weāre back again with more things to point out from testing varying levels of Plateau dungeon shards!
First I want to say that it doesnāt seem like weāre having any problems so far with levels 1 through 6. We were able to sub-15 a level 5 and a 6 isnāt going to be that much different.
After the level 5, we moved on to a level 9 (big jump, but weāre working with what we have) and thatās the point where we ran into big issues. Iām just gonna list off the things weāve noticed as bullet points, and some of this is just going to be a repeat from my earlier post about the 14 we attempted, but I feel like the points need to be reiterated based on our experience in the level 9.
I know thereās supposed to be an update coming soon that will probably address some of these things, I just want to give as much feedback as I can so that we can highlight what we already know & bring any other issues we find to your attention as quickly as possible.
I want to stress that this is a VERY capable group. Like itās one of, if not the most skilled & experienced groups of players that I run with. We have very high DPS & very experienced tanks & healers, and weāre struggling a lot on as low as a level 9 shard for this dungeon. I have to imagine it will be unbearable for less experienced/skilled groups. So take everything weāre saying with that in mind.
Weāll still be testing shards for Plateau as often as we get chances to, and I still want to wish the best of luck to any other parties who are doing the same! We canāt wait to see this dungeon in a manageable state so we can start having fun running shards for it with everyone else & sharing everything weāve learned!
On this note heres our parse from Mordoken on a level 9. we did 12 Mil Health and he wasnt close to dead, maybe had a 1/3rd of health left, maybe more.
I feel like this one shows it just as well. This was a 5 minute run and I belive this might have been the time where we got him to ~20% HP. Nearly 19 million damage dealt, 5 minutes, and no kill.
i too think that the bosses are too hard
