Thread: Patch 6.21 Notes

Such a flex. "Our team got gud."

Originally Posted by Jojoya

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, and I'm sure many others, are still very curious to know what comp their testing team was using, but I don't reckon they'll ever reveal that kind of info. We'll just be left to wonder.

Originally Posted by Iyrnthota

I, and I'm sure many others, are still very curious to know what comp their testing team was using, but I don't reckon they'll ever reveal that kind of info. We'll just be left to wonder.

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.

Originally Posted by Jojoya

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.

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

Kind of a disappointing way to "fix" the issues players were having without actually substantively addressing the concerns players have around job balance.

The HP of Hephaistos in Abyssos: The Eighth Circle (Savage) has been reduced.
This adjustment applies to both phases of the battle.

Reasoning for HP Adjustment
In our endeavor to create an encounter more challenging than Asphodelos: The Fourth Circle (Savage), the team responsible for final adjustments spent a great deal more time than usual working on balance for this raid battle.

Under normal circumstances, the DPS of this team serves as a base for determining a boss HP value that results in clears as close to the time limit as possible. However, as extra time was dedicated to testing this battle, the team's overall performance proved to be higher than usual. As a result, the base values used for adjustments were too high, with final values roughly 1% higher than intended.

We have reduced the boss's HP to bring the battle in line with our initial balance projections. We apologize for any inconvenience caused.

This is a crap take. I'd rather them admit that they just really screwed up in job balancing and this is the reason for the discrepancy. Not because 'oh lulz our team just did better than expected so we got it wrong. '

Gimme a break SE, your crap balancing of classes is the reason for it, and nothing else.

Apology not accepted.

Originally Posted by Kanzer

This is a crap take. I'd rather them admit that they just really screwed up in job balancing and this is the reason for the discrepancy. Not because 'oh lulz our team just did better than expected so we got it wrong. '

Gimme a break SE, your crap balancing of classes is the reason for it, and nothing else.

Apology not accepted.

They COULD be right, since we don't know their job makeup for the fight, nor whether they did it at minimum ilvl or not. I'd prefer if they'd test at minimum ilvl with every job makeup, but that may take too long (and require them to actually play jobs we know they don't play, like DRK or SCH).

Originally Posted by RyuDragnier

They COULD be right, since we don't know their job makeup for the fight, nor whether they did it at minimum ilvl or not. I'd prefer if they'd test at minimum ilvl with every job makeup, but that may take too long (and require them to actually play jobs we know they don't play, like DRK or SCH).

I'm not sure every job makeup would be necessary but they should test it with the projected lowest damage composition respective to sub roles, including a double melee, double caster, and double physical ranged comp respectively, and possibly cross references that with the projected highest damage comp. It should be doable even with double physical ranged without needing to rely on above average crit luck.