Its time to remove job-based glamour restrictions.

[Rongway]

That's why I suspect it's more of a deep technical issue than the official answer of "job identity!" - obviously there's no good design reason why casters might be able to equip boots with gold decorations and healers can equip the exact same boots with silver decorations, but heavens forbid you ever try to wear the gold ones as a healer!

I struggle to think of how it could be at all a technical issue. If I had coded the current system as it functions today, the glamour validation check would involve, among other things, if item.EquipableBy.contains(currentJob). All that would be needed to allow all non-AF gear to be universally glamourable would be to change that one check to if (item.EquipableBy.size >= 2 or item.EquipableBy.contains(currentJob)).

In layperson's terms, this checks if the item is AF by checking how many jobs/classes can equip it. If it's exactly one, then the gear is AF, and it needs to check if current job matches. If it's equipable by more than one, it's not AF and glamourable by anybody. Of course, this only works so long as we have classes, since the defining feature for DRG AF and NIN AF currently is that they cannot be equipped by LNC and ROG respectively. Were we to eliminate classes, an AF flag would have to be added to all AF gear because you wouldn't be able to tell DRG general gear from DRG AF, or NIN general gear from NIN AF, just by looking at the list of equipable jobs. So in that case the check would be if (not item.IsAF or item.EquipableBy.Contains(currentJob)).

But it should really be as simple as this.

[MariaArvana]

bunch of comparison coding

Given how they've setup other systems in this game, I have a strong feeling that we're not actually "glamouring" an item per say, but ACTUALLY equipping it in a 'ghost' slot the game is using, which would make it impossible for any other job to glamour anything they can't actually equip. and the reason they use "job identity" as the PR response since it would take more time than they want to allocate to change.

[Iscah]

Given how they've setup other systems in this game, I have a strong feeling that we're not actually "glamouring" an item per say, but ACTUALLY equipping it in a 'ghost' slot the game is using, which would make it impossible for any other job to glamour anything they can't actually equip. and the reason they use "job identity" as the PR response since it would take more time than they want to allocate to change.

Glamours are linked to the item rather than you or your current gearset, though. Unless it's reading the "glamour instruction" on the item and placing it in the phantom slot every time you change gear, I don't think that sounds like the way it would work.

[MariaArvana]

Glamours are linked to the item rather than you or your current gearset, though. Unless it's reading the "glamour instruction" on the item and placing it in the phantom slot every time you change gear, I don't think that sounds like the way it would work.

It's simply my own hypothesis from the short time I spent coding, due to the fact they've intrinsically tied the glamour system to the equip conditions of the actual item. I doubt it's as simple as a simple byte value on the actual gear, or it'd be pretty easy to code around it, as all you'd need is to have a function to grab the appearance of the other item and override the graphic/model display function calls with the glamour piece instead, the equip conditions not even needing to be referenced.

Hence why I believe there's extraneous conditions, or the game is using some sort of 'ghost' slot for Glamour leading to the "You can only glamour what you can equip" issue, with "Job identity!" being their PR response. Either that or they're pretty adamant about their aesthetic choice and made it limiting on purpose. Who knows :shrug: