How to Test an Elgrove-to-Dualith Demon’s Hand Breeding Chain

A proposed breeding chain is useful only when each pairing, offspring result, and passive checkpoint can be evaluated separately.

Define the exact chain before breeding

Convert the broad goal into two independently testable stages without presenting the proposed route as established fact.

• Write the final goal as two separate conditions: producing Dualith and retaining Demon’s Hand.
• Record Elgrove as the proposed starting carrier only as part of the route being evaluated; the supplied evidence does not verify the mechanic.
• For Stage A, list both proposed parents, the expected intermediate species, and whether that intermediate must display Demon’s Hand before it can advance.
• For Stage B, list the qualifying Stage A offspring, the proposed second partner, and Dualith as the expected species result.

Tag the plan to the current version

Keep observations useful when breeding mechanics may be patch-sensitive.

• Record the game version, platform or server context, and test date at the top of the route log.
• Keep older lists, comments, and personal notes labeled by their stated version rather than treating them as current confirmation.
• The supplied official patch excerpt does not document the named combinations or passive-inheritance behavior, so it cannot validate either stage.

Check feasibility before the first attempt

Identify missing parents and unsupported assumptions before resources are committed to the full chain.

• Confirm that the proposed parents for Stage A are present and available in the current save.
• Identify every parent or intermediate result required by Stage B, even though Stage B will not be tested yet.
• Mark each pairing as observed in the current version, supported only by an outside claim, or still unverified.
• Pause the plan if a required pairing is unclear or a required parent is inaccessible.

Test Stage A as a bounded question

Learn whether the first pairing produces the expected intermediate without mixing that question with later-stage results.

• State the Stage A expectation as a hypothesis before beginning.
• Record each observed offspring species without replacing the original expectation.
• Track whether Demon’s Hand appears in a separate field from species.
• Use a personal attempt, time, or resource cap and stop when that cap is reached.

Apply the advancement gate

Prevent an unsuitable intermediate from entering Stage B and obscuring where the route failed.

• Advance an offspring only if it matches the species requirement established for Stage B.
• If the plan requires Demon’s Hand at the intermediate stage, confirm that the selected offspring visibly has it before continuing.
• If the species matches but the passive does not, record partial progress without treating passive transfer as confirmed.
• If the species does not match, recheck the first pairing rather than compensating with repeated Stage B attempts.

Test Stage B and interpret the result

Evaluate the final species and passive outcomes separately while preserving the limits of a small test.

• Record the qualifying intermediate and proposed second partner used for each Stage B attempt.
• Log whether the observed offspring is Dualith and whether it displays Demon’s Hand as two distinct outcomes.
• A Dualith result without Demon’s Hand answers the species question for that observation but leaves passive transfer unresolved.
• One successful observation documents that attempt; it does not establish a universal inheritance rate or a permanent rule.

Decision checklist

• Record the current game version and test context.
• Write both proposed parent pairings before beginning.
• Define the expected intermediate species for Stage A.
• Decide whether the intermediate must display Demon’s Hand to advance.
• Confirm that every required parent is available in the save.
• Track offspring species and passive status in separate fields.
• Set an attempt, time, or resource cap for each stage.
• Stop and recheck the first failed checkpoint before continuing.

Worked example

Hypothetical log: Stage A uses Elgrove and the proposed first partner, with “Intermediate X carrying Demon’s Hand” written as the advancement requirement. After each attempt, the player records the observed species in one column and Demon’s Hand status in another. If Intermediate X appears without the passive, that observation is marked “species condition met; passive condition unresolved,” and the offspring does not advance under this plan. If a qualifying Intermediate X appears, Stage B begins with that individual and the proposed second partner. A resulting Dualith is recorded separately from whether Demon’s Hand appears, so the player can identify which part of the proposed chain still needs verification.

Common mistakes

• Treating a community-suggested pairing as confirmed current-version evidence.
• Beginning the second stage before the first-stage offspring meets the written advancement requirement.
• Recording the expected offspring instead of the species actually observed.
• Combining species success and passive success into one result field.
• Inferring an inheritance rate from a small personal sample.
• Continuing after the preset limit without identifying what the extra attempts would test.

Related guides