[quote] “The problem I have is constantly retrieving updating these tables and being able to save it every time it updates,”
Yes, this is the problem. You should really take a look at my PlayerDataStore module and see how it handles the problem. You can both store everything in one big table for the most part and also only make one request every minute or whatever for autosave. If you do both the current request limit is easily high enough for everything except for things that still wouldn’t be possible even with triple or even more over the current request limit.
And that isn’t a “hack” or something like that: That’s the way real software works. No real game-server is saving to a datastore every single time that someone gets a KO, they do the same caching and batched requests that I’m suggesting that you use.
I’m not saying that the current request limit is “final” in any way, but I am saying that any increases to it will not actually fix the problem like you think they will. [/quote]
I’m currently stuck at 1,200 max furniture per store. Can I at least request you bump it to 128kb? That would cut down on how many stores we use, and give people less excuses to ask for more data stores.
Unfortunately the key-size is limited by the backend database that we’re using, it’s not an arbitrary limit set by us. No database will let you store huge amounts of data like that in single keys, because that’s not the “correct” way that those databases are expecting to be used.
The old DataPersistence on the player object let you do some pretty non-database-ey things because… it wasn’t a database. Which is also why it didn’t have any backups or anything like that.
Ah, well then I have on small request, instead of making it 60+10x, can we have 20x and no +60? I say this because some of us would like to store more data (yes, even cramming using tables) but would love to have an easier estimate of how much can be stored. Thoughts?
Ideally you should not be using the “60” at all for things related to per-player data exactly because it’s not tied to players. The point of the “60” is for doing something like an in-game global leaderboard display, which at startup needs to query the names / stats of a bunch of people or something like that.
You should more aggressively put your per-player data into as close to a single key as possible, that’s the correct way to use the DataStores right now.
Thanks, never knew what that was for. I already stated though, I`m stuffing LITERALLY as much as I can (1,200 furniture, somewhere after that it stops saving…) into each store, all I need is just 5 more at least per player to help the trading system work properly.