At a glance
Use Share Tree on the Hub to save a craft tree as a .json file. The recipient uses Import tree, checks the flow and local setup, and then runs it when ready.
Before you start
Choose a personal tree you created, such as the bounded first tree. Check that it has a clear name, complete connections, and sensible parameter defaults.
Example filename: Three Alterations (share).json. You choose the save location and filename.
1. Finish the node edits
Open your tree with Edit and inspect each node you changed. Press Update for any pending existing-node edits. Check that Start reaches Finish and that both outputs of each check lead somewhere valid.
Use Back to Hub, then reopen Edit to confirm the flow before exporting.
2. Check what another person needs
Write a short explanation of the tree's goal, required item, materials, budget, and tier. For the example: an identified, uncorrupted magic item, three Alterations, a Roll budget of 3, and Tier 1 Craft or higher.
If your tree uses Embed Tree, identify the child tree too. Share the required personal children separately and have the recipient select the imported child in the embed node.
3. Save the share file
On the Hub, expand your tree card and click Share Tree. Choose a destination and save the .json file. Check for the Saved share file confirmation.
Send that exported file when you want someone to load the tree. The app's run snapshot, run_config.json, is a different kind of file and cannot be imported as a shared tree.
4. Import the file
Before importing, check the filename. Import uses it as the tree name, removing a trailing (share). An existing same-name tree in the main craft tree folder is replaced.
For practice, rename a copy to Three Alterations practice.json first. Click Import tree beside + on the Hub, select it, and check that the imported tree appears.
5. Review the imported tree
Open Edit and compare the nodes and connections with the intended example. Inspect Run Parameters, including the budget, before starting.
Verify local stash pins, pixels, and grids through setup. A named Area Locations preset must be configured on the receiving PC. My saved overlay entries belong to the installation; check the imported tree's actual on-screen grid placement before using bulk.
6. Test a small run
Use a disposable test item and a small budget. Keep bulk off for the first check unless the tree specifically requires it. Start only after local setup and tier requirements are satisfied.
Open Logs afterward. For the hypothetical three-Alteration tree, verify that its counter permits three passes and then exits through unmet to Finish.
Check the result
The share file should import as a tree you can inspect, configure, and run. A successful export confirms the file was saved; the receiving installation still needs its own setup and behavior check.
If it does not work
- Share is unavailable: choose your own personal tree; bundled and internal trees have sharing restrictions.
- File is rejected: select the file produced by Share Tree.
- Imported flow cannot run: fix missing child references, local setup, tier locks, or incomplete nodes shown in Edit.