At a glance
Quiver Roll prepares magic rarity, checks a list of modifier names, then chooses Augmentation or Alteration from an empty-prefix check. Its saved target rows need attention: all eight historical rows have Required: 0, while the check requires a total of 1. Set the contributions explicitly before running a copy.
Before you start
Complete setup, configure Alteration and Augmentation, and enable Orb stock guard. Prepare a disposable identified, uncorrupted magic quiver. Verify advanced copied item information for name and prefix checks.
1. Create a personal practice tree
Press + on the Hub, name it Quiver names 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.
Select Current item.
The source is Learn/High Value/Quiver Roll.json, titled Learn: Quiver Roll in saved Hub metadata. These steps correct its target contributions and add a Counter. The sample stores disabled bulk settings; confirm your own Current item mode.
2. Prepare the entry path
Add Open Panel to ensure the stash is open on the currency tab. Add Embed Tree and select your own saved magic-rarity child, following Force magic rarity.
Connect Start → panel step → Embed Tree. The sample references the internal Learn RarityForcerMagic helper, which is hidden from normal pickers. Creating a personal child gives this practice tree a selectable dependency.
3. Enter the name list
Add Check Item > Mods, select the quiver item type, and use modifier-name matching. The sample lists Flaring, Cremating, Entombing, Electrocuting, Impaling, of Grandmastery, of Splintering and Fecund.
Select each available name and click Add mod name before searching for the next. Fecund is absent from the current catalog, so skip it in this practice tree. Keep only names you intend to accept and can select for your item scope. Check separately whether your base can roll them; the list makes no value claim.
4. Make matching rows contribute
In Advanced, set each retained row to Required: 1. Turn off automatic Required threshold syncing and set Required matches >= 1 and Score needed >= 0. Mod-name rows expose Required and Only If. This example uses Required matching, so leave the score threshold at zero.
The saved sample's zero-weight rows cannot supply its Required total of 1. Increasing the threshold does not repair that. With the explicit values above, one matching retained name contributes 1 and can pass. Connect Embed Tree to this check and its met output to Finish.
Set Required to 1 separately on each retained row: Flaring, Cremating, Entombing, Electrocuting, Impaling, of Grandmastery and of Splintering. There is no Points field on these mod-name rows.
5. Add the bounded retry path
Add a Counter using Number parameter Orb actions, fallback 5. Connect Mods unmet → Counter, Counter unmet → Finish, and Counter met → Empty Mods set to Empty prefix quantity: 1.
Connect Empty Mods met → Augmentation and unmet → Alteration. Return both orb outputs to Mods. This permits at most five combined retry applications. The rarity child runs before Counter, so any conversion spend is outside that allowance. Start with the prepared magic quiver for this test.
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.
6. Run and inspect the reason for Finish
Save Orb actions as 5 on the Hub and wait for Saved. Confirm Current item, start on the quiver, then compare Logs with its modifier names.
Check the result
A target exit should show a name contributing Required 1. A budget exit can leave the target unmet. Neither exit confirms market value or a finished rare craft.
If it does not work
- A visible name contributes zero: reopen Advanced and inspect the row's Required value.
- Every row must match: change the final threshold to 1 and disable automatic syncing.
- Wrong retry branch: check Empty Mods and copied prefix labels.