The issue there is localization. In the West a commode is a toilet, but in other parts of the world it means a dresser ir cabinet with drawers. They need to pick a different term for it is all. I know I stifled a laugh when I heard the term they used.


While I agree it ain't perfect it's certainly better than what we have.
200 slots ain't that bad for me. Excluding belts and weapons that's 40 sets of left side gear. And a massively freed up retainer inventory.
10 ensembles ain't that bad either for a start. Nothing to stop me glamiuorng my scholar using the current system and creating 2 ensembles for ast and whm.
It's not great but definitely a step up


And you don't understand the minuscule amount of data this actually would take.
First, all resources for displaying gear (the polygons, textures, shaders, ect) is all done on the local client machine.
Second, the data for a single character would fit in an unedited forum post.
Ever seen an IP address? That's Four 3-digit numbers ranging from 0-255 that gives 4 billion individual numbers. If they wanted to use hexidecimal in a similar fashion, they could have 281 trillion. Little more than 200 they're offering. Just a little bit.
All they need to do is flip a bit to true everytime you obtain a unique look (not all gear has unique looks, many share them) for a slot. The hardpart would be the initial system that detects all gear you currently wear, armory chest, armoire, inventory, and retainers. That could be done in encrypted form locally and send a small number to the server to unlock the items for use.
We're talking less bytes than a typical Free Company advertisement. That FC that doesn't shut up day in and day out trying to zerg invite costs more server load than 10,000 characters would logging in with this system.
Instead they go with a system of 200 slots that could fit any visible item (including redundancies). A system that is going to tax the memory of the PS4 through the UI. Sucks to be them I guess. And one that will be constantly updated as players put things in and out. Not very efficient in my opinion.


In this fashion if they did it hexadecimally each byte of informantion could cover 4 unique looks. in a binary sequence.
so unique look 1 would be 1. unique look 2 would be 2 unique look 3 would be 4. unique look 4 would be 8. etc etc.
so if a player had looks 3 and 4 but not 1 and 2 the byte would simply be a C. if a player had looks 2and 3 the bit would be a 6. or all 4 would be an F.
in this fashion then the small String of "FF FF FF FF FF FF FF FF" could account for 64 entries within the glamour log based on a simple true/false switch on whether that glamour is unlocked or not.
"FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF" would be all the data required to store 256 unique looks within a glamour log catergoriy.
this equate to just 32 bytes of information.
if you added that up. across all gear slots you could store 256 looks for every slot in the glamour log and it would total 384 bytes per character.
which would then mean 2604 characters glamour logs could be stored in a single megabyte of server space.
Which to illustrate would equate to over 3,500 players glamour logs being stored on a single 3.5 inch floppy disk
Last edited by Dzian; 12-17-2017 at 09:54 AM.



Try "Kommode" (german for commode) or "french commode" with google. I think only english speakers use commode for toilet.
The word itself come from french
Last edited by Felis; 12-16-2017 at 06:40 AM.


Does the commode let you wear anything you want? or is their still a job restriction on it?




I live in western US, and never even heard the term 'commode', and I'd wager most around my area are also unfamiliar with it. We could sooner tell you what a bidet is, and we don't even have those here.
But why has the conversation shifted focus on the use and semantics behind a word?
Anywho. This is definitely a step in the right direction, and sure in hell more than what we have now. If anything, we know that SE has finally acknowledged glamour being a true endgame. Yet, the griping continues.



Just a note that 'C' is a byte, not a bit.In this fashion if they did it hexadecimally each bit of informantion could cover 4 unique looks. in a binary sequence.
so unique look 1 would be 1. unique look 2 would be 2 unique look 3 would be 4. unique look 4 would be 8. etc etc.
so if a player had looks 3 and 4 but not 1 and 2 the bit would simply be a C. if a player had looks 2and 3 the bit would be a 6. or all 4 would be an F.
in this fashion then the small String of "FF FF FF FF FF FF FF FF" could account for 64 entries within the glamour log based on a simple true/false switch on whether that glamour is unlocked or not.
"FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF" would be all the data required to store 256 unique looks within a glamour log catergoriy.
this equate to just 32 bytes of information.
if you added that up. across all gear slots you could store 256 looks for every slot in the glamour log and it would total 384 bytes per character.
which would then mean 2604 characters glamour logs could be stored in a single megabyte of server space.
Which to illustrate would equate to over 3,500 players glamour logs being stored on a single 3.5 inch floppy diskIf they're using an 8 bit encoding (which is fairly standard these days), each letter is 8 bits. A bit also can't be 6, because a bit only has two valid values: 0,1. You need 3 bits to represent 6: 110. You're more or less correct otherwise in describing a bitmask format.
Every byte in this case could store 8 entries. 10,000 entries would be 1,250B, which for the client is trivial and would only require retransmission from the server upon logging in. For the server you're looking at multiplying that by several thousand logged in people and moving it around, which pushes it up into MBs, but it would be pretty odd if that was game breaking, and I don't think the server actually even needs it in memory all the time. Really, the server only needs it when the client says "I want to glamour to this" (to check if you have that glamour), "I want to unlock this glamour" (to save the relevant data change), and "I'm logging in, send my client the updated list."
You'd also want audit information about how and when something was unlocked, but those can be stored separately as it's only needed for the support & security teams.
Well Id love a glamour log, and Id take the restriction of only being able to use it from my Inn room or from a piece of furniture I place in my house/apartment.
I won't pretend to understand server limitations because I don't.
But, I also don't understand how an instant replay feature, with options to replay from every team members point of view, including the bosses, is less of a server load than a list of clothing skins that players can access in an inn.
So why are we limited to only 200 favourites and not the glamour log book everyone has been straight up begging for.
Last edited by Tigerlilley; 12-16-2017 at 09:16 AM.
|
|
![]() |
![]() |
![]() |
|
|
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.


Reply With Quote

If they're using an 8 bit encoding (which is fairly standard these days), each letter is 8 bits. A bit also can't be 6, because a bit only has two valid values: 0,1. You need 3 bits to represent 6: 110. You're more or less correct otherwise in describing a bitmask format. 

