Roll a magic weapon against a physical mod group

Updated
Tier 2 Economy or higher for the embedded-tree example.

Roll a magic weapon against a physical mod group

Read the written guide

Follow each step in the app. Numbered markers show the real controls. To connect nodes, drag from output marker 1 to input marker 2. Connection maps show the completed route. Steps outside the app name where to continue.

  1. At a glance

    1. Read the scope

    Read the practice target and changes from the saved sample.

    The scope and limits are clear.

    Read and complete this step before continuing.

  2. Before you start

    2. Prepare the setup and test item

    Complete [setup](setup-first-run.md), enable [Orb stock guard](orb-stock-guard.md), and configure Alteration and Augmentation. Prepare an identified, uncorrupted magic weapon you are willing to reroll. Use advanced item-copy information for affix names and prefix counts.

    Local captures, materials and input suitability are checked.

    Read and complete this step before continuing.

  3. 1. Create the parent and child

    3. Create a personal tree

    Choose + on the Hub.

    Create Tree opens.

    Open full-size screenshot
  4. 1. Create the parent and child

    4. Name the tree

    Set Name this tree (shown on the hub) to Physical weapon practice.

    Name this tree (shown on the hub) keeps the selected value.

    Open full-size screenshot
  5. 1. Create the parent and child

    5. Create the tree

    Choose Create tree.

    The personal tree appears on the Hub.

    Open full-size screenshot
  6. 1. Create the parent and child

    6. Open the editor

    Choose Edit Tree.

    The production editor opens.

    Open full-size screenshot
  7. 1. Create the parent and child

    7. Open Bulk settings

    Click the sliders button beside Bulk, labeled Configure bulk / grid settings.

    The Bulk settings dialog opens.

    Open full-size screenshot
  8. 1. Create the parent and child

    8. Use one item

    Click Current item in the Bulk settings dialog.

    Current item is selected in the dialog; click Save next.

    Open full-size screenshot
  9. 1. Create the parent and child

    9. Save one-item mode

    Click Save in the Bulk settings dialog.

    Current item is saved and the dialog closes.

    Open full-size screenshot
  10. 1. Create the parent and child

    10. Prepare the rarity child

    Complete case-force-magic and return to this parent.

    The personal child is saved and tested.

    Read and complete this step before continuing.

  11. 1. Create the parent and child

    11. Add Prepare magic item

    Choose Embed Tree.

    The node appears on the canvas and its settings open.

    Open full-size screenshot
  12. 1. Create the parent and child

    12. Select the child

    Set Craft tree to Prepare magic item.

    Craft tree keeps the selected value.

    Open full-size screenshot
  13. 2. Verify what Physical means

    13. Add Mods check

    Choose Check Item.

    The node appears on the canvas and its settings open.

    Open full-size screenshot
  14. 2. Verify what Physical means

    14. Choose Mods

    Choose Mods.

    The Check Item template is Mods.

    Open full-size screenshot
  15. 2. Verify what Physical means

    15. Choose the weapon scope

    Choose One Handed Sword.

    The modifier catalog is scoped to One Handed Sword.

    Open full-size screenshot
  16. 2. Verify what Physical means

    16. Open saved groups

    Choose Pseudomods.

    The saved group list opens.

    Open full-size screenshot
  17. 2. Verify what Physical means

    17. Choose Physical

    Choose Physical.

    The group is selected.

    Open full-size screenshot
  18. 2. Verify what Physical means

    18. Inspect the group

    Click the eye beside Physical to inspect its members.

    The saved member rows show what this target can match.

    Open full-size screenshot
  19. 2. Verify what Physical means

    19. Verify every member

    Inspect Flaring, Cruel, Tyrannical, Merciless, Conqueror's, Emperor's, Dictator's, each Required 1 and Points 0.

    The members define the target names.

    Open full-size screenshot
  20. 2. Verify what Physical means

    20. Close the group preview

    Choose Close in the group preview.

    The Mods editor is available again.

    Open full-size screenshot
  21. 3. Set an explicit group threshold

    21. Add the reference

    Choose Add pseudomod.

    Physical is added as the only reference row.

    Open full-size screenshot
  22. 3. Set an explicit group threshold

    22. Confirm the reference

    Choose Done.

    The group reference appears.

    Open full-size screenshot
  23. 3. Set an explicit group threshold

    23. Use Advanced mode

    Choose Advanced.

    Contributions and thresholds appear.

    Open full-size screenshot
  24. 3. Set an explicit group threshold

    24. Disable automatic syncing

    Set Keep Required matches equal to mod count to False.

    Keep Required matches equal to mod count keeps the selected value.

    Open full-size screenshot
  25. 3. Set an explicit group threshold

    25. Set Physical Required

    On modifier row 1, Physical, set Required to 1.

    Physical has Required 1.

    Open full-size screenshot
  26. 3. Set an explicit group threshold

    26. Read the reference-row controls

    The Physical pseudomod reference exposes Required and Only If. Keep Score needed >= at 0 for this example.

    Required controls the reference contribution; the reference has no Points field.

    Read and complete this step before continuing.

  27. 3. Set an explicit group threshold

    27. Require one match

    Set Required matches >= to 1.

    Required matches >= keeps the selected value.

    Open full-size screenshot
  28. 3. Set an explicit group threshold

    28. Use no score threshold

    Set Score needed >= to 0.

    Score needed >= keeps the selected value.

    Open full-size screenshot
  29. 4. Connect the retry decision

    29. Add Open currency stash

    Choose Open Panel.

    The node appears on the canvas and its settings open.

    Open full-size screenshot
  30. 4. Connect the retry decision

    30. Open the stash

    Choose Stash.

    Open Panel targets the stash.

    Open full-size screenshot
  31. 4. Connect the retry decision

    31. Select the currency tab

    Choose Currency.

    The configured currency tab is selected.

    Open full-size screenshot
  32. 4. Connect the retry decision

    32. Connect Start output to Open currency stash

    Drag from Start's unnamed output to an input on Open currency stash.

    The next route reaches Open currency stash. The former Start to Finish connection is replaced automatically.

    Open full-size screenshot
  33. 4. Connect the retry decision

    33. Connect Open currency stash output to Prepare magic item

    Drag from Open currency stash's unnamed output to an input on Prepare magic item.

    The next route reaches Prepare magic item.

    Open full-size screenshot
  34. 4. Connect the retry decision

    34. Connect Prepare magic item output to Mods check

    Drag from Prepare magic item's unnamed output to an input on Mods check.

    The next route reaches Mods check.

    Open full-size screenshot
  35. 4. Connect the retry decision

    35. Connect Mods check met to Finish

    Drag from Mods check's met output to an input on Finish.

    The met route reaches Finish.

    Open full-size screenshot
  36. 4. Connect the retry decision

    36. Add Empty prefix

    Choose Check Item.

    The node appears on the canvas and its settings open.

    Open full-size screenshot
  37. 4. Connect the retry decision

    37. Choose Empty Mods

    Choose Empty Mods.

    The Check Item template is Empty Mods.

    Open full-size screenshot
  38. 4. Connect the retry decision

    38. Count open prefixes

    Choose Empty prefix quantity.

    Only prefix slots count.

    Open full-size screenshot
  39. 4. Connect the retry decision

    39. Require one open prefix

    Set Minimum open slots to 1.

    Minimum open slots keeps the selected value.

    Open full-size screenshot
  40. 4. Connect the retry decision

    40. Add Augmentation

    Choose Orb.

    The node appears on the canvas and its settings open.

    Open full-size screenshot
  41. 4. Connect the retry decision

    41. Choose Augmentation

    Choose Augmentation.

    The Orb node uses Augmentation.

    Open full-size screenshot
  42. 4. Connect the retry decision

    42. Add Alteration

    Choose Orb.

    The node appears on the canvas and its settings open.

    Open full-size screenshot
  43. 4. Connect the retry decision

    43. Choose Alteration

    Choose Alteration.

    The Orb node uses Alteration.

    Open full-size screenshot
  44. 4. Connect the retry decision

    44. Connect Empty prefix met to Augmentation

    Drag from Empty prefix's met output to an input on Augmentation.

    The met route reaches Augmentation.

    Open full-size screenshot
  45. 4. Connect the retry decision

    45. Connect Empty prefix unmet to Alteration

    Drag from Empty prefix's unmet output to an input on Alteration.

    The unmet route reaches Alteration.

    Open full-size screenshot
  46. 4. Connect the retry decision

    46. Connect Augmentation output to Mods check

    Drag from Augmentation's unnamed output to an input on Mods check.

    The next route reaches Mods check.

    Open full-size screenshot
  47. 4. Connect the retry decision

    47. Connect Alteration output to Mods check

    Drag from Alteration's unnamed output to an input on Mods check.

    The next route reaches Mods check.

    Open full-size screenshot
  48. 5. Gate every retry with a budget

    48. Add Counter

    Choose Counter.

    The node appears on the canvas and its settings open.

    Open full-size screenshot
  49. 5. Gate every retry with a budget

    49. Open the Run Parameters counter picker

    Open the Run Parameters counter picker.

    The parameter dropdown opens.

    Open full-size screenshot
  50. 5. Gate every retry with a budget

    50. Click Create new

    Click Create new.

    The inline Label and Add form opens.

    Open full-size screenshot
  51. 5. Gate every retry with a budget

    51. Enter Orb actions in Label

    Enter Orb actions in Label.

    The new parameter label is filled.

    Open full-size screenshot
  52. 5. Gate every retry with a budget

    52. Click Add

    Click Add.

    The Number parameter is created and automatically selected for Counter.

    Open full-size screenshot
  53. 5. Gate every retry with a budget

    53. Click Params in the editor toolbar

    Click Params in the editor toolbar.

    The parameter schema editor opens.

    Open full-size screenshot
  54. 5. Gate every retry with a budget

    54. Expand Details for the Orb actions parameter

    Expand Details for the Orb actions parameter.

    The details for this parameter are visible.

    Open full-size screenshot
  55. 5. Gate every retry with a budget

    55. Check that Orb actions has Type Number

    Check that Orb actions has Type Number.

    The parameter is a Number; Counter fixes this type during inline creation.

    Open full-size screenshot
  56. 5. Gate every retry with a budget

    56. Set Kind to Run setting (with fallback default)

    Set Kind to Run setting (with fallback default).

    The budget remains editable before a run.

    Open full-size screenshot
  57. 5. Gate every retry with a budget

    57. Enter 5 in Fallback default

    Enter 5 in Fallback default.

    The parameter has the stated fallback value.

    Open full-size screenshot
  58. 5. Gate every retry with a budget

    58. Click Save in the parameter schema editor

    Click Save in the parameter schema editor.

    The schema is saved and the tree editor is visible.

    Open full-size screenshot
  59. 5. Gate every retry with a budget

    59. Connect Mods check unmet to Counter

    Drag from Mods check's unmet output to an input on Counter.

    The unmet route reaches Counter.

    Open full-size screenshot
  60. 5. Gate every retry with a budget

    60. Connect Counter met to Empty prefix

    Drag from Counter's met output to an input on Empty prefix.

    The met route reaches Empty prefix.

    Open full-size screenshot
  61. 5. Gate every retry with a budget

    61. Connect Counter unmet to Finish

    Drag from Counter's unmet output to an input on Finish.

    The unmet route reaches Finish.

    Open full-size screenshot
  62. 6. Run one item and inspect

    62. Check the node settings

    With Node autosave on, check the settings on the canvas. Switching nodes or using Back to Hub saves pending edits. If Node autosave is off, use Add to Tree for new nodes and Update for edits.

    The graph contains the configured nodes.

    Read and complete this step before continuing.

  63. 6. Run one item and inspect

    63. Return to the Hub

    Choose Back to Hub.

    The personal tree is shown.

    Open full-size screenshot
  64. 6. Run one item and inspect

    64. Find saved inputs

    Select the tree on the Hub and find its Run Parameters section.

    Saved inputs are visible.

    Read and complete this step before continuing.

  65. 6. Run one item and inspect

    65. Save Orb actions

    Set Orb actions to 5.

    Orb actions keeps the selected value.

    Open full-size screenshot
  66. 6. Run one item and inspect

    66. Wait for Saved

    Wait until Run Parameters shows Saved.

    The inputs are persisted.

    Read and complete this step before continuing.

  67. 6. Run one item and inspect

    67. Start the test

    On the selected Hub card, choose Run after checking the real setup.

    The configured run can begin on the prepared item.

    Open full-size screenshot
  68. 6. Run one item and inspect

    68. Inspect the ending

    Use a prepared magic item so the child returns without spending. Keep the mouse still, then compare names with Logs.

    Target match and budget exhaustion remain distinct.

    Complete and verify this step in the stated app or game.

  69. Check the result

    69. Open Logs

    Choose Logs.

    The actual sequence and exit can be inspected.

    Open full-size screenshot
  70. Check the result

    70. Inspect the actual result

    Compare accepted names with the retained group or row list, and count combined Augmentation/Alteration applications.

    At most five retry actions. Child conversion spend falls outside this allowance.

    Complete and verify this step in the stated app or game.

  71. If it does not work

    71. Review if it does not work

    - **Physical is missing:** create your own named group using [pseudomods](pseudomods.md). - **Child cannot load:** select your saved child again in Embed Tree. - **Wrong orb branch:** check [Empty Mods](empty-mod-slots.md) and advanced copied affix labels.

    The section context and checks are preserved.

    Read and complete this step before continuing.

  72. Next guide

    72. Review next guide

    [Adapt the weapon group for elemental targets](case-elemental-weapon.md).

    The section context and checks are preserved.

    Read and complete this step before continuing.

