Undoing homogenisation thought: replace cross role skills with unique versions

[Recon1o6]

Woudl like to point out folks, htis is about making the role actions unique to each job like how some of them used to be, rather than the meat of each job

we all know we want healers unique with their actual spells, abilities etc and this has been discussed at length already in plenty of threads, that's not what this thread is focused on. this one is focused specifically on the role actions

[Jaelommiss]

Woudl like to point out folks, htis is about making the role actions unique to each job like how some of them used to be, rather than the meat of each job

we all know we want healers unique with their actual spells, abilities etc and this has been discussed at length already in plenty of threads, that's not what this thread is focused on. this one is focused specifically on the role actions

The problem with homogenization is that it leads to all healers feeling the same to play. Changing the name and animation of role actions does nothing to fix that because it does not address the mechanical similarities that all healers' toolkits share. Others have rightfully pointed out that all healers need the same baseline actions (Lucid, Swift, Surecast, Esuna, etc.) in order to function interchangeably. Changing role actions to unique, class specific versions does nothing to address the root cause of homogenization and would draw development resources away from meaningful changes.

Homogenization is a mechanical issue that cannot be solved with a fresh coat of paint.

[MintnHoney]

Homogenization is a mechanical issue that cannot be solved with a fresh coat of paint.

I agree that the idea wouldn't solve the core issue, but I also think that it wouldn't hurt to have the animations and V+SFX individualized to the job in question (if only to create a deeper, though still-shallow illusion of individuality, and aid the perception overall if they only ever decide to bring subtle nuance in for differentiation of the healers).

Also, for as much as development resources are a valid concern to take into consideration, I think we should put that aside for suggestions, in general. For one thing, it undermines the responsibility of the development team to manage their workflow and employees (and provides them an easy excuse to provide less for the same profit, and to stop trying in general), and, for another thing, it generally just puts people down for any and all suggestions that could be made (because whether or not someone likes a suggestion, or how "valid" the suggestion might be, only the development team is really able to decide if the endeavor is worthwhile).