A consern about space efficieny since stormblood is not getting enough space increase

[Lycieus]

Because what works in other MMO's works in OTHER MMO's.

FFXIV favors speed and safety, have you heard of any widespread crashes and rollbacks? Now go look at pretty much all freemium RPG's. It's a regular thing because that's how "dupe bugs" work in other games. The game server has one copy, and the filesystem has another and doesn't write to it for long periods of time. So if the bots and hackers want to dupe items, they just load up their bots to do whatever activity will crash the server, and when the server reboots, they now have duplicate items.

Are you referring to freemium in the literal sense, or is this just a blanket term for all f2p mmos?

Also, I'm not exactly sure what your point is. Duping is bad, I think everyone can agree, but it's not a major issue in any MMO I can think of that I've played or can think of. Square has had issues with people exploiting gil and items anyway in the past. Is your post supposed to be some sort of excuse for them to not solve this problem because their execution might be shoddy?

[Shurrikhan]

3. Go into a dungeon or some part of the game that you know can be crashed
4. As the crashing begins (usually no other users can login) trade the item to your buddy and then have them log out. Meanwhile you stay logged in so that when the data rolls back you will still have the item, but since your buddy logged out, their copy of the item has already been written to disk.

Remind me of which dungeons in this game can:
1. be crashed on demand
2. in a manner that would allow you to trade items WHILE crashing

Also, I'm not exactly sure what your point is. Is your post supposed to be some sort of excuse for them to not solve this problem because their execution might be shoddy?

Same question. I really cannot tell.

[KisaiTenshi]

Remind me of which dungeons in this game can:
1. be crashed on demand
2. in a manner that would allow you to trade items WHILE crashing

Even if I knew that, I would not share it publicly, I'd report it to SE. Please don't derail the topic by taking things out of context, I even said that was a very generalized explanation.

As stated in the previous post, the safety of the game is paramount, and SE clearly wants to prevent widespread damage should some kind of inventory bug pop up. They stay submarined for a very long time because the botters, hackers, and other script kiddies want to abuse it as much as possible before they are caught.

If they are backing things up every 30 seconds, that is often faster than any such bug can be induced, let alone recovered from. If they are only backing things up upon zone change, which is what the previous example was based on, that is how dupers get away with it, and dupe-collision bugs can also destroy those items by having the duped item put on the market and suddenly disappear from the buyers inventory when the collision happen during maintenance.

There is an entire chain of damage that can be created from a single bug, and so far we've not seen any version of this except when SE went and deleted large sums of gil from players during the 2.0 era. Players who had dealt with duped items had their gil decimated.

[Lycieus]

There is an entire chain of damage that can be created from a single bug, and so far we've not seen any version of this except when SE went and deleted large sums of gil from players during the 2.0 era. Players who had dealt with duped items had their gil decimated.

So your point is we can't have a glamour log because Square-Enix exclusively can't deal with these sort of issues?

[savageink]

So your point is we can't have a glamour log because Square-Enix exclusively can't deal with these sort of issues?

Lol! She does seem to be arguing for their incompetence.

[Shurrikhan]

There is an entire chain of damage that can be created from a single bug, and so far we've not seen any version of this except when SE went and deleted large sums of gil from players during the 2.0 era. Players who had dealt with duped items had their gil decimated.

In that case, at what point in design is SE, if so incompetent, not opening themselves up to exploits?

Release 2.0's bug, wherein item count was carried client side, iirc, allowing Allagan coins to be multiplied by 99 and sold off 98 at a time, infinitely, may be evidence of prior incompetence, but it doesn't say anything about what would likely go wrong with a glamour log. What bugs, specifically would you expect to occur?

[OcieKo]

In that case, at what point in design is SE, if so incompetent, not opening themselves up to exploits?

Release 2.0's bug, wherein item count was carried client side, iirc, allowing Allagan coins to be multiplied by 99 and sold off 98 at a time, infinitely, may be evidence of prior incompetence, but it doesn't say anything about what would likely go wrong with a glamour log. What bugs, specifically would you expect to occur?

If handled like the gil duping example, a person could feasibly change all the 0s in the script for 1s and just hand themselves a full log for nothing. Should be possible to mostly save it client side while making a server side save upon log out, and using said file to double check upon log in. Might make it take a bit longer to log in/out and extend the time your character is tied up after a disconnect, but probably less than constant info transfers. Someone with more (or any really compared to me) experience in network coding may be able to explain it better.

[Shurrikhan]

If handled like the gil duping example, a person could feasibly change all the 0s in the script for 1s and just hand themselves a full log for nothing. Should be possible to mostly save it client side while making a server side save upon log out, and using said file to double check upon log in. Might make it take a bit longer to log in/out and extend the time your character is tied up after a disconnect, but probably less than constant info transfers. Someone with more (or any really compared to me) experience in network coding may be able to explain it better.

I guess I just rreeeaaaallllyyy want to hope that SE wouldn't break Rule 101 (don't trust the client, let alone hand them the ability to manipulate their stats, states, or inventory) twice.'

I really wish I knew more about these things; all the stuff I've found so far has said that when an item is added to one's inventory, in any form, it's added to the server listing for that player, while all the client side caches is the information tied to those items' tags and their arrangement within the inventory.

In my experiences being hacked multiple times and having my inventory rolled back in WoW this would also appear to be the case. The way GMs explained this to me is that they simply sort all server item transactions by player, formulaically flag them for suspicious activity within the reported date parameters, and then revert all changes between the chosen point and the reporting date.

In either case, it doesn't appear that there ought to be any way for the player to manipulate a server list.

But again, I know nothing about this. I'm just summarizing some hour's insomniatic research and anecdotal findings.

[Niwashi]

If handled like the gil duping example, a person could feasibly change all the 0s in the script for 1s and just hand themselves a full log for nothing.

But that bug was (or the hypothetical one would be) based on client side control of server side data. That's why you never let the client control such data. Keep it where it belongs, and no such abuse can take place. The fact that a horribly designed feature could be vulnerable is no reason to avoid implementing features. It's just a reason to not design them so horribly.

[Niwashi]

Back in 2014 they seemed to think a glamour log was feasible enough. They were just trying to decide how much other information it would also include.

0:52:08
Q: Is there any update on the weapon and armor log?

A: We've currently finished off a lot of the details, but we have to plans for implementation, we've been estimating the amount of work for each. The first idea would simply have players building a collection of weapons and armor, while the second idea would allow players to read the lore surrounding the gear they obtain. However, this data will affect the player data used in real time, so we are carefully investigating this at the moment. Next week we will reach a conclusion and proceed for actual implementation, but if we decide to go with the first idea it will be implemented in patch 2.4. In the case we decide on the second option, it will be implemented a bit further in the future. In any event, we've progressed quite a bit on this and we will have our verdict soon enough.

Since they thought at that point it would be implemented in the next major patch if they went with the simple version just recording what gear we do and don't have, I'm guessing they decided on the more in-depth version giving detailed info about each item, and then it got bogged down in coming up with all that background info. They took what would have been an enormously helpful feature that they could have done if they'd kept with the simple version and instead expanded it into something too big to actually get finished/implemented.