Step-by-step guide
LanternProof
Build an original paper puzzle trail with a player briefing, separate host answers and a clear record of what to reprint after each revision.
You author small printable puzzle trails and want player pages, host notes and revision records to come from the same source.
See it in use
Solve and reprint a three-card puzzle
A screenshot walkthrough with fictional practice data. Select a step to explore.
1. Start with
Solve and reprint a three-card puzzle
The Observatory Ledger has three visible clue cards.
Sample files and contents
All three cards are visible. C01 orders the tabs; C02 maps tab names to digits; C03 looks up a direction.
Practice files and guides are free. The complete app is included only where the product page says so.
2. In the app

Try it in three steps
- Order MOON, SUN and STAR from C01.
- Map them to 729 and look up EAST on C03.
- Save a baseline, edit C02 wording and review the changed-page reprint.
Show every click and setting
- Read MOON before SUN and STAR after SUN: MOON, SUN, STAR.
- Map MOON = 7, SUN = 2, STAR = 9 to 729.
- Find 729 in C03’s index and read EAST.
- Save a baseline; clarify C02’s wording and inspect changed-page and downstream review results.
3. The result
Inspect the result
The solution is 729 → EAST. The player PDF has a briefing and three cards; a C02 edit needs one player-page reprint.

What to check in the practice result
MOON SUN STAR →729→EAST. The A4 and Letter player PDFs each have four pages: the briefing and three cards. A C02 player-text edit produces a one-page player reprint, one host reference and a review cue for unchanged C03. Playtest the revised trail before sharing it.
This fictional example is shown in the working interface and in the supplied result. Review the guide before using your own files.
See the workflow at a glance
Choose a short explanation, then follow the worked example below. Check the requirements and compatibility before using your own files.
Reprint the changed card. Review what follows it.
One wording edit can matter beyond its own page. LanternProof's original Observatory Ledger follows MOON, SUN, STAR to 729 and then EAST. Save a baseline, clarify card C02 and inspect which player and host pages need reprinting, plus the unchanged downstream card flagged for review. Dependency checks identify structural consequences; they do not solve the puzzle or verify physical playability. Review and playtest your revised game before sharing it. The desktop Chrome-on-Linux workflow supports A4 or US Letter output, and the guide walks through the three-card example.
View the illustrated card

Before you start
- Desktop Google Chrome. Chrome 152 on Linux with offline file:// use checked; other browsers and operating systems remain unverified.
- Extract the entire purchased ZIP and open index.html. The original Observatory Ledger opens immediately. No server, account or npm installation is needed.
- 1–24 cards; A4 or US Letter; up to120 generated PDF pages. Project JSON import:20MiB. Save project JSON before closing; there is no autosave.
Your first result
Open the original example
Extract the entire buyer ZIP and open index.html in desktop Chrome. The three-card Observatory Ledger is loaded. Use Load example to restore it later.
Read both editions
Choose Preview. Read the player start page, then use Previous/Next card to walk through C01, C02 and C03. Compare each clue with its private answer, hints and reset notes. Keep player PDFs separate from the host handbook when sharing the game.
Write your own cards
Return to Write. Enter a title, edition and briefing. Give each card a stable ID, player clue and private host notes. Use required earlier cards to describe information dependencies; they do not represent physical locks or hiding places.
Review and export
Open Review & export. Correct duplicate or missing IDs, self-dependencies and cycles. Choose Download print pack ZIP. The example produces four player pages (briefing plus three clues), three private host pages, a dependency map and a playtest sheet. Inspect every PDF before printing.
Prepare a controlled revision
Choose Set current edition as baseline, then save the project. Clarify only C02’s player wording and return to Review. C02 requires one player and one host reprint; unchanged downstream C03 is flagged for review. A briefing edit reprints the updated start page with the player edition.
Keep the editable source
Choose Save project and retain the downloaded JSON. Open it with Open JSON next time. Keep the baseline version as a separate saved file when you need a long-term revision record.
A worked example
The Observatory Ledger
Input: All three cards are visible. C01 orders the tabs; C02 maps tab names to digits; C03 looks up a direction.
- Read MOON before SUN and STAR after SUN: MOON, SUN, STAR.
- Map MOON = 7, SUN = 2, STAR = 9 to 729.
- Find 729 in C03’s index and read EAST.
- Save a baseline; clarify C02’s wording and inspect changed-page and downstream review results.
Expected result: MOON SUN STAR →729→EAST. The A4 and Letter player PDFs each have four pages: the briefing and three cards. A C02 player-text edit produces a one-page player reprint, one host reference and a review cue for unchanged C03. Playtest the revised trail before sharing it.
More application screens
From the first clue to a revised print pack
Actual screenshots of version1.0.1 and a rendered page from its exported PDF. The free pack contains the same worked example, with player and host files kept separate.
1. Write one source for player and host

2. Read the briefing and each card

3. Reprint the changed card

4. See the actual print output

5. Keep card selection close to the editor

Troubleshooting
Export is disabled
Read Review and correct the named duplicate, missing, self or cyclic dependency. You can keep editing and save the project while fixing structural problems.
A PDF page cannot be generated
Read the named card and field in the error. Shorten overflowing text or remove its image. Unsupported font characters must be replaced before export.
An import is rejected
Use the app’s own schema 1 project JSON within 20 MiB. A rejected import should leave your current project intact.
A downstream card is flagged but unchanged
Review whether the revised earlier clue still supplies the same information. The flag does not mean the later card was automatically edited.
Work is missing after closing
Reopen the latest project JSON you downloaded. Browser editing does not create an automatic backup.
Compatibility & limits
- 1–24 cards; A4 or US Letter; up to 120 generated PDF pages. Project JSON import: 20 MiB.
- Each card accepts one PNG or JPEG up to 1 MiB, 4096 pixels per side and 12 megapixels. Text must fit the named fields and the bundled DejaVu Sans font.
- Dependency checks identify structural problems. They do not solve your puzzles or verify physical playability. Review and playtest your own game before sharing it.
- Tested in desktop Chrome on Linux. Other browsers and operating systems are unverified. Save project JSON before closing; there is no cloud sync or automatic save.
Need a hand?
Tell us the product, host application and version, what you tried, and the exact error. Contact support with a fictional example; keep private customer files and passwords out of your message.