When Time Advances in a Text Adventure: Observation, Action, and Waiting Must Be Separated

You can start with a checkable set of time rules: observation does not advance the story clock; actions such as movement and negotiation advance by prewritten durations; active waiting advances to the next event or waiting limit. This is the design approach used in this article's example. If a work requires observation to consume time too, it should be disclosed in advance and applied consistently. Below, the fictional "Last Ferry at the Crossing" breaks the rules into three types of clock tables; place names, characters, and numbers are all teaching settings.

Player input falls roughly into three categories, each corresponding to different time handling.

Observation is obtaining existing information: reading a notice, sizing up the ferryman, recalling what was heard yesterday. Observation does not consume world time, because the character is only directing attention to something that already exists. The cost is not in the clock, but in the information itself possibly becoming outdated—if something has already happened, observation can only see the result.

Action is an operation that changes the situation: handing over a ticket, walking onto the pier, passing a bundle to the ferryman. Actions have durations; however long you walk or work, world time advances by that much.

Waiting is actively letting time pass, but it must have a trigger condition or limit: wait until the boat docks, wait until dusk, wait at most until a certain moment. Waiting without a limit makes players lose control of pacing.

Once these three are separated, neither "one glance consumes a day" nor "repeated observation farms time" will occur.

Fictional setting: the player plays a traveler who needs to cross the river and carries an old ferry ticket. The last ferry leaves at dusk. The crossing has a notice board, ferryman Old Zhou, and a pier. Before dusk, two things will happen: the cargo boat first docks to unload, and Old Zhou will go check tickets. The player does not know the exact hour and can only read clues from the environment.

First write clear clues that support judgment, then let the character make inferences. The notice board says, "Last ferry at dusk, no waiting after the time"; Old Zhou says, "Once the cargo boat arrives, I'll be busy for a while"; the dock clock shows twenty minutes until the last ferry, and Old Zhou says ticket checking starts in five minutes. The player can therefore compare action durations with the remaining margin. Water level only expresses the environment; it does not treat one observation of yesterday's water level as reliable proof of today's time.

Fill the rules into a table and check them one by one when writing the script.

"Walk the pier" can be set as a short duration, for example a short walk from the shore to the boat. When this walk is completed, world time advances by the same amount. If the player stops on the pier to observe the water surface, time no longer advances, because stopping is not an action. In this way, "one glance consumes a day" will not happen.

The cargo boat docking and Old Zhou checking tickets can happen at the same time. The way to write it is to give each event a trigger point, rather than arranging a separate timeline for each.

In this example, the cargo boat docking is written as five minutes after the current time point, and Old Zhou then begins checking tickets. The player needs two minutes to walk to the middle of the pier, so when arriving, the cargo boat has not yet docked; choosing to wait for the cargo boat advances time to the fifth minute. This is the same story clock; you cannot separately set "as long as you walk to the middle, the cargo boat arrives." When two events occur at the same moment, first clarify the processing order, then explain in the feedback the event that was not shown first.

The benefit of writing it this way is: players will not lose events because of "simultaneity," and they will not feel that time has been stolen because the system sorted things for them.

Waiting is the easiest thing to write badly. It is recommended that every wait write three things: what you are waiting for, the latest you can wait until, and what happens after waiting.

"Wait for cargo boat" has a limit of five minutes after the current time point. If you write another delay branch, then at the fifth minute show "The cargo boat is delayed; fifteen minutes remain until the last ferry," providing three exits: hand over the ticket, ask Old Zhou, or give up crossing. If you continue waiting until dusk, the last ferry leaves, and the next round changes to handling being stranded; the same waiting feedback cannot be repeated infinitely.

Observation can be inserted during waiting to read the state at the current time point. Checking the dock clock can tell you the remaining time; looking at the water level can only tell you environmental changes. Do not secretly advance a few minutes inside an observation that originally takes no time, then use that new result to prove that time has passed.

Old Zhou might say, "The boat left long ago, don't wait." This sentence is the character's statement, not a world fact. In writing, mark it as "Old Zhou's statement," not narrator confirmation. It can be written as: Old Zhou says the boat left long ago. Whether the boat really left is verified by the player's later observation or action. In this way, readers will not treat the character's excuse as a new world setting.

Likewise, if Old Zhou says, "I knew your father," and the previous text has not provided any past events, this sentence cannot automatically become true background. It can be kept as his statement; the player can choose to believe it or not, but the system does not confirm it for the player.

Edge input means the player does something the rules did not anticipate: throwing the ferry ticket into the water, jumping onto the cargo boat, lying to Old Zhou. The handling principle is to first judge whether it belongs to observation, action, or waiting, then apply the corresponding clock.

Throw the ferry ticket into the water: this is an action, it has a duration, and time advances. Afterward, the "hand over ticket" path closes, and the player must find another way. Jump onto the cargo boat: if the cargo boat has docked, this is an action; if the cargo boat has not docked, this is an impossible action, and you can respond "you cannot reach it," without advancing time. Lie to Old Zhou: this is an action, time advances, and Old Zhou's reaction is written according to his goals, with no guarantee that he believes it.

Edge input does not need new rules; it only needs to return to the three types of clocks.

After writing a section, check it with the following items:

1. Does every observation option avoid advancing time?
2. Does every action have a written duration, and does the duration match the event trigger point?
3. Does every wait have a clear limit and an event after the point is reached?
4. Do simultaneous events each have trigger points, and is the one the player participates in settled first?
5. Are excuses spoken by characters marked as "his statement," not mixed into world facts?
6. Can edge input be classified into one of the three types of clocks?

If all six items can be answered, time advancement will not be dragged away by a single observation, nor will it be stuck by repeated waiting.

Take a scene you are writing and do only one thing: list all player-selectable inputs in this scene, mark each one as "observation / action / waiting," then fill in durations for actions and limits for waiting. After marking them, write the narrative, and the time rules will not conflict midway through writing.