Sep 2, 2026
Here is the first draft of the Puzzle Dependency Chart for Thimbleweed Park 2.
The game is divided into four parts, and this is part 1 (and the simplest part).
Still some missing nodes to make some puzzles more complex, but it’s a solid first draft.
Green nodes are tutorial sections, yellow nodes are flashbacks, and red nodes are TBD nodes that need to be filled out in detail.
All sensitive information has been redacted for your protection.

Comments:
Thank you!
I guess uncensored puzzle dependency chart could be used by speed runners eventually (?)
(But make sure there are no bullets in the game. Then patch the first game that everyone will replay, to insert a box of bullets that are for another game)
I love seeing this.
Thanks!
PS: The captchas on this page will soon need a dependency chart.
President DONALD J. TRUMP
Are you more the kind of storyteller who wants to tell a story with a set of points, so you have a skeleton you flesh out with puzzles, characters, and situations?
Or you are more like a sketch comedian, where you have disparate jokes / puzzles / ideas you have come up with over the years, and you chain them together, with the story being just a vehicle to deliver them?
1 - Arrow from Flashback Nodes into a late-game Red TBD Node: Enables Flashback-Forcing. For example, you retroactively rewrite history by forcing a character to put an item in a safe 20 years ago, bypassing present-day lock logic.
2 - Connect the chart directly to the Inventory System: The player gets an in-game marker that lets them redraw dependency arrows in the pause menu, thereby forcing past-state logic onto current inventory constraints. Naturally, changing one arrow invalidates six other puzzles.
3 - A Floating Node drifting in unanchored orbit around all other nodes: Disconnected from every branch, it continuously clips through active nodes. Puzzle logic is randomised exclusively during the precise seconds when it overlaps another node.
How do you properly cope when something in a heavy dependable part needs to change, do you start over or just 'tear it open ' and add / alter things?
Is it normal for the chart to keep changing even deeper in the development phase?
Thanks for opening up on the development process like in TWP1 and still trusting us as a community, even after all the strenuous happenings around RtMI. Much appreciated !
Can't wait to read more.
(Disclaimer: Have not created any Puzzle Dependency Graphs/Charts - but used it for DFDs etc.)
Add comment: