Yes, "We", have.
Your one example of how this is possible uses a Job stone.
All modern additions to the game are with a Job stone.
There's literally no reason NOT to do this with a Job stone (save one, which I'll get to...)

Originally Posted by
ty_taurus
I don't care if there isn't a branching job off CNJ.
YOU don't. _I_ do.

Originally Posted by
ty_taurus
My point is, rather than investing the resources needed to create an entirely new healer...
I know what's going on here, but you won't accept it if I tell you. Here's the short version:
You're like a kid who hordes all his toys when playing with friends at his house, and is only willing to share the action figure he doesn't like anyway that has a broken off arm if the other kid cries enough and your mom makes you share. It's immature and it's selfish. It's why you won't let people have WHM as it is (despite always being the simple Healer AND being the logical choice for the easy one) and you won't let them have SGE, either (despite it only existing in this model and under this form) - because you want them both. You're only VAGUELY "willing" to "share" the WHM with the broken arm that you don't like anyway, CNJ.
So much so you oppose the creation of Druid or Geomancer - a new Job - having WHM's current kit because that would be A JOB which YOU don't own and are having to share, which you desperately don't want to do. How dare there be a Healing Job that doesn't comport to your system, you protest, while insisting giving the armless WHM is "good enough".

Originally Posted by
ty_taurus
The point of suggesting that we use CNJ as this bare-minimum DPS healer is that anyone who likes CNJ/WHM is given the option to have more in their gameplay.
Which they'd get if it was Druid or Geomancer. OR if it was WHM and DRU/GEO was the one one that Yoshi P took your WHM rework idea and made THAT Job into it instead. What's the downside of the people with the simple kit having a JOB instead of a CLASS, exactly?

Originally Posted by
ty_taurus
It's also extremely economic since it requires a very minor amount of work to accomplish.
You know what would be even more extremely economic?
Leaving WHM as it is right now and adding GEO/DRU as what you want WHM to be.
Your proposal, while you insist it's little work, is actually MORE work than adding a new Job. Because they'd have to (a) rework the Class system to have Traits that are not inherited by the Job that comes from it (something that doesn't exist currently; SCH, in the game code, is basically like AST, a stand alone Job without a Class, at this point), (b) they'd then have to copy ALL the current WHM abilities to this new "Class", (c) they'd have to alter the game's matchmaking system to allow Classes to que up in things that don't right now, but ONLY for CNJ, (d) then they'd have to rework the WHM Job entirely, basically creating a new Job out of it like SMN.
How is that less work than "Leave WHM alone and then do (d) as a branching Job"? That's FAR more economical.

Originally Posted by
ty_taurus
Sometimes you do new things to resolve a problem.
Like adding a new branching Job to an existing Class? That would be a new thing.

Originally Posted by
ty_taurus
then that is a solution that could quite literally be done in minutes.
Know what could be done in even less minutes?
Leaving WHM as it is right now and adding GEO/DRU as what you want WHM to be.

Originally Posted by
ty_taurus
You get what you want, everyone else gets what they want.
NO!
I DON'T get what I want.
YOU get what YOU want and I get what you're barely even willing to give me, even though it would require far more work to do what you propose than just adding a new Job for your WHM idea and leaving WHM alone OR adding a new Job to CNJ, copying WHM's abilities to that, and then changing WHM. Either of those would still be less work than what you've proposed.
You clearly don't know what I want, and don't care, but no, your proposal isn't what I want. It's what YOU want.

Originally Posted by
ty_taurus
Why complicate it with trying to introduce Druid or Geomancer instead?
Because that's not COMPLICATING it. That's the SIMPLER solution.
Your solution would require new coding. It would require the community to see a Class - but ONLY one Class - as equal to Jobs. It would require change to the game's backend to accomplish.
That's not the simpler solution.
What's happening here is this:
I was right.
You don't want to share. You want every Healing Job to be one that YOU want with YOUR style of play. The only case you're willing to "give up" is one that you feel you aren't sacrificing anything because (a) CNJ isn't a Healer Job right now and (b) you having WHM means you aren't giving anything up.
"To obtain, something of equal value must be lost. Equivalent Exchange." It's not just Alchemy's one and only truth from a cartoon in a fictional universe, it's also the art of compromise. You give up something and you get something in return.
Your "compromise" here is that you give up nothing and get everything you want.
And the idea of GEO or DRU going to the simple players OR you getting those but WHM going to the simple players would mean you giving up something.

Originally Posted by
Renathras
But then we'd have this same problem again - all of you complaining that you like the Druid/GEO aesthetic but it has a simple damage rotation and how that's unfun and unfair to you guys. All the people right now complaining WHM doesn't have the earth/wind/water elements would be pissed if Druid/GEO got them and we'd still have this exact same complaint. So while they COULD arguably lock Druid/GEO as a Level 50 CNJ with just boosted ability power to keep it competitive with WHM, not only would they probably never do that in a million years, even if they did it, the people demanding complex DPS of every Healer aesthetic would STILL complain about it.
Let's be real: THIS is what's going on here.
Admit it, don't admit it, it's the only reason to go through your tortured proposal rather than just adding a new Job for your WHM rework and leaving WHM alone, or adding a branching Job to CNJ that is WHM now (though that's still stupid since that'd be more work than just adding the new Job and giving it your WHM ideas as its rotation.)