Players set their phone clock forward to collect a week of offline rewards

Rewards for the time a player was away only make sense if nobody can lie about how long that was. Here is whose clock to trust, how to stop long absences from being worth too much, and what to do when the numbers make no sense.

Why this works

Anything the player's device says about time can be changed by the player, so the only trustworthy measure is the clock of the server they cannot touch. Letting the device only lower the credit, and paying less per hour for long absences, removes the reason to cheat.

When not to use it

Pointless in a game with no online server, or one where rewards do not matter to anyone else. Then a simple local timer is fine. It also feels wrong if the game punishes people for taking a long, honest break.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• A diagram of every state
• 15 lines of example code with 5 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Players set their phone clock forward to collect a week of offline rewards" (read_entry away-time-credit-from-server-clock) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP