Threads - Story Flowchart, Ending Gallery & Branch Jump for RPG Maker MZ

Your game has multiple endings. Your players cannot see them.

They finished on ending three, and they have no idea there were six. They do not know which choice split the road, they cannot remember which door they opened in chapter two, and replaying the whole game to find out is a bigger ask than most of them will make.

Threads gives them the chart. Every scene they reached. Every branch they took. Every branch they can see exists and have not opened yet. Every ending they have collected, and how many are still out there. And from that chart they can jump straight back to any decision they have already reached, and take the other road.

Every ending draws its own emblem

This is the part that is not a flowchart.

When a player reaches an ending, Threads generates a mark for it out of the route that got them there — the decisions they took, and the order they took them in. The motif comes from a corpus of 48 hand-authored marks in six visual families. The binding ring encodes how long the journey was and how much it branched. The small marks around the ring are one per decision, in order. The palette comes from the route as well.

Two players who reach the same ending by different roads get visibly different emblems. There are no image files in this plugin — not one PNG. Every mark on every screen is drawn at runtime.

It is fully deterministic: no Math.random() is called in any visual decision, so the same route always produces the same mark.

What it does

• The chart. Nodes laid out from your own story graph — you declare the shape, Threads computes the layout, the columns, the convergences and the states.
• The road not taken. A branch out of a place they have been is drawn dashed: they can see a road exists without being told where it goes.
• Branch jump. Store a snapshot at a decision and the chart can return them to it. Jump slots sit at 900 and up, well clear of the player's own saves.
• The ending gallery. Every ending as a slot — earned ones showing the emblem their route generated, unearned ones showing a designed locked plate rather than a hole.
• Secret nodes. Hide a label until it is reached. The player sees that something is there.
• New Game+. Reset the run's path and keep every ending and every node they have ever reached.

It does not look like RPG Maker

Neither scene creates a single window. There is no windowskin, no stock frame, no stock cursor and no engine font anywhere in either screen — the panels, the rules, the threads, the cursor and every emblem are drawn from scratch. Nothing is loaded from img/. Set your accent, ink and ground colours in the Plugin Manager and the whole thing follows them.

Three steps to install

1. Add the three files in the Plugin Manager.
2. Declare your story's nodes — id, label, act, kind, and what leads into it.
3. Call Reach Node where it happens, and Reach Ending at an ending.

That is the whole integration. Threads works out the layout, the unlock states, the convergences and the emblems itself.

Safe to add to a finished project

Threads patches by prototype extension with saved originals and never replaces a core method. It adds one non-enumerable property to $gameSystem, so it is invisible to JsonEx — including JsonEx.makeDeepCopy, which other plugins call freely.

It does not touch your map, your battle system, your message window or your default menu. Adding it to a finished game cannot change how that game plays. Save data is versioned and migrates forward, and a save made before you installed it loads normally with an empty chart.

What ships

• Three raw, readable JavaScript files — 3,100 lines, fully commented, nothing minified.
• 48 ending motifs in six families, plus 8 orbital marks, 6 binding rings and 8 chart glyphs — 70 generated marks in all.
• 6 plugin commands and 11 parameters.
• The motif corpus is data, in its own file. Add your own marks by appending one entry.
• A full Readme, and a licence that lets you ship unlimited commercial games with no royalty.

Verified with 45 headless tests and 52 checks against the real MZ runtime.

Also from Core Systems Asset Factory

• Sigil Core — every spell generates its own animated seal.
• Chronicle Core — the consequence engine under your quest log.
• Verdict Core — evidence, contradictions and the case file.
• Loop Core — time loops and what changes on the next pass.
• The whole catalogue →