Teach the editor

The game keeps its list of items and effects, and its quests and map, in files the editor can't read. So the editor learns how the game saves an item, an effect, an enchantment or a quest from real saves: yours.

What your saves can teach it

• Effects and their tiers. A tier nobody has sent yet becomes one the editor can write for everyone.
• Enchantments. Enchant an item at the Enchantsmith, and the editor can copy that enchantment from your save.
• What the game calls things. Anything the editor knows only by the name a save uses gets a Name it… button on its card. Nothing does at the moment: the last five enchantment books got their names this way.
• The world. Quests and their steps, doors and where they are, minecart stations and regions. The editor's list of the world starts early in the story, so a hero further along has the rest. If you've used the play recorder, your list also says where chests were opened and where minecart stations turned up.

How to send it

1. Open the editor and choose Menu → Share and suggest → Share item IDs…
2. It lists what your saves hold that the editor doesn't know yet: item and effect IDs, their numbers, any item names you typed in, and under those, what your saves show of the world. Every line is there to read before anything is sent, all of it in the game's own names and numbers. Nothing about your account or your hero's ID is in it.
3. Untick the box under the list if you'd rather leave the world out.
4. Send the list as an issue.

Send a play recording

A list shows what your saves hold now. A recording shows what the game does to a save while you play, which is how the editor learns to do the same: what enchanting an item writes, what a level-up changes, what a Soul Storm's reward chest hands you.

1. Choose Menu → World → Play recorder… and press Start recording.
2. Play. Do the thing you'd like the editor to learn, and type a note when you do it ("opened the storm's chest").
3. Press Stop recording, then Share this recording…
4. It shows what the recording found, as it can be sent: new item IDs, what happened to your items, how your stats moved, quest steps and places, and your notes. Take out any line you'd rather not send.
5. Press Open a GitHub issue…, or copy it.

It leaves out the date, the time of day and where your saves are. The recording itself holds your whole hero save, so don't post its folder or anything else from it.

What makes a list most useful

• Items the game gave you, not ones made with the editor. The editor leaves out anything it would have written the same way itself, because that proves nothing.
• Enchantments at each tier. Enchant something at tier I, II and III and the editor learns all three.
• Names. When the list asks what the game calls something, the name on the item's card in the game is the answer. To name an enchantment, put it on an item and read what the game calls it there.
• A hero far into the story. Its quests and doors are the ones the editor is missing.
• A rock moved or a key gate opened with the play recorder on, on a hero whose map isn't all discovered. The recording shows where it was, which puts it on everyone's World map, and for a gate which lock went with it.
• A quest finished with the play recorder on. The recording shows which quests the game opened after it, which is what Finish it in Story progress needs to do the same.

People who send lists are credited in the README.