Pay offline earnings with a cap, and survive a phone clock set backwards

Welcoming players back with what they earned while away is a core pleasure, but the same sum can be farmed by moving the clock, and a negative gap can even take coins away. This entry covers the cap, the efficiency, and what to do when the clock has gone backwards.

Why this works

The phone clock belongs to the player, so any reward based on it can be farmed. A cap limits how much one absence can pay, and never moving your saved time backwards means only time that truly passed is ever paid, however often the clock is changed.

When not to use it

Skip it when the game has a server and the reward matters, such as a shared ranking or paid items: ask the server for the time and the earnings. Also skip it when your game is not about waiting; offline pay then only teaches people to leave.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 24 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 "Pay offline earnings with a cap, and survive a phone clock set backwards" (read_entry offline-earnings-cap-and-clock-back) 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