Bug hunt — game systems

Your game systems work — until one of them quietly doesn't. The classic system bugs are less about syntax and more about who decides and when things run. A price checked on the wrong computer, a loop without a breath, a function connected with parentheses. Hunt them:

#Hunt one — the check on the wrong computer

The shop button dims when you can't afford something, and an exploiter just bought everything for free.

-- LocalScript — on the player's computer
if player.leaderstats.Coins.Value >= 25 then
    purchaseEvent:FireServer("multiplier")
end

#Hunt two — the function that ran too soon

The button does nothing. No error, no click, nothing — and the log shows the handler fired the moment the script loaded.

button.Activated:Connect(myFunction())

#Hunt three — the coins fountain

Idle income is paying out thousands of coins a second, and the game crawls.

while true do
    for _, player in ipairs(Players:GetPlayers()) do
        player.leaderstats.Coins.Value += 1
    end
end

#Hunt four — the silent mismatch

Clicks still give coins — the leaderboard climbs — but the on-screen label never moves.

-- server script
clickEvent.OnServerEvent:Connect(function(player)
    ...
end)

-- client script
clickEvent.OnClientEvent:Connect(function(total)
    label.Text = "Coins: " .. total
end)

#Hunt five — type the fix

The idle loop should pay every player one coin each second. Type the corrected loop header so it doesn't freeze the game.

while true do
end

#Hunt six — arrange the purchase

Put the server's checkout counter in order: reject unknowns, check the wallet, spend, tell the client.