Wardrobe-System. What do you think?

[TaranTatsuuchi]

Better glamor system would be nice...

[Skivvy]

I'm not as familiar with BnS's glamour system, but it seems sort of similar to GW2 - and I would LOVE to have that copied and dropped into this game. Basically, all of your weapon and armour "skins" are saved once you either equip, or specifically unlock the skin. After this point, no need to keep the original item. That would be amazing.


XIV needs a lot of help when it comes to wardrobe storage.

[rabbitzero]

Someone may have mentioned it, and i just missed it, but i'd actually prefer what WoW is doing with theirs in Legion. It records everything you could have gotten from quests and gives you access to it, even before this feature was added. At least that's the promise. Keep in mind though, it took WoW over 10 years to get this in, after having transmog and void storage, which was only added after removing keys or some such that made room for the data of item looks.

I say this as someone who has two and a half retainers full of glamour gear.

[CrystalWeapon]

People seem to be overestimating how taxing a sytem like this would be. A glamour log would work similarly to how our seasonal armoire chest works or how our crafting and gathering logs work. It's just a list of boolean flags. Is this item stored? Has this item been crafted? Have you gathered this item before? yes? no? This works in a completely different way than what our inventory system does.

Not all data associated with our characters is backed up every 15 seconds. This is specific to our on hand items. I'm damn certain the servers aren't derpy enough that they are constantly doing checks on what's in all of my retainers when I'm running a dungeon. If done right a full glamour log would only be doing a verification on your items when you change equipment, and would only request the full listing of flags when you bring up the glamour menu. Ex: When you change your helmet the game would send a request to check serverside whether or not the flag has been activated for owning helmet #87.

The only time it would need to send the entire listing of boolean flags is when you open up the glamour menu. Even this request shouldn't eat up too much traffic as at the most each flag would be 1 byte. With more efficient coding you can bring this down to 1 bit per item. Iirc this is how the mog slips work for storage in xi. Each bit in the bytes used to store the mog slip's information is used as a flag. Each individual bit is assigned an ID that matches up with an item. A 1 is a flag that the item is stored on the slip. A 0 is a flag that the item is not stored.

If this truely was some insurmountable task then glamour logs like this would not be including in just about every single modern mmo on the market. Repeating myself here. Again, we've already got quite a few logs like this already in place. The game already has boolean flags to keep track of: What items we've gathered for every class, What items we've crafted for every class, what portions of the map we've already uncovered, what mounts we've unlocked, what minions we've unlocked, what emotes we've unlocked, etc... These logs take up next to no space at all.

With the last response on the issue given either there was a misunderstanding on what exactly the players were asking, or they are prioritizing more important matters first. I'm willing to bet it's the latter, and the excuse was a way to pacify players who have little to no programming background.

[TaranTatsuuchi]

People seem to be overestimating how taxing a sytem like this would be. A glamour log would work similarly to how our seasonal armoire chest works or how our crafting and gathering logs work. It's just a list of boolean flags. Is this item stored? Has this item been crafted? Have you gathered this item before? yes? no? This works in a completely different way than what our inventory system does.

Not all data associated with our characters is backed up every 15 seconds. This is specific to our on hand items. I'm damn certain the servers aren't derpy enough that they are constantly doing checks on what's in all of my retainers when I'm running a dungeon. If done right a full glamour log would only be doing a verification on your items when you change equipment, and would only request the full listing of flags when you bring up the glamour menu. Ex: When you change your helmet the game would send a request to check serverside whether or not the flag has been activated for owning helmet #87.

The only time it would need to send the entire listing of boolean flags is when you open up the glamour menu. Even this request shouldn't eat up too much traffic as at the most each flag would be 1 byte. With more efficient coding you can bring this down to 1 bit per item. Iirc this is how the mog slips work for storage in xi. Each bit in the bytes used to store the mog slip's information is used as a flag. Each individual bit is assigned an ID that matches up with an item. A 1 is a flag that the item is stored on the slip. A 0 is a flag that the item is not stored.

If this truely was some insurmountable task then glamour logs like this would not be including in just about every single modern mmo on the market. Repeating myself here. Again, we've already got quite a few logs like this already in place. The game already has boolean flags to keep track of: What items we've gathered for every class, What items we've crafted for every class, what portions of the map we've already uncovered, what mounts we've unlocked, what minions we've unlocked, what emotes we've unlocked, etc... These logs take up next to no space at all.

With the last response on the issue given either there was a misunderstanding on what exactly the players were asking, or they are prioritizing more important matters first. I'm willing to bet it's the latter, and the excuse was a way to pacify players who have little to no programming background.

Yeah, I remember reading something a while back on the subject where they used this with the entire amount of items in the game to show how much total size the entire log would take... And it wasn't that large.

[AeraLure]

With the last response on the issue given either there was a misunderstanding on what exactly the players were asking, or they are prioritizing more important matters first. I'm willing to bet it's the latter, and the excuse was a way to pacify players who have little to no programming background.

That and they don't want to now, as they would lose the extra retainer income. Cancelled the ones I had, to show that I do not support it, but in the end I feel like I am just gimping myself.

[Ageofwar]

a lot of stuff

implementing a Enhanced Armoire or Mog slip system is in theory possible if only the following data is needing to be stored:-

User ID, Item ID

with the following restrictions:-

you have to own the items to store it (and i mean store it, for abuse propose)
only one copy of each item can be stored (to reduce data)
Pink items and relics can't be stored (to much info needed to be kept)
Durability has to be 100% or above (if above value is reset to 100%, to reduce data, for abuse propose)
item has to be un-dyed (to reduce data)
spirit bond level will be reset to 0% on storing item (reduce data)
materia has to be removed to store item (reduce data)

[Laelius]

I'd be glad, my retainers would be glad, who wouldn't?! SE, hop hop!

[Alexander_Dragonfang]

Blade and Soul and Guild Wars 2 can manage excellent Wardrobe systems. XIV? Not so much.

Whats the diference? If you ask me, the diference is care, thats all there is to it really. B&S and GW2 cared enough to create and implement such systems. On the other hand, the best people is ever going to get done about this in this game is maybe, 2 extra free retainers as the paid retainer cap is increased to 12.

[Ilitsa]

I'd love this system to be put in, or at the very least a "chest" that can be crafted that allows us to deposit anything we wish into it (lke an armoire chest for crafted/dungeon gear) and make us go back and pick it out again to glamour. SOMETHING needs to give though in the long run