Overall the Armoire should be able to have more stuff in it and not limited to stuff from an ach etc.
But well, would not count on it happening.
Overall the Armoire should be able to have more stuff in it and not limited to stuff from an ach etc.
But well, would not count on it happening.
Last edited by White_Wolf_X; 09-10-2021 at 11:19 PM.
What they need to do is fix a proper glamour log. Glamour is the one true end-game and our very own inventory shouldn't be a hurdle for it.
Honestly if we could just store our upgraded AF sets in the armorie it would clear up swathes of my retainer inventory alone.
They've said it's very limited on what they can put into the armoire, just seems like another technical limitation. People have been asking for this for years.
While I'm sure we'd all love more glamour storage, pretty sure the only way that's gonna happen is if they strip down the existing system and rebuild it from the ground up. I remember that we can't have glamour chests in homes/FCs because it will just crash the server, so I wouldn't be shocked if adding extra space or changing things in general is out of reach due to how the originally implemented the system. Will they fix it for EW? Probably not, most likely the only side time they had went to bun boys or other mogstation related cosmetics. We can wait and see though.
Totally agree with this.
If you pay 12 bucks or so for a dress, that should includes a free space in the armoire and not using your inventory or retainer.
- Queen of Heal 2022 -
Hahahaha. Blade & Soul wants to talk to you about their cash shop items and the need to buy additional wardrobe space.
I'd very much welcome more storage space. They've said they can't implement a proper glamour log either due to technical limitations. I think we all know they have to start doing something drastic to the crazy inventory bloat, a new expansion is going to again make it so much worse. I know the devs are aware of the problem, all I can hope is that they come up with some sort of real solution. Adding another 100 slots to the glamour dresser just doesn't cut it and they know it's not sustainable, otherwise they'd have added another 1000 slots in there already, it must take a lot of server space with that system.
It's just the housing system all over again, band aids on top of band aids is not a real solution.
My guess, as I've noted before, is that their storage backend likely was not designed with support for sparse bitfields as a data type.
To explain, imagine you have a checklist; each row has a checkbox, and the name of a piece of gear. As you get that gear, you go down and check off the checkbox. This list can be represented as a 'bitfield' -- basically, a series of the 0s and 1s that make up binary numbers. So, one byte (8 bits) can represent 8 pieces of gear. The armoire is almost certainly stored as a bitfield, since all it has is "is this gear in the armoire or not", no dye information or HQ or anything else, like the glamour dresser does.
Now, an approach like this is fine when you have a short checklist, but if your checklist is, say, a million items long and is going to continue to grow, that begins to be a Problem. Moreover, the most effective way to do this is use the existing item IDs as the bits.
So, according to the lodestone, the Augmented Cryptlurker's Robe of Healing is "ac97d9229b0", or 11860511435184 -- assuming that is the internal item ID (which seems quite possible, as it's how Lodestone refers to the item), that's what we'd need to use in a bitfield; toggle on the 11860511435184th bit in a single number. However, it would take 1.3 terabytes to store a 11,860,511,435,184-bit number -- and that's assuming they never added another item to the game beyond that one. Obviously, using 1.3 terabytes of storage for each player's armoire wouldn't be ideal... and that's without even getting into the fact that you'd have to load that value into memory to check for a bit being on or off.
Now, you could do a translation table of things like "item ID 11860511435184 maps to gear ID 89764532" but that has other issues.
The proper way to solve this is a sparse bitfield; it's a bit beyond the scope of this post to explain how they work, but you could store someone's gear checklist in a much smaller number; easily fit into on-disk storage and suchnot. However, if your backend storage system—and the engine, and the network protocol—doesn't support sparse bitfields, retrofitting it in could be a potentially large task.
My standing assumption is that's the obstacle to the armoire holding more stuff; it's one thing to have, say, a 1024-bit checklist (only 128 bytes!) and a lookup table saying "item X is bit 873" or whatever, but it becomes another thing entirely to try to have a checklist of all gear well after the fact.
Doesn't mean it can't be solved, just that my guess is that it wouldn't be a small task to do so. :/
I aim to make my posts engaging and entertaining, even when you might not agree with me. And failing that, I'll just be very, VERY wordy.Originally Posted by Packetdancer
The healer main's struggle for pants is both real, and unending. Be strong, sister. #GiveUsMorePants2k20 #HealersNotRevealers #RandomOtherSleepDeprivedHashtagsHere
|
![]() |
![]() |
![]() |
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.