This fight is, hands down, probably one of the most unfun, chaotic, clusterf fights I have ever seen in a mmo. Please, for the love of god, gut this boss it is not fun.
The random trap RNG bricking your arena is so, so, so, so frustrating. You have three different, very positioning intensive mechanics ontop of mechanics that force you to move around the arena constantly.
If the boss was designed to be this god awful, you should have just left the cheese in. Honestly.
And the boss is so bad I feel justified making an entirely different thread to make my voice heard 
You should see Twitter lol
Just remember; this fight had the cheese strat until the Blizzard dev that made the fight got their guildâs clear (they are GM and they used the cheese strat) then they âfixedâ it. Real standup dev Blizz has there, huh!
Please listen to this feedback blizz. Not only is this unfun - itâs horribly tuned. Even if we did all the mechanics (which are absolutely annoying, regardless of difficulty) this fight would rank as top 3 worst in all of wow history.
If they make more bosses like this Iâm done with raiding. This RNG fest that all the good guilds didnât even properly do. Why make it harder for objectively worse guilds??? When all the HOF just cheesed. So dumb
this is subjective. theyâre not going to change the boss just because you donât like it.
Itâs very funny to see comments from people who either cheesed the boss, havenât done it on mythic, or donât raid mythic.
I have yet to see anyone who actually progged this boss after the âfixâ enjoy the fight.
You can have a perfect pull where all mechanics are done perfectly and nobody makes mistakes and you can very easily wipe due to bad RNG of traps. Thatâs not good game design, which in turn makes the fight not fun - thatâs not subjective, thatâs a fact.
Iâm not sure whatâs a scarier thought⌠Either the fact that itâs incredibly unlikely anyone from Blizzard is doing this fight after the fix (they barely play their own game) or the thought that someone greenlit this fight after the fix and thought itâs acceptable raid design.
Furthermore Iâve seen first hand accounts on both the raid lead discord and comments from other guilds that this fight is actively killing guilds. This isnât a âprog-checkâ boss that kills guilds, this is a horrendously designed fight to which nobody has a good time and some wipes are out of you control.
It would be in the best interest of the game to change this fight, otherwise weâre going to see more hyped guilds who just killed Rashok die on this boss, just as they are now.
Our guild literally dreads showing up for Zskarn prog. The fight is trashy because itâs start to finish RNG. You can have an amazing pull where no traps spawn where you pull the boss and then the next pull all the traps activate in the same spot. Then you have adds, lines to dodge, knockbacks, and a million other ways to get toasted.
Rashok is a trashy raid fight as well because the boss has ridiculously high dps requirements and it falls back to the same blizzard trope of just spamming the room with things to one shot you when they canât come up with anything else.
The lack of nerfs to these bosses (and well, M+ too) is astonishing. Rashok should have had a -10% hp nerf already and Zskarn should have been completely overhauled with no RNG.
How to fix the entire encounter in a few easy steps:
Thereâs a decent fight at the core of zskarn, its just ruined right now with awful RNG and even more terrible visuals.
or you can have the opposite⌠which makes the fight fun.
If wiping 19 out of 20 times to RNG is fun because you had a single pull with good luck, then more power to you - Iâm pretty sure youâd be in a boat by yourself with that though.
how many overlapping combos are impossible as a percentage? you mentioned 19/20 so youâre saying 95% of mechanic placements are unsolvable?
seems ⌠hyperbolic.
Given you clearly havenât progged this boss and you clearly havenât truly read the complaints of the fight to understand whatâs actually RNG (plot twist, the overlaps are not the RNG), the trap spawning mechanic is, Iâm not really sure why youâre so hellbent on defending this boss.
Best of luck to you when you get to it.
This boss single-handedly made me want to quit raiding all together. Proging as a dps warrior on this fight is worse than pretty much any fight I can think of in wowâs raid history. I just donât understand what the developers were thinking. And if the rumor about the developer killing it with cheese with his guild then âfixingâ it afterwards, somehow I wouldnât be surprised given the recent blizzard behaviors.
Itâs not a rumour, he literally said as much on Twitter. Somewhat of a case of bad timing, but itâs undeniably a bad look for the developer of the freakin boss to do that and then leave the boss in a state that requires wayyy more pulls for everyone who got there later. They could have forced everyone to reset instance instead of extending. Or nerfed the boss further so that it wasnât significantly harder than with the cheese.
Personally Iâd like to see them just reduce some of the clutter. Lower the random trap spawns from 2->1, and reduce the number of golems. Room fills up slower and less randomly but you have less clearing power so itâs more about plotting an efficient path through the encounter than the current state of reacting to the randomness.
Blizz seems to LOVE to do this, it was same exact issue with Dathea. By the end of the fight you had 12+ tornadoes to dodge with only an arrow. If 4 were grouped up in a small area it was incredibly difficult to tell exactly which way certain tornadoes were going. So many other mmos and games have much better indications of area on spells. I understand wanting something to be difficult, but often the lack of visual clarity on a lot of things seems to be an issue lately.
The boss designers deserved an award for creating the worst boss design in the history. The Blizzard designer who designed Zskarn and whose guild killed Zskarn using cheese strat. Then they changed Zskarn 24 hours later in the middle of the week (on a Friday).
Whoever designed this boss should not have a job