Do I really need to do a timed autosave?

Help and Feedback Scripting Support
#1

Although there are examples of timed autosave (for example, every 30 seconds for the player), I ask:

  • Is it really necessary to do a timed autosave?
  • Would it be safe to save all data just in BindToClose?
1 Like
#2

Timed autosave is fairly simple to make and cuts down on unreliability (so I dont see why not)
If the server crashes, if a client crashes (depending on how you set it up), those could all be major issues and they could use hours of progress
I think an autosave is a pretty nice and easy solution to a fairly big problem

#3

Thanks, I know it’s easy.
If the client crashes, I don’t see any problems, because all players’ data is in the server’s RAM.
My question is if Roblox Servers are trusted to the point that many developers save everything just in BindToClose?
Do you know of any real cases of data lost due to Roblox server failure?

1 Like
#4

I save using BindToClose, PlayerRemoving, and UpdateAsync

auto save should only be used if you need to use it, saving at the end is better because of the limits

1 Like
#5

You can if you want, the one I use in my games saves every tick, meaning no loss, and it also doesn’t lag yhe client or the server.

#6

I don’t believe this is possible since you can’t save before 6 seconds between saves.

1 Like
#7

you shouldn’t even do that anyways unless you only have one person in the server(the 6 seconds thing)

#8

Well what I mean is it instantly saves, there no delay whatsoever.

#9

I’ve just tried it, I added a mini time counter to test what you meant, I instantly joined and gave myself 100 coins then left, then did that twice and it added up, I don’t get what you mean by 6 seconds here.
@rogeriodec_games so I don’t know where you are getting this from, also I tried it with 2 other people in the server, worked fine.

#10

image
image1111×646 68.9 KB

1 Like
#11

Well thing is I use “GetPropertyChangedSignal” for mine and use a while loop to get data and stuff, so I think it ignores it because I use secondary values too.

#12

another reason auto saving is bad is because if multiple people are in the game you have more of a chance of hitting the limit

saving at the end is smart

#13

I have 3 games, in 2 I use player added and player removed, in only one I use this system. I would prefer not using timed but I’m only bringing it up for this forum, I can give an example of what I mean when I do get on my pc.

#14

I remember now that DataStore2 already does this, that is, it keeps all data in a cache (RAM) and only saves them at the end.

2 Likes
#15

To answer your questions:

  1. No. I believe people do it mainly for a ‘backup’ per se, just incase the server fails when they leave, although if you have a trustworthy method of saving data (i.e DataStore2), then this shouldn’t be an issue.
  2. Yes. This is something that DataStore2 (mentioned above) does, and it works fairly well. This would actually help if the server shuts down, not giving time for Players.PlayerRemoving to fire. I would suggest using it.
2 Likes