On this page

At a glance

Physical Weapon Roll opens the currency stash, calls a magic-rarity helper, then repeats a Mods check with Augmentation or Alteration. Its target is the pseudomod Physical, so the group's member rows determine what ends the loop.

Before you start

Complete setup, enable Orb stock guard, and configure Alteration and Augmentation. Prepare an identified, uncorrupted magic one handed sword you are willing to reroll. Use advanced item-copy information for affix names and prefix counts.

1. Create the parent and child

On the Hub, press + and create Physical weapon practice. Keep Current item selected. The source is Learn/High Value/Physical Weapon Roll.json, titled Learn: Physical Weapon Roll in saved Hub metadata.

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.

Prepare a personal magic-rarity child using Force magic rarity. Add Embed Tree to the parent and select that child. The sample references Learn/Rarity/RarityForcerMagic.json; that internal Learn helper is hidden from normal pickers, so select your own saved child when recreating the example.

2. Verify what Physical means

Add Check Item > Mods and select One Handed Sword as the item type. In Pseudomods, find Physical and inspect its members with the eye button.

The source group contains Flaring, Cruel, Tyrannical, Merciless, Conqueror's, Emperor's and Dictator's, each with Required 1 and Points 0. Your installed group may differ; inspect its rows before using it as a stopping rule. Click Close to return to the picker.

