There's nothing wrong with shaking things up. The designer for Evolved mode, Hikaru Tamaki, was also responsible for the changes to the PvP job action rework in 6.1, and you can see that influence in what we've seen so far from Evolved mode. Ideas like the DRG jump mitigation idea are creative and give jobs unique flavor, and I'm very interested to see what he does with this opportunity.
What makes me worry is when the devs come in with a fixed expectation on how players will engage with those changes. One of the strengths of their pre-Stormblood game design is that they let emergent gameplay outcomes be for the most part and just observed what players did with them. It doesn't really matter if players tank a fight in a completely different way from how the fight was originally designed, or if they equip gear that's not intended for them (STR gear), or if they prioritize completely different stats from the ones you thought they would prioritize (Parry), so long as it doesn't trivialize content. Fighting this generally is not a good idea. Instead, it's better to ask why they're prioritizing things differently from your expectations, and to build on that organically.
You won't convince people to care about Parry, so you're better off finding out what they care about instead. Tanks are (unexpectedly?) choosing to play in ways that push their damage? Lean into that. When game design becomes too tyrannical, players become frustrated and lose interest. The starting point shouldn't be 'let's split tanks into MT jobs and OT jobs'. That's the sort of decision that I'd expect from someone who hasn't observed how tanks do content for the past 10+ years. The starting point should be 'let's create interesting but different gameplay mechanics for each tank subrole that encourage players to approach tanking in a new way'.
The counterattack mechanic is a really interesting concept with problems. They tried it out in Heavensward and Stormblood but eventually removed it. One of the drawbacks of the design was that PLD would use Sheltron on raidwides to generate Shield Swipe if they were not actively tanking, which made Intervention a dps loss. They've since experimented with it in the form of lost actions from exploratory content, as well as with BLU. I'm not sure what lessons they've extracted from observing players put it into action. What would have made me more confident in this decision is if they had instead said 'we've tried out counterattacks previously and run into the following problems, and this is how we intend on overcoming it.' Even if it doesn't work out, that shows me that they're taking into account player behavior. But the fact that we have the same implementation, with no comment on prior iterations of it, and no comment on a potential direction for the OT subrole makes me concerned that the starting point was 'let's enforce a split that tanks don't actually do in practice'.


Reply With Quote



