Request was throttled output message?

You are going over the DataStore request limit by attempting to save whenever a value changes.

There are four times that we should be saving to a DataStore:

1. When the player leaves the game. This should work most of the time.

2. When the server is about to shut down. We can't guarantee this will work, but we can try.

3. Auto-saving every few minutes. Attempting to save when the server shuts down or player leaves might fail for some reason, so we want to make sure the player only loses a few minutes of data at most.

4. After a player makes a R$ purchase, we should save immediately before accepting the purchase. This is very important. Players should never lose data after spending money.

You should wrap your DataStore requests in a pcall, since they can error.

Additionally, we should be saving and loading a dictionary as our player data. This is because it allows us to easily add and remove what we want to save at any time. Do this always, even if you only have one value you want to save at the time. It'll make your life easier, trust me!

Something I see a lot is that people forget to check if the attempt to load a player's data failed or not before saving. This is a must, because you can overwrite a player's data if you don't do this.

We can also avoid wasting DataStore requests on guests by checking if we're not in Studio's Test Server mode and checking their Player.UserId. Though guests have been officially removed from the platform, they're still around, and players can still join as them. The reason to check if the game is running in Test Server mode is that players all get negative user IDs in it.

Let's try something like this:

You may see a warning message about your data request being throttled when testing the game in Studio, because the game will both attempt to save the data when the player leaves, and right after when the game shuts down. It's fine to ignore this.

Additionally, your AddCash RemoteEvent is very insecure. Exploiters can fire it and get unlimited amounts of cash. The client should never be in the business of ordering the server to perform actions. They should never have access to a RemoteEvent that adds cash like that.

Your requests are throttled because you're sending too many requests. Here are the request limits. https://gyazo.com/cbbe05a6b679dc39a75b4563973a4054 To conserve requests, I've fixed some code below.

Inside ServerScriptService:

First of all, you should specify what player for your AddCash event in ReplicatedStorage. As of right now, it will change it for all players and use another request up. You can also take the saving for .Changed away due to it saving when they leave.You should change the script that sets off the BindableEvent by adding the player as the first argument. Also, there's no need to save data when they join, just load it. Also, the LocalScript already checks for .Changed, so no need to tell it to change the value if it already does.

Inside StarterGui:

I removed the event due to the reason explained above.

Inside the button:

You should add the player due to the extra argument I added in the BindableEvent.

I hope this helped, if you continue to have this issue, please comment below so I can edit and try to help you out!