At a glance
The saved RarityForcerRare pattern keeps an existing rare, applies Alchemy to a normal item, and uses Scour then Alchemy on a magic item. Its Alchemy routes finish after the action, so checking the game item is part of the result check.
Build a personal version with an entry guard, then test one starting rarity at a time.
Before you start
Complete setup, configure Scour and Alchemy, and enable Orb stock guard. Prepare ordinary, identified, uncorrupted equipment you are willing to modify. The magic route erases its existing explicit modifiers.
Use Current item for these tests. The internal Learn helper is hidden; the steps below recreate its branches using +.
1. Define the accepted starting items
Create Prepare rare item 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.
Add Check Item > Rarity with Normal, Magic and Rare selected.
Connect Start to this check. Connect its unmet output to Finish. This stops an input outside those three rarities before the orb routes. Also inspect the item's actual eligibility before running.
Set the rarity buttons one at a time: Normal selected, Magic selected, Rare selected and Unique deselected. Click a button only when its current state differs from that setting.
2. Keep an existing rare
Add a second Rarity check with only Rare selected. Connect the entry check's met output to it.
Connect Rare's met output to Finish. An already rare item now takes the shortest path and keeps its current explicit modifiers.
3. Give normal items a direct route
Add a Rarity check with only Normal selected. Connect Rare's unmet output to it.
Add Orb > Alchemy. Connect Normal's met output to Alchemy, then Alchemy to Finish. This branch uses one Alchemy application when the starting item is normal.
4. Prepare a magic item before Alchemy
Add Orb > Scour. Connect Normal's unmet output to Scour, and Scour to the same Alchemy node.
The entry guard makes this the magic-item branch. The complete route is Magic input → Scour → Alchemy → Finish. The saved pattern has no loop that retries a failed conversion.
5. Run three small checks
Save, then test a disposable normal item. It should receive Alchemy and become rare. Test a disposable magic item separately: it should receive Scour and then Alchemy.
Finally, start on an already rare item. It should finish without reaching either orb node. Compare Logs with each actual tooltip; reaching Finish alone does not prove that an orb changed the item successfully.
Check the result
Normal and magic test inputs become rare through their respective routes. An already rare input remains unchanged. There should be no repeated crafting cycle in this tree.
If it does not work
- Alchemy is attempted on a magic item: reconnect Normal's unmet output through Scour.
- A rare item is changed: inspect the Rare check's selected buttons and met connection.
- Finish is reached but rarity is wrong: inspect the item, stock and orb coordinates before another run.