I will probably sound pessimist but I am so afraid of what changes they will do to Paladin in 6.3 just to "fit" in the whole burst thing.
Hopefully my fears are just misplaced
Printable View
I will probably sound pessimist but I am so afraid of what changes they will do to Paladin in 6.3 just to "fit" in the whole burst thing.
Hopefully my fears are just misplaced
The post was also acknowledging that players would likewise get good after they had a similar amount of time to do the content.
At least SE has a team devoted to thoroughly testing Savage content before release to make certain that it can be cleared on release. Then there's Blizzard's "whack-a-mole" approach... (just release it then we'll start making changes after seeing what roadblocks the world first teams).
Either way, players like knowing why things went wrong, not just what went wrong. This time, they got a pretty direct answer.
I've always gotten the impression they use a few different comps during testing so all jobs end up represented (but not all combinations of those jobs). I could be wrong, of course.
But they definitely aren't going to share that information. They don't want to feed player obsession with meta comps.
If players want to feed their own obsession, they can always go to FFLogs to see if there were any jobs not represented at all in week 1 clears, and which jobs were the most represented.
usually they own up to their own mistakes but passing the blame onto the players because of atrocious job balance resulting in mathmatically impossible dps checks for some comps is really really bizarre
I dunno, the idea that they use a variety of different comps doens't jive with their statement about this tier.
They claim to have spent a long time figuring out this fight and using that to determine the check, which tells me they had the same comp throughout, like a typical static might.
If they managed to spend as much time as they're implying optimising their runs on multiple comps, then they might actually be god gamers