UrdTrace · Local SugarCube playtest tool 1.0.0 · Chrome on Linux
Turn SugarCube playtest notes into a revision worklist
See the passages testers visited, the endings they reached and the notes they left along the way.
Use UrdTrace after a small playtest round when you need to connect a tester's comment to the passage and route they actually recorded, then decide what to revise and what to test next.
$7.99 USD · one-time purchase
Continue to checkoutStep-by-step guide
No subscription. Final total and tax appear at checkout.
See a complete playtest round before buying
Inspect the original story, three fictional tester transcripts and finished report before buying. The free pack includes the complete illustrated manual; the author app and recorder are in the paid ZIP.
- For: Twine authors using SugarCube 2.37.3
- First result: Open the built-in example and review its six passage-linked notes
- You get: One local author app, source, manual and original examples
- Runs in: Desktop Chrome on Linux · no account or server required
What it helps you do
For authors testing published SugarCube 2.37.3 stories. Make a separate recorder copy, collect the transcript files testers choose to return, and review their routes and passage-linked notes in one local workspace.
What is in your download
- Local author app and source
- Illustrated manual with 10 actual screenshots
- Original Ferry story, scripted tester transcripts and readable example outputs
- Tester-copy recorder workflow with explicit consent
- Printable HTML report, CSV worklists and editable saved-round export
A practical example
Find the untested ending in The Ferry at Low Water
Start with
The original 21-passage SugarCube story and three fictional tester files. StoryInit is code and is excluded from the 20-passage coverage count.
Get this result
Four scripted runs, 30 passage displays and six notes; 17 of 20 counted passages visited, three of four endings reached and 21 of 27 parsed static links matched by recorded transitions. Sinking, TideTable and EndingTide were not reached.
Free Ferry example, finished report and illustrated manual
Examples use fictional or synthetic data. Follow this example step by step.
Follow a complete playtest round
Actual screens from the downloadable app, using an original story and fictional scripted tester files.
See the round on the story map
Actual app view of the original Ferry example. Passage visits and optional recorded routes sit beside the passage inspector. View full size Read notes with their route context
Six notes from fictional, scripted testers are attached to passages and the preceding route. Classify the work without changing the tester's original text. View full size Make a recorder copy for this round
Download a separate tester HTML bound to the exact original story and named round. View full size Let testers write at the relevant passage
The recorder attaches a note to the current passage and run step. Testers choose when to record and download their transcript. View full size Choose what to test next
Sinking, TideTable and EndingTide were not reached in the four scripted runs. Static-link suggestions need to be checked against the story's conditions. View full size
How it works
Prepare the round
Open the exact published story and download a separate tester copy.
Collect returned transcripts
Testers consent, play, add notes and send you the files they download.
Choose the next revision
Review routes, notes and unvisited passages; export a worklist and save the round.
Before you buy
- Desktop Google Chrome on Linux is the tested environment.
- Extract the ZIP and open UrdTrace.html in desktop Chrome on Linux. Load the built-in Ferry example for a complete first round, then open your own published SugarCube 2.37.3 HTML.
- Only published SugarCube 2.37.3 HTML. Harlowe, ink, Yarn, Twee source and Twine archive JSON are not supported inputs.
Compatibility & limits
Only published SugarCube 2.37.3 HTML. Harlowe, ink, Yarn, Twee source and Twine archive JSON are not supported inputs. Verified in desktop Chrome 152 on Linux. Other browsers, operating systems and mobile platforms are unverified. Up to 500 total story passages and 10 MiB story HTML. A round accepts 10 transcripts, at most 2 MiB each and 8 MiB combined. Each transcript holds up to 2,000 passage displays and 200 notes, with 2,000 JavaScript string units per note. Saved-round import is limited to 24 MiB. Transcripts must match the exact original HTML bytes and round. Keep the original file; start a new round after republishing. Coverage comes from recorded passage displays and parsed static links. Route hints do not solve conditions, analyze every dynamic link or prove a path is playable. Testers must choose to record, download and return their files. There is no automatic collection, variable capture or cloud collaboration. The app and recorder do not upload your data. Your own story may still run network code or require external assets. Keep those assets with the tester copy. Printable reports were checked using Chrome's PDF output; physical printers and other PDF engines are unverified.
Get UrdTrace
Perpetual use of the purchased version on your devices for personal or internal commercial work. Keep reasonable backups and modify your own copy; do not redistribute or resell original proprietary code. Third-party licenses and any existing preview permissions retain their rights.
Before payment, save the private recovery code shown by checkout. After Paddle confirms payment, use it to download your ZIP or return for it later. No subscription, future update or email delivery is promised. See the illustrated steps.
$7.99 USD · once
Buy download