Best Practices for Storing Player Data – Server Tables vs. Player Folders?

Hey everyone,
I’m currently reworking my game’s organization and wanted to get some input on how others handle player data.

Specifically:
Is it better to store player data in a server-side table or inside folders within the player instance?

I’ve been using folders inside the player to store things like stats and progression, which makes it easy to access and visualize in Studio. But I recently looked through some other developers’ code and noticed they’re storing everything in server-side tables. That approach seems cleaner and more secure, but it also means I’d need to use RemoteEvents every time data changes or needs to be accessed by the client.

I’m Looking For:

• What the pros and cons of each method?
• Is there a recommended standard?
• How do you handle syncing using server tables?

1 Like

U can only store data on the server anyway, so a “server side” table it is. And the difference between table and instances is mostly performance, but it’s subtle enough that u shouldn’t really care.

Syncing the server table depends on how u store it and I don’t really think security is that important since it’s server sided.

Either way, choose whatever method is the easiest and most convenient for u.

4 Likes

My bad, I got ahead of myself when I said security for server side tables.

3 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.