At a glance
The Learn sample Boots Magic Roll combines rarity conversion, an empty-prefix check, Augmentation and Alteration. This walkthrough builds a personal version for boots that are already magic, with one movement speed requirement and an explicit spending limit.
Follow the click-by-click slideshow to build this tree in the app. Each slide highlights the control or connection ports for that action. The images show configuration previews; select an image to open it at full size.
Before you start
Complete setup and item-copy checks. Prepare identified, uncorrupted magic boots you are willing to reroll. Configure Alteration and Augmentation stash locations, enable Orb stock guard, and know your Stop shortcut.
1. Create your practice version
On the Hub, press +, name the tree Boots speed practice, and open Edit Tree.
Click the sliders button beside Bulk in the editor toolbar, labeled Configure bulk / grid settings. Choose Current item, then click Save. The dialog closes and the tree uses one item.
Keep Current item selected.
The source example is Learn/Magic Crafting/Boots Magic Roll.json, titled Learn: Boots Magic Roll in its saved Hub metadata. Look under Learn if it is available on your installation. These instructions build an adapted personal tree; opening the sample alone does not apply the changes below.
2. Use one movement speed requirement
Add Check Item > Mods. Choose the appropriate boots item type and add #% increased Movement Speed. Set Min Value to 10 and require that one configured line. Call this the speed check.
The saved sample has two checks: its first accepts the movement speed line at minimum 0, while its inner loop requires 10. An item can therefore exit through the first check before reaching the stricter one. This practice version uses the same 10 requirement at every visit.
3. Add the empty-prefix branch
Add Check Item > Empty Mods. Choose Empty prefix quantity and Minimum open slots: 1. Add an Augmentation orb node and an Alteration orb node.
Connect Empty Mods met → Augmentation and unmet → Alteration. Connect both orb outputs back to the speed check. This follows the sample's prefix decision: an open prefix gets an Augmentation attempt; otherwise the item is rerolled.
4. Bound the spending route
Add a Counter, create a Number parameter called Orb actions, and set its fallback default to 5, following Counter setup.
Select Orb actions in the Counter's Run Parameters counter field.
Connect Start → speed check. Connect speed check met → Finish, and unmet → Counter. Connect Counter met → Empty Mods, and unmet → Finish. Every currency action now requires one counter pass. There is no direct route from the speed check to an orb.
In Counter, open Run Parameters counter, click Create new, enter Orb actions in Label, then click Add. Counter creates a Number parameter and selects it automatically. Open Params, expand Details for Orb actions, check Type: Number, keep Kind as Run setting (with fallback default), enter 5 in Fallback default, then click Save.
5. Confirm the input and run
Use Back to Hub, save Orb actions as 5, and wait for Saved. Confirm the boots are magic, keep the currency stash and inventory ready, then start on that item.
This version omits the sample's Scour and Transmutation branches. Prepare magic boots first; it has no rarity guard.
6. Read the ending
Open Logs and inspect the final boots. The tree ends when the speed check passes or the next Counter visit finds no allowance. The allowance covers at most five combined Alteration and Augmentation actions; it does not guarantee a matching roll.
Check the result
Compare movement speed with the saved minimum. Check whether the target branch or exhausted Counter ended the run.
If it does not work
- A low roll passes in the original sample: inspect its separate opening check at minimum 0.
- Empty-prefix results look wrong: verify advanced copied modifier labels using Empty Mods.
- Currency keeps spending: stop and check that every retry passes through Counter.



