I actually just made the switch today, im now double fire spec.
TTW main and FFB dual spec.
No more arcane, thank god!
Not complicated, it comes down to raid comp. As soon as you have a geared Combat rogue providing the bleed damage buff Arms is no longer a relevant addition to a comp.
Fury provides crit and commanding shout, so is taken for the later, or bith in absence of a kitty.
Anthing ret provides (kings, wisdom, might) is also provided by prot/holy which are both solid choices. Might can be gotten from Battleshout if you have an extra warrior.
Ranged dps > Warrior dps > ret, so comp takes a ranged unless arms warrior needed due to lack of rogue.
âreti eunt domunâ - means Rets Go Home!
Iâm going to snipe this because itâs a bad way to look at it.
Guilds that are killing Algalon right now are the guilds that did more prep for Ulduar, the dad guilds havenât gotten to him yet. You have this weird narative where youâre posting like Algalon is what people are prepping for, when the fights not hard and can be completed by most comps. Itâs just right now the only people that have killed him are the small handful that did a lot of prep work, and prepped almost exclusively for 0 light.
Ret got buffed, not because of representation but because some guilds were having the 2nd Prot Paladin tank go on a different class instead of playing Ret for single tank fights.
Guilds who prepped, didnât prep for Algalon. We prepped for 0 light, which is why thereâs so many Warlocks. Warlocks are doing so well because guilds that did prep stacked gear on them for 0 light, and 0 light favors having 5 or 6 warlocks because they counter P3 lunatic gaze and can hit the DPS threshhold for 3rd beacon.
If they started doing balance based off representation, weâd be unjustly nerfing Warlocks right now. Half of them are going to swap to Mage at the start of ToC anyway.
And youâre more likely to see a kill as a Holy Paladin on Algalon because not only does DG do wonders for collapsing stars, DG is also phenominal for tantrum, taking an extra 2 stacks of biting cold to maximize the buffs, anamousâ stacking raid damage, and every raid damage spike on Freya.
Youâre posing the question as for the hardest boss youâre more likely kill a boss if you played X spec.
The response from the higher end playerbase is itâs 10 year old content with a wealth of information, we prepped X spec to beat the content in the first two weeks.
1 Like
Correct. I specifically chose Algalon because that is a fight that specs are most likely to be stacked or ignored for a perfect comp. The early kills also highlight which specs are most useful for utilities that get them brought to the fight.
When you include âdad guildâ data, you miss a lot of the class stacking/avoiding, which is what I was looking to identify.
No one cares if ret paladins donât have issues getting into bad guilds.
Itâs more interesting to see how much they struggle to get into the super prepared min/max guilds, as those comps are typically what the weaker guilds will emulate in order to make the fights easier on themselves.
You arenât going to see a representation issue on Ignis. Those logs just show you that less players have even tried using X spec.
Thats not including Hand of Sac, Aura Mastery or DivGuard and Replenishment.
1 Like
The buff to collapsing stars on Algalon didnât paladin stacking the optimal comp, it made it the required comp.
Not really true. Having killed him the last two weeks I can tell you itâs just as easy for melee as it is for ranged. The only damage thatâs avoidable that isnât a one shot is cosmic smash, and if you bait on his right foot and run to his left foot you take a less than 1k hit. The majority of deaths will happen from constellation barrages overlapping with star explosions and tanks.
We are running 2-3 DKs, 3 rogues, a Feral, a Fury warrior, and an enhance shaman as melee dps and it didnât cause any issues.
If we know itâs poor⌠why canât we change it?
Is some of your enjoyment of classic a certain spec being bad?
Because the fact that ret sucks isnât how it was⌠itâs because of the patch choice.
Itâs like weâre all pretending this is a âclassicâ experience, but itâs not. Just like 20+ warrior raids in vanilla.
So if we know itâs not actually classic⌠why canât we fix issues?
I think some of you would fit better in Afghanistan instead of a video game.
âWomen showing their ankles? Pfftt women knew what they were getting into when they were born. Asking to show ankles and asking us to change? Entitled!â
Rolling a class and being born are not even slightly analogous.
1 Like
Even though I donât overall disagree with the body of you post, reductive arguing like this:
Is unhelpful to getting your point across.
Itâs just like people saying âwhy donât we just hand out epics in the mailâ when people have tuning or gearing concerns.
1 Like
Your response is absolutely uncalled for and in my opinion falls in line with hate speech.
How does player choice have to do with Afghan women are treated? You are quite delusional if you are equating player free choice and being born in as a person in a country where your freedoms are indeed limited.
Your fanatical and out of line ideas equating your fellow player base equivalent to the taliban is incredibly inflammatory and incendiary.
At the end of the day, rolling RET was player choice.
You looked at spec instead of class.
Class wise paladin has extreamly high representation on that fight.
Class representation doesnât matter when it only has 1 option for a role itâs allowed to spec into.
Just like it wouldnât matter if prot warriors were the only viable tank and in every raid as an argument to not balance fury.
If a class can spec into damage, it should have at least one option with competitive damage output.
Same with healing and tanking.
Blizzard messing up and making one or two roles too good shouldnât be used as justification to keep the others bad.
If healing / prot is too good, nerf those. Donât keep the damage spec below the bottom of the barrell.
Same with specs, blizzard making 2 specs ok, isnât justification for the 3rd to be a dumpster fire. Class balance is being done, so dont stop at rets.
They donât go as far as spec representation because many of the underpowered PvE specs are commonly very powerful in PvP (frost mage, for example), so they opted to not buff those into viability given that mage has other specs that deal PvE damage.
So, best way to describe the representation that matters would be role representation.
If your class has a spec in a role, it should be able to do that role competently in a raid. This may not be in your preferred spec if you have multiple options. (Like how disc is favored over holy, fire/arcane over frost, combat/assassination over subtlety, etc.)
Yes but if we move the goalposts just right, then their argument will hold up. Move it a bit to the left or the right and now we either do nothing or fix the other broken classes.
And thats the problem with many rets. They got their buff and now are trying to shut down any conversation on possible fixes to other classes low performing specs.
No, people just misinterpreting what Blizzard said.
They specifically stated they arenât aiming for full spec parity.
They brought rets up because their only damage spec was significantly under the rest of the PvE damage specs.
In order to be buffed under the new guidelines, you need to have a spec that is a classâ only option for that role, that is significantly underpowered at doing that role.
So far the only other spec that I can see that might fit the bill is resto druid.
So can we divide dps roles to ranged vs melee or are your goalposts stuck right there at âOnly dps option for class?â Because the dps role(ranged vs melee) does in fact matter.
I mean, Iâd be open to discussing ele shaman for that reason. It is definitely hurting at the top end from what the data shows, despite beating ret in damage.