Rust Genetics FAQ - Practical Crossbreeding Answers

The best workflow is cyclical: define target, evaluate one-step and path candidates, check center sensitivity, execute, and compare actual outcomes against expected chance. A single calculation is never enough for production quality. The strength of your system comes from repeated review and disciplined updates after each cycle.

Because parent IDs are only part of the recipe signature. Center genotype still matters in each slot whenever parent pressure is not strictly stronger. Tie branches also distribute probability across multiple outcomes. If center differs or tie pressure shifts, final exact chance and real outcomes can diverge.

Trust one-step when exact chance is practical, tie concentration in critical slots is low, and center substitutions do not collapse probability. If one-step depends on a rare center or produces frequent near-miss results, it is not production-safe. One-step is a speed tool, not a default policy.

Switch to path when one-step remains unstable after donor cleanup or repeatedly misses your operational threshold. Path mode reduces variance by inserting bridge milestones that stabilize weak slots before the final exact finish. It often saves time because fewer failed retries are needed.

Evaluate donor effect per slot, not by full-string aesthetics. A contaminating donor usually helps one visible column while increasing weak pressure in other important slots. Keep a short donor role log and move repeatedly contaminating donors to archive unless they are required for a narrow transition.

Screenshots show one observed outcome, not route resilience. They hide center dependence, tie-heavy critical columns, and contamination risk. Use screenshots only as examples, then validate with your own center options, donor bank, and slot-level chance profile before committing production resources.

Choose hemp targets by farm stage and cycle objective. Early cycles often benefit from stable bridge progression. Mature farms can enforce tighter exact goals if donor quality supports them. Always separate throughput cycles from development cycles to avoid mixed priorities and weak execution.

First define objective: stable daily supply or high-upside branch development. Stable supply routes prioritize repeatability and contamination resistance. Development branches can accept deeper path planning. Mixing both objectives inside one unmanaged route usually causes inconsistent output and poor decision clarity.

Bridge lines are intermediate recipes that remove variance before final targets. A strong bridge lowers tie density, supports center stability, and can be reused by multiple downstream routes. In long-term planning, reusable bridge lines often create more value than one isolated lucky finish.

Teams need explicit center governance. Define who can change center, when changes are allowed, and how center-sensitive routes are marked. Without policy, operators silently apply different assumptions, and reproducibility collapses. Center governance is a major quality control mechanism in shared clone banks.

At minimum log center ID, parent signature, expected exact chance, actual outcome, tie-sensitive slots, and contamination notes. This minimal dataset is enough to improve route quality quickly. Logs transform isolated attempts into a learning loop with measurable progress.

Retire routes that repeatedly underperform expected chance, remain contamination-prone after cleanup, or rely on unrealistic center conditions. Archive them for reference, but remove them from default production selection. Active pools should stay clean, explainable, and reproducible.

Score can reflect aggregate quality, but exact chance determines probability of achieving your specific target. A high-score card with weak exact chance may be less valuable than a lower-score card with stable exact outcomes. In production, exact chance and repeatability are usually the dominant metrics.

Never promote a route based on one screenshot. Require repeated outcomes, center substitution checks, and slot-level diagnostics before scaling. Overfitting happens when players treat isolated success as structural quality. Evidence across cycles is the real validation signal.