Please reconsider removing job restrictions on glamour armor

[Bright-Flower]

I have a feeling that unshackling job restrictions from glamour, given the game's infamous spaghettie code, might actually be a bigger undertaking than I'd first imagine.

From a philosophical stand point, I'm all for it with the exceptions of main/offhand items and artifact sets.

I don't feel like there's all that much 'job identity' behind many of the sets. You have things like sky rate/sky pirate and others they've outright made crafted versions without role restrictions. Sets like late allagan where you have tanks and ranged dps in the same set. Sets like shisui or yorha dresses from copied factory that have no real 'job' or 'role' identity behind them. You have tank sets that are skimpy and you have healer sets with some armor on them. You have things like moogle costumes, job agnostic mog station and crafted gear, hempen sets, casual clothes, etc. The idea that a tank wearing a robe would clash with role identity is way past a moot point by now.

So I can get not wanting a black mage artifact on a scholar, or a paladin artifact set on a bard, or swapping out a dark knight's greatsword with a red mage rapier.

But I'd be 100% for the typical 'fending/maiming/striking/scouting/aiming/casting/healing' role sets being made inter glamable, even if you have to have a job leveled that 'can' equip a piece to glam it. Gives incentive to level multiple jobs.

[JamieRose]

I have a feeling that unshackling job restrictions from glamour, given the game's infamous spaghettie code, might actually be a bigger undertaking than I'd first imagine.

Is the code really that much of a mess? I mean it's not like YandereDev is on the coding team, right?

[Bright-Flower]

Is the code really that much of a mess? I mean it's not like YandereDev is on the coding team, right?

I couldn't say, I'm not on the dev team. All I know is that old 1.0 code has made things tricky for them in the past. I'm only guessing that this 'might' actually be harder to do with their current code than I'd initially guess, because sometimes when you're not famliar with how a piece of software works it's not always as clean cut as you'd first imagine.