Real-time clock · mechanic

definition

Owns a mapping from the device or server clock to game time plus the last-seen timestamp. On launch or each tick, the real time elapsed since the last update is computed and the simulation catches up: needs decay, crops grow, timers finish, or a capped amount of progress is granted. Calendar dates trigger holidays and seasonal events. Tamagotchi (1996) ages its pet through life stages in real time; Animal Crossing uses the console's internal clock and calendar so time of day, seasons, holidays, and tree growth follow the real date, with music that changes each hour; mobile builders and idle games run construction timers and offline earnings on the device or server clock. Inputs are real elapsed time; outputs are catch-up updates and dated events.

player experience

A world that lives alongside the player's own day. Visiting at different hours shows different scenes, shops open and close, and holidays arrive with the real calendar. The player builds a daily habit, and absence has consequences, from weeds to a sick pet, so returning feels like coming home or like guilt.

design levers

ratio of game time to real time, 1:1 or compressed
catch-up rule for absence: full simulation, capped progress, or frozen
penalties or rewards for absence
calendar-tied events and how often content changes
handling of player clock changes

failure modes

Players change the device clock to skip waits (Animal Crossing players call it time travel), which breaks event pacing and timer economies.
Harsh absence penalties punish ordinary life events and drive players to quit after a missed week.
Content tied to real dates excludes players in other time zones or hemispheres unless the game adapts it.

dynamics

Daily check-in habits form, and with streak rewards they produce strong retention.
Offline catch-up must be computed in bulk, pushing designs toward simple closed-form growth.
Real-time waits become a resource that free-to-play games sell speed-ups for.