The funny part is, despite barely changing since 4.0 a Stormblood bard main could immediately tell you as soon as they use Wanderer's Minuet.Hypothetically. You could give the current lvl 70 Bard to some bardmain back in the days and the person wouldn't noticed anything immediately except the duration changes and the missing requiem.
Bard pretty much plays the same and i hope it stays that way. Lets hope they dont remove BRD dots in the future.
The simple change of making Repertoire procs no longer tied to your dot crits changed the feeling of the job massively.
Give BRD repertoire procs back (and give it a Bane while you're at it)
god I miss endlessly raining arrows on trash pulls
Future battle design may cause difficulty with casting spells, so we have shortened the cast time for a variety of actions. Furthermore, the effect expiration of Astral Fire and Umbral Ice has been largely detrimental to attack power in situations where players must interrupt casting to address battle mechanics. For this reason, these statuses will no longer expire.
In Patch 7.1, Ley Lines became a charge-based action, which has resulted in movement restriction lasting longer than intended, so we have reduced its duration.
In light of all these changes, we have generally amplified black mage's firepower by increasing attack potency and adjusting the trait Enochian.
EVERYTHING IN THIS GAME MUST BOW DOWN IN FRONT OF THE ALMIGHTY DDR RAID DESIGNFuture battle design may cause difficulty with casting spells, so we have shortened the cast time for a variety of actions. Furthermore, the effect expiration of Astral Fire and Umbral Ice has been largely detrimental to attack power in situations where players must interrupt casting to address battle mechanics. For this reason, these statuses will no longer expire.
In Patch 7.1, Ley Lines became a charge-based action, which has resulted in movement restriction lasting longer than intended, so we have reduced its duration.
In light of all these changes, we have generally amplified black mage's firepower by increasing attack potency and adjusting the trait Enochian.
Wow, we're so lucky to have the devs noticed the immobile caster was immobile! It'd be a shame if that caster stayed immobile though, we can't have thatFuture battle design may cause difficulty with casting spells, so we have shortened the cast time for a variety of actions. Furthermore, the effect expiration of Astral Fire and Umbral Ice has been largely detrimental to attack power in situations where players must interrupt casting to address battle mechanics. For this reason, these statuses will no longer expire.
I've never seen a worst justification of job murdering than this one, and I've played a lot of MMORPGs. Players dropping their enochian so they can't hit the boss and do less damage? How's this a big deal? They'll learn the fight and they'll be able to do every mechs without spell interrupting. Like we've always done it. Ah but right, we can't have that too, of course, no failures allowed, only success even if that means the game must almost played by itself.
Can't wait for next patches to give every caster instant cast on all of their spell too, after all, we're dropping our cast too when dodging a mechanic for the first time right? Don't forget the enormous EW hitbox to come back, melee have to hit the boss 24/24 too or they'll get sad
No difficulty or optimization potential in job design! This is only allowed in fight design! That's is the CS3 way.Wow, we're so lucky to have the devs noticed the immobile caster was immobile! It'd be a shame if that caster stayed immobile though, we can't have that
I've never seen a worst justification of job murdering than this one, and I've played a lot of MMORPGs. Players dropping their enochian so they can't hit the boss and do less damage? How's this a big deal? They'll learn the fight and they'll be able to do every mechs without spell interrupting. Like we've always done it. Ah but right, we can't have that too, of course, no failures allowed, only success even if that means the game must almost played by itself.
Considering Yoshi-P said something about them having gone too far in terms of job simplifications roughly a year ago, I don't see how we can take anything he says serious anymore.
RIP Viper 28/06/2024 - 30/07/2024. It was a fun month.
I think he was talking specifically about the content design, not the job design. And it's the content he's trying to address at the moment.
But since he has declared 8.0 as the expansion that will focus on job design in a number of ways (skill tree tease, making them unique tease, etc), they'll have to confront this sentiment eventually.
No, he specifically was talking about the jobs.I think he was talking specifically about the content design, not the job design. And it's the content he's trying to address at the moment.
But since he has declared 8.0 as the expansion that will focus on job design in a number of ways (skill tree tease, making them unique tease, etc), they'll have to confront this sentiment eventually.
The bit that patch 7.2 would mark a change in job design was a mistranslation in this article, but the rest is pretty much what he said. Yes, they wanted to work on content design first, but fact remains that he promised jobs would not become more simple. And yet here we are.In an attempt to curb multiple updates' worth of simplification, Yoshi-P details how Square Enix "will be incorporating various changes" post-Dawntrail, some of which will be "related to the skill rotations." He even jokes that Kaiten could return as "Kaiten 2" and reiterates his earlier promise - come such changes, classes "will not be more simple."
RIP Viper 28/06/2024 - 30/07/2024. It was a fun month.
Gotta remove positionals too. Not being able to get the extra 50 potency on Gekko because a boss was doing a backwards half-room or something just made me want to delete the soul crystal.Wow, we're so lucky to have the devs noticed the immobile caster was immobile! It'd be a shame if that caster stayed immobile though, we can't have that
I've never seen a worst justification of job murdering than this one, and I've played a lot of MMORPGs. Players dropping their enochian so they can't hit the boss and do less damage? How's this a big deal? They'll learn the fight and they'll be able to do every mechs without spell interrupting. Like we've always done it. Ah but right, we can't have that too, of course, no failures allowed, only success even if that means the game must almost played by itself.
Can't wait for next patches to give every caster instant cast on all of their spell too, after all, we're dropping our cast too when dodging a mechanic for the first time right? Don't forget the enormous EW hitbox to come back, melee have to hit the boss 24/24 too or they'll get sad
Like, if he was actually serious about that statement, and they have legitimate plans to overhaul every job to restore its sense of identity in 8.0, how does he think tripling down on homogenization during the 7.x patches will help that? If it were up to me, I would think it would make more sense to start restoring job identity piecemeal during the patches before the "big leap" in 8.0. From all appearances, they’re simplifying and homogenizing the jobs to cater to the "more challenging raid content," but if they actually follow through on a serious overhaul of the jobs in 8.0, they’ll want to revisit the encounter design again after that because the overhauled jobs will no longer “fit” with the encounter design.No difficulty or optimization potential in job design! This is only allowed in fight design! That's is the CS3 way.
Considering Yoshi-P said something about them having gone too far in terms of job simplifications roughly a year ago, I don't see how we can take anything he says serious anymore.
This is why it’s a fool's errand to try and work on encounter design in a vacuum separated from job design. The two are intrinsically linked, and if you don’t build one with consideration for the other, you end up in a cycle of “fix encounters-fix jobs-fix encounters-fix jobs…” ad infinitum.
Last edited by Illianaro; 03-24-2025 at 09:40 PM. Reason: Grammar and clarification
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.