How to Write a Text Game Across Timelines: When the Past Changes, Who Still Remembers?
An old photo now includes her father, yet he says he was home that Sunday all along. A fictional cinema story separates rewritten events, objects, and memories.

Introduction
In the photo, her father was finally sitting at the dining table. The player breathed a sigh of relief and turned to ask him about that Sunday, but her father looked puzzled. “Wasn't I there all along?”
If that line has a basis in the story's rules, it can suddenly make a rewrite of history feel concrete. Without one, it may simply be a more sentimental reaction the author chose on the spot. When writing a text game across timelines, deciding who will forget is often more useful than planning three twists first.
This article uses a fictional cinema as a teaching example. The characters, specific events in the periods depicted, and method of rewriting history are all original and do not correspond to a real case.
Choose One Set of Time Rules and Finish This Short Story
This example has only two fixed points in time: a Saturday in 1998 and the same day in 2026. An adult daughter finds a staff scheduling ledger in an old cinema. Through it, she can send a one-sentence request to her father in the past, with a maximum of three rewrites of history. She cannot choose a third period or relay messages to create a new entry point into time.
A rewrite takes effect in the present only after her father reads the request and completes the relevant action in the past. The current timeline is replaced, leaving no parallel world that anyone can freely enter; the author should still keep notes on the old version to check the changes. After seeing the result, the player can make another request, each time continuing from the past as changed by the previous rewrite.
Other stories can certainly allow parallel worlds to coexist. But within the same short story, avoid saying that the old world has disappeared and then letting anyone return to it at will to retrieve things, unless that exception has been established in advance.
Use One Small Incident to Build a Traceable Chain of Changes
On the original Saturday, the cinema needed a replacement light fixture. The father put off collecting it until Sunday, missed the family lunch, and left an empty seat in the photo.
The daughter's first request is: “Borrow the light fixture from the cinema next door today, so you can keep tomorrow free for lunch.” Her father in the past agrees and borrows it on Saturday. As a result, he does not need to go out to collect it on Sunday. He now appears in the photo on the wall in 2026, and the scheduling ledger also contains a new entry recording Saturday's loan.
That is enough for now: the request changes an action, the action changes his absence, and his absence changes the photo. The borrowing arrangements serve only the plot; there is no need to explain how to operate the equipment. Do not casually make this loan resolve years of family tensions as well. At most, a photo showing the father proves that he attended. It cannot prove that every argument never happened.
When Events Change, Track What Each Person Knows Separately
In this example, only the sender of a request that crosses time retains memories of the old timeline. The father and the other family members remember only their lives after the rewrite. His statement, “I was home that day,” is therefore a natural result of his new memories, rather than a deliberate denial of his daughter's experience.
Nor does the father automatically know who was missing from the original photo simply because his daughter remembers the old events. She can explain it to him, but “hearing his daughter say this” and “personally remembering that version” must be recorded separately.
You can write down four things, one by one: what originally happened, what happens now, what the player remembers, and what the father remembers. If there are siblings, add records for them too. Do not skip over the differences with a line such as “the whole family regained their memories.”
This differs from writing two parallel strands in which events happen simultaneously. In that approach, events have not been rewritten; information simply arrives late. Here, the events themselves have changed. Both kinds of story require checking the timeline, but the contradictions to look for are different.
Set Equally Clear Limits for Objects and the Number of Rewrites
The ordinary writing in the scheduling ledger and the photo on the wall both change with the new timeline. An old ticket stub the daughter keeps between the ledger's pages is the only protected object: the notes she writes on its back about the old version do not change. This exception is demonstrated before the first rewrite. The author cannot later casually add a box with the same protection.
One chance is used only when a request is sent, and it is not refunded if the father refuses or the result is unsatisfactory. A maximum of three requests can be sent. Reading and comparing records uses no chances, and there is no automatic restart. Neither the remaining chances nor the ticket stub is affected by a rewrite of history, so after the first request is sent, only two chances remain. An updated photo will not restore the count to three.
Before confirmation, show the exact words that will be sent and the number of chances remaining. If the player later wants to undo the request, they must use one remaining chance to send a new request and proceed from the past as it has already changed. They cannot pretend the first request never happened while keeping its benefits. These are writing rules for this article that authors need to build into their own works, not a time-rewind feature automatically provided by the website.
On the Final Read, Take Each Character's Perspective Separately
First, read only the version the daughter sees: she remembers the empty seat, sees the family photo as it is now, and can still use the ticket stub to check the changes. Then read only the version the father sees: he borrowed the light fixture and attended lunch; he never experienced being absent. Only when both can say things grounded in their own experiences does the conflict avoid depending on someone pretending not to understand.
Finally, check three things: whether changes to objects come from actions that have already happened, whether characters suddenly know details of the old version, and whether scene changes have reset the number of rewrites. When you need to connect a character's response to specific facts, see how to write quest completion conditions: establish that the event happened before writing the emotions it causes.
A story spanning time can leave room for regret. The daughter has gained a more complete photo, but lost the possibility of talking with her father about that absence as a shared experience. Readers can trace how that cost arose, and it leaves a question worth hesitating over before the next request.






