GAME MECHANICS HOARD

SCHEDULING SYSTEMS

Time-slot programming of recurring behavior — colonist daily schedules assigning sleep, work, and recreation by hour; NPC routines that put the blacksmith at the forge by day and the tavern by night; player-authored timetables for shifts, patrols, and services.

RimWorld's schedule grid is the player-facing classic (paint each colonist's hours, and night-owl artists coexist with dawn farmers), Oxygen Not Included staggers shifts so bathrooms and mess halls don't stampede, Ultima VII and Stardew Valley built world-believability on NPC clockwork (schedules are what make a town feel inhabited — and make befriending the fisherman require learning his Tuesdays), and transport sims run literal timetables. Designers expose scheduling because time is a resource layout, exactly like space: a day has fixed hours the way a base has fixed tiles, and allocating them — recreation before stress breaks, sleep staggered across shifts, work hours matched to daylight — is optimization with the same texture as floor planning, but along an axis most games leave automatic. Player-authored schedules are also delegation's most legible form: a schedule is a standing order the player can read at a glance, unlike buried behavior trees. On the world side, NPC schedules do double duty — simulation believability and gameplay surface (the guard's dinner hour is the infiltration window; scheduled lives are what make both stealth timing and social sims possible). Key decisions: granularity (hourly paint-grids versus rough day-phases — finer control, heavier interface), exception handling (emergencies overriding schedule, and how behavior resumes), and observability of consequences — players tune schedules well only when the results (tired workers, queued toilets) trace visibly back to the timetable. Pitfall: schedules that don't survive contact with the simulation — when pathing delays, interruptions, and cascading events mean the schedule is aspirational fiction, players stop authoring what the world won't honor; the grid must bind, or it's a spreadsheet of wishes.

SEEN IN

ALSO FILED UNDER

VIEW “SCHEDULING SYSTEMS” IN THE MAP ▶