At a glance
Elemental Weapon Roll uses the same rarity-helper and Alteration/Augmentation structure as the physical sample. Its saved target is a pseudomod called Weapon Fracture. Inspect that group's contents before treating it as an elemental-only rule.
Before you start
Complete setup, configure Alteration and Augmentation, and enable Orb stock guard. Use an identified, uncorrupted magic one handed sword you are willing to reroll. Confirm item-copy reads include the advanced modifier names.
1. Create the practice parent
Press + on the Hub, name the tree Elemental weapon 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 is Learn/High Value/Elemental Weapon Roll.json, titled Learn: Elemental Weapon Roll in saved Hub metadata. These steps replace its mixed target and add a budget to its unlimited retry route.
2. Inspect the original group
Add Check Item > Mods, choose One Handed Sword, then choose Pseudomods. Select Weapon Fracture, click Add pseudomod, then Done. Use the eye beside its reference row to inspect the group if it is present. The saved group contains Carbonising, Crystalising, Vapourising, Flaring, Merciless, Dictator's, Electrocuting, Entombing, Cremating, Emperor's and Tyrannical.
Each member contributes Required 1; a threshold of 1 accepts any member. Several are physical targets. The title does not filter the group, and the flow contains no fracturing action. Click Close to return to Mods.
3. Save a narrower personal group
Using pseudomod setup, create Elemental practice names. For this worked example, select One Handed Sword as the item type and add the modifier-name rows Cremating, Entombing and Electrocuting from the catalog. After selecting each name, click Add mod name before editing its row or searching for the next.
Click Advanced, then set each row to Required: 1. Mod-name rows expose Required and Only If, with no Points field. Confirm that the names exist for your chosen item scope before saving. These are example matching rules; check your base and desired outcome separately before spending. Click Save Pseudomod, then use the manager's Close button to return to Mods.
4. Build the entry and target check
Add Open Panel to ensure the currency stash is open. Add Embed Tree, selecting your own magic-rarity child from Force magic rarity. The sample's internal Learn helper is hidden from normal pickers.
Connect Start → panel step → Embed Tree → Mods check. Select Mods check on the canvas. On the Weapon Fracture reference row, click Remove. Click Add mods, choose Pseudomods, select Elemental practice names, click Add pseudomod, then Done. The new group should be the check's only reference. In Advanced, disable automatic Required syncing, set reference Required to 1, Required matches >= 1, and Score needed >= 0. Connect met → Finish.
On the Elemental practice names reference row, enter Required 1. Pseudomod reference rows expose Required and Only If. Leave Score needed >= at 0 for this name-matching example.
5. Bound and connect retries
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, unmet → Alteration, and both orbs back to Mods. The allowance covers five combined retry actions. Rarity conversion in the child occurs before the allowance; start with a magic item so that child can return without spending.
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. Save and verify the ending
Return to the Hub, save Orb actions as 5, and wait for Saved. Start on the prepared item, then compare Logs with its modifier names.
Check the result
A passing target check should identify a member of your new three-name group. Counter exhaustion can finish with no matching member. The example sets a matching rule and spending limit; it does not establish item value.
If it does not work
- Physical names pass: inspect whether the check still references Weapon Fracture.
- Group is unavailable: check the item type and archive filters.
- Helper is missing: select your personal rarity child in Embed Tree.