Quote Originally Posted by Supersnow845 View Post
That’s not what I mean at all

The only skills this would affect in a practical sense are

-PLD’s magical combo of which PLD is getting changed
-DRK’s AOE combo
-RDM’s first three melee pieces

I didn’t realise BRD’s songs and NIN’s mudras got changed and I didn’t realise enchanted melee combos are still weaponskills (I’ll amend that) but that’s all it would affect, sure it would be nice but it’s like 9000th on the priority list since square doesn’t seem to want anyone else to be half and half because RDM and PLD occupy opposing sides on that area and they like enforcing melee be ranged jobs for raid strats

But I’ll shut up now because the suggestion isn’t exactly bad and I’ve argued way too much (and been wrong too many times) for someone who actually agrees with the idea even if I think it would change barely nothing if implemented
Glad I could clear up a few misunderstandings.

That said, your opinion of what is priority #xyz is skewed, for one has this issue been around since Heavensward and further escalates with each expansion, even if it affects only OnE jobnit is a problem. It would also futureproof this issue ahead of time with new job and action releases.

For two, the actual workload for solving the conundrum works in three possible ways as I mentioned in another post.

1.) Merging = scan every class and object for either speed stats, create a new class for the basic speed stat and copy the attributes of both stats into it.

2.) Trait = create a trait attribute that will "if true: Spellspeed = Skillspeed" (or other way around for RDM) that exists on jobs with said actions.

3.) Recategorise = change the attribute of each problem actions to something their job can support.

For third, game development and combat / job design workloads are not a singular string of work in order.