Markland Published 2026-10-29

Separate Player Knowledge from Character Knowledge

By Arctale Team / Twincurrent Studio

A reader can know that a staircase is unsafe while the character approaching it has no idea. That difference can make an interactive scene tense. It becomes confusing when the writing quietly treats the reader's information as something the character has learned.

For a creator, the useful question is precise: what route carried this fact to this person? Follow that route before writing the next choice.

Start with one fact and two viewpoints

Consider this original fictional example. In a lighthouse scene, the reader briefly follows Mara, a keeper who discovers that a north stair has split. She leaves to fetch a warning rope. The next scene follows Ivo, a visitor looking for his brother. Ivo enters through the south door and has not met Mara.

The reader knows about the broken stair. Mara knows because she inspected it. Ivo knows neither the damage nor that Mara is fetching a rope. The author knows everything, including whether the stair will hold, but that knowledge does not belong in Ivo's observations automatically.

Write down the paths separately:

This is a small scene audit, not a complete character biography. Its purpose is to catch an unsupported transfer of information.

Find the leak in the choice text

Suppose Ivo's options are "Take the dangerous north stairs" and "Use the safe south stairs." Those labels reveal a conclusion he cannot yet make. That may be intentional if the game addresses the player as an outside strategist. If the scene promises decisions from Ivo's perspective, however, the labels break that promise.

Two revisions create different experiences.

One preserves the information gap: "Follow the voices above the north stairs" or "Search the rooms beside the south entrance." The reader may dread the first route, while Ivo has an understandable reason to consider it. If the hazard could end the story, decide whether you intend that risk to depend on outside knowledge; do not confuse dramatic irony with a fair warning.

The other lets Ivo discover evidence: a splintered tread lies beside the north passage, and a fresh crack is visible above it. Now "Inspect the north stairs before climbing" follows from something he can observe. The danger is no longer exclusively the reader's secret.

Neither approach is a universal rule. Choose the relationship between reader and viewpoint, then keep the choice language consistent with it.

Make every transfer visible

When Mara returns, she can tell Ivo what she found. That sentence changes his information. An unexplained warning rope might only make him suspicious; it does not tell him which stair is broken.

Distinguish a report from direct observation, too. If a stranger says the staircase is safe, Ivo has heard a claim. He has not verified it. A later response should reflect whether he trusted the speaker, inspected the stairs, or remained unsure.

For each important fact, keep one short note: who learned it, how they learned it, and what remains uncertain. You need this only where information affects the scene. Tracking every detail can obscure the few differences that matter.

Audit the next response

Read the passage once using only Ivo's information. Look for accusations without evidence, references to conversations he missed, and choices that disclose an answer through their wording. Then read it as the informed player. Is the gap creating anticipation, or merely making Ivo seem inexplicably oblivious?

This exercise is relevant to the worldbuilding and interactive fiction interests described on Arctale's official website. Arctale presents curated interactive works for readers and structured setting packs for creator submissions. The lighthouse example is independent fiction for this guide, not an Arctale episode or a test of its behavior.

Disclosure: This guide is published by the Arctale team at Twincurrent Studio. AI assisted with drafting and editing. It is brand-authored creative guidance, not an independent product review.