Define how the game clock advances
game-world-design requires delayed matters to return to the decision surface; game-build constrains due events and settlement. Time may advance by turns, events or real time. Choose what fits the game rather than charging every menu and reading action.
Original game: an island courier promises to return a signed receipt before the third ferry departure. Each cross-area action advances a period; inspecting acquired records does not. Players can see the current period, schedule and delivery route before leaving.
These are example rules, not universal values. Clear advancement rules let players know whether reviewing evidence spends the deadline. Real-time waiting needs separate pause, focus-loss and reading behavior.
Give the deadline an origin and a settlement
| Record | Ferry task |
|---|---|
| Origin | Player promises the crew to return a receipt |
| Carried facts | Who promised, location of the document, witnesses |
| Due condition | Check before the third departure begins |
| Status | Pending, delivered or missed |
| Return to attention | Route cue and an active crew reminder |
| Settlement | Delivery or a revised arrangement after failure |
The promise creates the matter. Entering the harbor must not create another copy. Stop reminders after settlement and do not revive failure as a fresh pending task.
Timing matters. If last-minute delivery is allowed, resolve it before departure. A program that departs first and handles submission later silently changes that rule.
Make missing it change an opportunity
Delivery lets the crew carry the document, enabling a later recipient to verify an arrangement. After a missed departure, the courier must wait for another ferry, use an established alternative recipient or acknowledge the broken promise.
An unexpected passerby should not automatically solve the core task. Missing a deadline also need not permanently close the whole story. It may reduce today’s opportunities, change meeting order or require another commitment, according to the declared experience.
Put knowable deadlines and costs beside affected choices without exposing every ending. A reminder, changed ship position or brief cue can convey pressure. An exact seconds counter is optional.
Check boundary timing, settlement and loading
Compare early, boundary-time and missed delivery from the same task state. Record advancing actions and the actual due check, ensuring outcomes follow choices rather than animation length.
Load before the deadline and ensure no early departure. Load after settlement and ensure no repeated reminder or reward. Repeated submission must not resolve twice. These checks establish deadline behavior; observing players determines whether the pressure feels compelling or irritating.
After changing schedules or route costs, replay affected paths and align design with implementation. A countdown changed without its rule undermines trust, as does an unannounced reduction of an established deadline.
FAQ
Must a missed deadline permanently close a route?
No. It can change daily opportunities, meeting order, later cost or renegotiation. Choose the intended consequence, then make the deadline read actions and time rather than using a decorative countdown.
Do it with the skill
Use game-world-design to define this timed commitment. Specify advancement, due checks and settlement, and current choices after early, boundary or missed delivery. Give game-build explicit loading and duplicate-submission behavior.
Read the method: Delayed consequences and world response · Deadline and duplicate-trigger boundaries