Concerning the 2 new Jobs

[DragonHearthX]

They're not changing their minds this late out. The job is probably a coding issue and a tuning pass away from "done."

how is it to late? It was just announced. Or are you one of those guys that think the time to change minds was 3 to 5 years ago when the very first thought seed was planted.

[Shurrikhan]

how is it to late? It was just announced. Or are you one of those guys that think the time to change minds was 3 to 5 years ago when the very first thought seed was planted.

Netflix releases the teaser for a new Netflix original animated series, containing snippets from episodes across the first half of its first season.

"No, they're not changing it now."

"But why? They've only just teased it!"

...

What's revealed is not likely to be nearly the limit of what has been done.

If one's writing a dissertation, they don't give a peak at the larger work as anything publishable until they're already pretty damn sure they can finish that project, usually by having damn near all of it pretty thoroughly planned out.

The same goes here. We know the storylines for each expansion are mostly charted out by about the time the previous one is released. We know that job additions are often made in parallel with / mindful of those expansion features and storylines.

Why then would we assume that they'd completely change their mind about what aesthetic they'd want to go with after already having locked in the name, gear, style, and proposed identity?

[Xlantaa]

Planning this things take months or years. Viper was probably planned as soon Endwalker was launched, since the devs starts the next expansion as soon they release the previous ones. This wasn't made in 2023, it probably date from 2021 or 2022.

people do not take very seriously schedules and development pipelines. People think things can be done in weeks, when they have already a bunch of things to do previously. I would even say that the 7.X patch series are already planned and in development alongside expansion.

[DragonHearthX]

I guess you guys forget about community feedback.

[ForsakenRoe]

I guess you guys forget about community feedback.

Said community has given feedback about, for example, AST's APM being super painful for some during it's burst window, and that Lightspeed is essentially 'forced' to be used there to allow doubleweaving. Two charges of Lightspeed would alleviate the second of those issues, and yet we still have only one charge.

Living Dead took several years to address. MCH's Hypercharge took years to be given stacks. DRK's Blood Weapon took years to be given stacks. Sure, the team listens to feedback, but at the rate they seem to act on it, you'll be getting the changes you're on about in 9.4 or so

Oh wait, you're asking for a new job to be tied to an old class, after it's implementation's already done. Which would be like asking 'hey can we split SCH/SMN, and have one of them reset to 1 so we have to level it again'. It ain't happening

[Shurrikhan]

I guess you guys forget about community feedback.

Then I guess the devs are in good company?

Well, I guess they still have their cherrypicked/misconstrued bits that occasionally slip through the cracks in their wall, but should actions something that hurts the goals of said feedback really be called a response "to" that feedback? That seems more an "against".

[SeverianLyonesse]

I guess you guys forget about community feedback.

Feedback would have to be overwhelmingly, universally negative for the devs to care about pivoting central features of a job class after it had been finalized for a reveal.

Such was not the case here, there are plenty of people clamoring about how much they love the job online. They will not change it.

I'm not really digging the name though. I do hope there was enough negativity surrounding that, since it is a minor aesthetic change. Just call the job Ranger please Squeenix.

[Shurrikhan]

Just call the job Ranger please Squeenix.

...Please no.

"Ranger" originally referred to a person entrusted with the care of a range of (typically private) land, usually to ensure that there is enough to hunt, raise, or fish on said land, often through wildlife management (including through hunting overpopulating or adversely invasive elements) and preventing poaching by peasants through preemptive or retributive threat if that land was privately owned (which it almost always was; a feudal lord being the government doesn't make the land they own public). And even now, it still refers to land management, known far more for its trekking and ecological observation and road maintenance, etc., than for anything to do with combat.

Now take a look at Viper's gear. Does their armor look the attire of someone who'd be travelling constantly through the countryside, sleeping outdoors at least as often as not? Look at their weapons? Is that what you'd expect for a hybrid between an ecologist and hunter of prey animals and the occasional trapper of wolves or wild dogs?

Even in DnD, a Rangers' unique functionality has little to nothing to do with melee combat. If you want a dual-wielding swordsman, both Fighters and Rogues do that better. Drizzt is as famous as he is largely because he is an amalgamation of outliers, a righteous, kind, surface-dwelling member of an under-dwelling mercenary, and typically outright cruel people who becomes a Ranger later in life (after already having picked up dual-wielding as a Fighter) who sticks to melee weapons. His being a Ranger has everything to do with him being an outworlder, a naturalist, not... dual-swords.

What part of Viper's garb makes them appear someone comfortable out in nature (while still pragmatic and/or short of glorifying said nature, per a Druid)?


Viper's aesthetic is that of an urban rogue with perhaps the occasional side of dungeoneering or piracy. It looks nothing like a Ranger.

[Hanayumi]

Yeah... not happening, already stated seperate from rogue/nin. Theyve mentioned tons of times they hate that sch/smn share a class with a passion so why another?