Names and renaming

The Count tab

Count shows how many times each name is used, in every .yarn file of your game. It is under More (⋯) at the end of the tabs.

Names are grouped by kind: characters, variables, nodes, items, areas, map places, portraits, unlocks and commands. Each file has its own column.

Find a name finds one.
Show picks one kind, like Items.
Total (click to open) adds up each kind.

Rename everywhere

Double-click a variable, node or command and type the new name. Press Enter. Esc cancels.

Tsumugi shows every change, in every file, before it makes them. It changes:

A variable: every $name, in every .yarn file, in tsumugi.json, and in your game’s code where it reads or sets the variable by name.
A node: its title: line, and every jump, hop and visit check that leads to it, in every .yarn file.
A command: every place the story calls it, and where your game’s code registers it with Chatterbox.

What characters say is never changed. A new name must be one word of letters, numbers and _, not starting with a number, and not already in use.

What can’t be renamed here

A variable with a lock is set up in your game’s code. Rename it in GameMaker.
Chatterbox’s own commands, like jump and wait.
Sprites, objects and rooms. Rename those in GameMaker.
A node your game’s code names, or your rooms or tsumugi.json name. Tsumugi says where. Change those places first.

If your game’s code writes the name somewhere Tsumugi can’t be sure about, it lists that place for you to check, and leaves it alone.

Names written differently

When most names follow one style, like BeachHut, a name in another style, like Obae_Inside, stands out. Tsumugi lists these at the top of Count, with a Rename button for each, and Rename all. You still see every change first.