At a glance
Use one Mods check for a mandatory requirement and another for acceptable alternatives. Continuing only through both condition-met branches gives you life AND either fire OR cold resistance.
Before you start
Know how to add mod requirements and connect condition branches. Use an identified item that the app can read. The sample values below are hypothetical settings, not a valuation or crafting recommendation.
1. Write the intended rule
For this example, accept an item with at least 70 maximum life and at least 30 fire resistance or 30 cold resistance. Either resistance is sufficient, but life is always required.
Keep that sentence beside the tree while configuring it. It gives you a direct way to check that each accepted item satisfies the original rule.
2. Create the mandatory life check
Add Check Item > Mods. Choose the item type and required subtype, add the maximum-life stat line, then click Done.
Choose Simplified, set Min Value to 70, and select All configured mods. Keep this check to the single life row, then click Add to Tree.
3. Create the alternatives check
Add a second Check Item > Mods node using the same item scope. Add fire resistance and cold resistance, then click Done.
In Simplified mode, set each minimum to 30. Select At least N and set N to 1. This check accepts one or both qualifying resistance lines. Click Add to Tree.
4. Connect the AND relationship
Connect the previous step to the life check. Connect the life check's condition met output to the resistance check.
Connect the resistance check's condition-met output to the successful next step. Connect both condition-not-met outputs to your chosen retry or finish path. For an initial test, finish on failure and leave currency actions out of the test route.
5. Test three different outcomes
A hypothetical item with 75 life, 35 fire resistance and 10 cold resistance passes both checks. So does one with 75 life, 10 fire resistance and 35 cold resistance.
An item with 60 life and both resistances at 35 fails the first check. Two good resistance lines cannot compensate for missing life because they are evaluated in a separate node.
Also check an item with 75 life and both resistances below 30. It reaches the second check, then takes that check's condition-not-met path.
6. Reuse the alternatives when needed
If you need the same resistance choices in several trees, save those member rows as a pseudomod. In its receiving check, use Advanced mode with reference Required 1, Required matches 1 and Score needed 0.
Keep the mandatory life check separate. A pseudomod forwards member totals, and a group with two matching members can contribute 2. A single combined count across all requirements would allow unwanted compensation.
Check the result
Logs show the life check first. Only a passing life check reaches the resistance check. The final success path is reachable only when life passes and at least one resistance passes.
If it does not work
- An item without life reaches success: inspect the first node's condition-met connection and remove any bypass.
- Both resistances are required: change the alternatives check from All to At least N with N 1.
- A check passes unexpectedly: inspect its configured rows and minimums, including any reused group members.