Update - Disconnects and Latency Issues

My only concern here is that this would involve a complete re-design of the save system. While this method is far superior to the current, it isn't very achievable (considering how much Nexon LOVES change).

The Item IDs, while still a major revamp, would seem to be easier to implement. I don't think any other major issues (besides duping) arise from the current save method. Might be missing something, though.

Yet again; The item IDs already exist and always have.
Adding them if they didn't exist is far more invasive than adding a transaction declaration at the begin and end of the save process.

You're at a handicap here if you don't understand the client server relationship or their database architecture so you should probably stop trying to explain how best to fix the situation.