Keep reward amounts on the server

local data = { coins = 0 }
data.coins += 10
player:SetAttribute("PracticeCoins", data.coins)

The published attribute reflects the server record after a server-owned transition.

New syntax: server-state, authority

• remoteevent
• communication
• client-server
• replication
• authority

Main guided reference implementation; use the hierarchy’s stated Script or ModuleScript type.

local Players = game:GetService("Players")
local records = {}
local function initialize(player)
    if records[player] then return end
    local data = { coins = 0, welcomeGranted = false }
    records[player] = data
    if not data.welcomeGranted then
        data.welcomeGranted = true
        data.coins += 10
    end
    player:SetAttribute("PracticeCoins", data.coins)
end
Players.PlayerAdded:Connect(initialize)
Players.PlayerRemoving:Connect(function(player) records[player] = nil end)
for _, player in ipairs(Players:GetPlayers()) do initialize(player) end

PlayerAdded alone can miss players already present when code starts; cover GetPlayers as well.

Do not publish the entire private record to every client; only publish the needed display field.

This is a bounded learning lab. It has not been executed in an approved Roblox Studio environment by this website.

A checked checklist records your own review, not automated project competence or a community verification.

The server owns the practice coin record. It publishes a read-only-for-gameplay display through an attribute; clients may display their local replica, but cannot authorize a server update by editing it.

This lab awards a fixed welcome amount during server initialization, once per Player object. No client reward request exists. The next lessons add validated requests and duplicate prevention.

Ownership means the server decides amount and transition. A visible attribute is not itself a secure persistent datastore, and a screenshot is not evidence of server validation.