3. Set an explicit group threshold

With Physical selected in the picker, click Add pseudomod, then Done. Keep it as the check's only reference. In Advanced, turn off automatic Required threshold syncing, set the reference's Required to 1, Required matches >= to 1, and Score needed >= to 0.

This accepts one matching member, without measuring physical damage per second. Review pseudomod arithmetic before increasing the threshold.

On the Physical reference row, enter Required 1. Pseudomod reference rows expose Required and Only If. Points controls belong to stat-line rows; leave this check's Score needed >= at 0.

4. Connect the retry decision

Add Open Panel configured to ensure the currency stash is open. Connect Start → panel step → Embed Tree → Mods check. Connect Mods met → Finish.

Add Check Item > Empty Mods, choosing Empty prefix quantity: 1. Connect its met → Augmentation and unmet → Alteration. Connect both orb outputs back to the Mods check.

5. Gate every retry with a budget

Insert a Counter between Mods unmet and Empty Mods. Create a Number parameter Orb actions, fallback 5. Connect Counter met → Empty Mods and unmet → Finish, following Counter setup.

This allows at most five combined Augmentation and Alteration applications. The child runs before this Counter. Use an already magic item so its rarity check returns without spending; any Scour or Transmutation performed by a conversion child falls outside this allowance.

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 one item and inspect

Save Orb actions as 5 on the Hub and wait for Saved. Confirm Current item, then start on the prepared weapon. The source stores a bulk configuration with its disabled flag set; inspect your own run mode rather than relying on that saved grid.

Check the result

Read Logs and compare any matching modifier name with the group's members. Finish can mean a target match or an exhausted allowance. This loop makes no Regal, Exalt, sale or price decision.

If it does not work

  • Physical is missing: create your own named group using pseudomods.
  • Child cannot load: select your saved child again in Embed Tree.
  • Wrong orb branch: check Empty Mods and advanced copied affix labels.

Next guide

Adapt the weapon group for elemental targets.

Keep learning

Browse all guides

For setup help, the installer or license keys, join the official Discord. Sales and key issues: DM PathOfRolling. Check the account before paying; watch for impostors.