LANTERNPROOF / VERSION 1.0.1

From clue to print

An illustrated guide to authoring player cards, private host notes and a controlled revision.

1. Open your studio

Extract the buyer ZIP to a folder. Open index.html in desktop Google Chrome on Linux. This release was checked in Chrome 152. The tested workflow uses file:// with the browser offline; no server, account or installation is needed. The fictional Observatory Ledger sample opens automatically. Keep the folder together so the guide and app remain available.

LanternProof editor with the Observatory Ledger sample and its three cards
The sample has three visible cards and a clear Write, Preview, Review & export path.

2. Get the first result

  1. Choose Preview. Read the player start page, then use Previous/Next card to read C01, C02 and C03 against the private host answer and hints.
  2. Choose Review & export. The dependency chain is C01 → C02 → C03; C03 is the final goal.
  3. Choose Download print pack ZIP. Unzip it. Open player-cards.pdf separately from host-handbook.pdf. The sample player PDF has four pages: the briefing, C01, C02 and C03. The host handbook has three pages. The sample answers are MOON SUN STAR, 729 and EAST. The host handbook also has private hints; do not hand it to players.

The ZIP also contains dependency-map.pdf, playtest-sheet.pdf, project.json and manifest.json. When the briefing has text, it is the first page of the player PDF. Each player clue and matching host reference gets its own labelled page. The playtest sheet continues onto additional pages when needed. Print at actual size on the selected A4 or Letter paper.

Side by side player and host preview for the Ledger key card
The right side is marked HOST — SPOILERS; answers, hints and placement notes stay there.

Inspect the supplied print files

The A4 player PDF begins with the briefing, followed by three clue cards. Keep the private host handbook with the game host. Also supplied: dependency map, playtest sheet, Letter player PDF and editable original project.

Actual first page of the player PDF, containing the Observatory Ledger briefing
The actual exported start page. Check every page and print one test copy at actual size before preparing a full game.

The C02 reprint example and revision record show a one-card change. These are fictional worked examples. Structural checks do not determine whether a puzzle is solvable or enjoyable; playtest your own trail.

3. Make your own game

Choose New game, or Open JSON to restore a previously saved project. The app asks before replacing unsaved work. Enter a game title, edition ID, A4 or Letter size, briefing and final goal. Add up to 24 cards. Give each a stable ID, player clue, answer, optional display variants, up to three hints, placement/reset notes, dependency IDs and playtest observations. PNG/JPEG images can be attached to player cards. Dependencies describe information needed; they do not hide cards or operate physical locks.

Select a card in the card list, then use Earlier, Later or Delete card in its editor. Review reports duplicate, missing, self or cyclic dependencies as export blockers. A card outside the final-goal chain is a manual review cue. Edit and save remain available while you fix structural errors.

Dependency review and export panel for the sample
Structural review shows the three-card chain before export.
Cycle blocker in dependency review with export disabled
A cycle gives an actionable blocker and disables export until repaired.

4. Save, revise and reprint

Choose Save project to download JSON. There is no autosave after the tab closes. When an edition is ready, choose Set current edition as baseline, then save the project again. The baseline travels inside the JSON. Edit a clue and revisit Review & export. The screen names changed player pages, matching host reference pages and unchanged downstream cards to review. A briefing change marks the player edition for reprint. Export includes full updated editions plus revision/player-reprints.pdf, revision/host-reference-pages.pdf and revision/delta.json when applicable. If no pages changed, it reports none.

In the worked example, changing C02 to “Read your ordered tab names from C01 left to right…” changes player C02 and its host reference. C03 is unchanged but flagged for human downstream review. The solution remains 729.

C02 revision shows C02 reprints and unchanged downstream C03 review
The revision list separates reprints from cards whose wording did not change.

Limits and troubleshooting

Privacy: authoring and export run in the local browser tab. You control downloads. Keep the host PDF private. To uninstall, close the tab and delete the extracted folder and any files you downloaded.

Working on a narrow screen

The compact card strip keeps card selection above the editor. Previous/Next in Preview moves through the trail. The image below is a 390px desktop browser resize check; physical phone and tablet operation remain unverified.

LanternProof at a 390 pixel desktop viewport with compact card selection
A narrow view of the same original example.