Update - Disconnects and Latency Issues

Because all items have IDs. It's a database, you can't just opt out of certain things generating identities. You have to have some unique way of identifying and referring to the object in memory after all, otherwise how would you tell one from the other? Just because they stack you don't suddenly not need to tell them apart.

Stackables have the most overhead, since they have to destroy one version and increment the counter of the survivor when merged, then spawn a new item and a new id when separated.

...was going to write a whole post of statements and questions about rowids and application ids and fields in tables and pointers to other tables but, bottom line is, the way Nexon set up their database is obviously nothing like I would have (I'm not a DBA. I've developed projects that used Oracle, but usually in a fairly trivial manner), so I'll not trouble you to explain it.