Is DataStore still good today?

Help and Feedback Game Design Support
1

Hey!

I am not sure about which wrapper (DataStore2, Profile Service) to use or if I should use just the normal Datastore…

I heard great things about both but these issues are making me unsure:
DataStore2: currently has bugs (Example: Update())

ProfileService: I don’t see bugs but I don’t want players to take a whole min to load into the game (This could cause them to get frustrated and leave)

And for DataStore (Normal ROBLOX datastore) has been around forever but could make players lose their data…

Would really appreciate feedback on which one is best :slight_smile:

2 Likes
2

Is that a thing with ProfileService? I’ve never heard that before.

2 Likes
3

One possible reason for ProfileService to take a long time to load is probably due to the fact that it uses Session Locking. Session locking helps prevent overwrites when rejoining on multiple clients or fast rejoin which helps with preventing duplication bugs.

Datastore2 Pros:

  • Automatic Backups

Datastore2 Cons:

  • No Session Lock

ProfileService Pros:

  • Session Lock

ProfileService Cons:

  • No Automatic Backups (I don’t believe it does)

I’m sure there are more, I’m just pointing out the major ones

In terms of which one you should use, Adopt Me utilizes DataStore2 (I believe) and they have a trading feature and I haven’t heard of any form of duplication glitches. The less transactions you have in your game the more the reason to use Datastore2.

1 Like
4

Yeah, sometimes if the script can’t find your profile it COULD take up to a minute to load which might seem frustrating to the players :sweat_smile:

5

Oh wow! Thank you! This really made things a bit more clear

6

ProfileService was never a think. Also, API Services Datastores works very efficiently nowadays and they have became smoother and easier then before.
They still hold an important position and are still good till today.

7

By “think” did you mean thing? ProfileService is a wrapper for the datastore made by loleris.

Ooooh, have u seen any data loss when u use the normal datastore? I am trying to prevent that

8

It is a rare hypothetical and shouldn’t be the deciding factor of not using ProfileService. It is made for a project with massive scalability as it has a very low foot-print. In contrast to its pros, the source code is quite unique and frankly hard to understand. On the other hand, DataStore2 is kind of discontinued in its development due to being finished, however, it has been used for loads of projects and for its purposes it is known to have no-fault. Maybe consider making your own DataStore if you’re serious about this.