Theme
Simulator and Optimizer Problems
What you see
A Lab tool is missing, unavailable, or gives an unexpected result.
What it usually means
The module may be disabled, login may be required, or the profile and inputs may not match the scenario.
Safe checks and resolution
Check the availability label, sign in if requested, refresh the profile inputs, and compare one controlled input change at a time.
When to contact an authorized manager
Ask for help when the issue depends on role assignment, community scope, review status, or a locked workflow. Include the page name, visible message, selected scope, approximate time, and the safe steps already tried. Do not include passwords, tokens, private keys, or unrelated personal data.
Related guides
Practical depth
Verify assumptions before results
Confirm profile, save state, units, current levels, targets, resources, and scenario name. Lab comparisons do not change live player, event, or inventory records and cannot guarantee an in-game outcome.
Worked example, recovery, and limitations
What you see: A Hero Gear plan stops with Forge Hammers remaining. Checks: Confirm active profile, visible saved state, current levels, locks, strategy, weights, every material balance, and dataset version. Decision: Remaining Hammers alone may not fund any valid positive step if XP, Mythic Gear, or Mithril is exhausted, a slot is locked, or the next gain has non-positive configured value. Recovery: Correct the input, wait for saved confirmation, and rerun; compare before state, ordered steps, and leftovers. The iterative plan is deterministic but not a proof of global optimality or live-game outcome. Include module, scenario, dataset, save state, inputs changed, and unexpected output.
The safe workflow changes one assumption in a copied scenario. It cannot guarantee future game balance, exact live damage, or recovery of a profile whose newer version legitimately won a save conflict.
A saved result changed after an update
Hero Gear XP costs and reforge comparisons, Bear formation search, and account-stat handling have been refined. Re-run the same input under the current catalog and compare objective, profile, locks, formation, and stat source before comparing totals. A previous screenshot is a historical result, not the current calculation.
If inputs changed after a run, use the tool's Run or Optimize action to refresh a stale result. If screenshot import misreads a field, leave it unselected and enter it manually. See Screenshot Build Import and Ascension Path for safe input and scenario boundaries.
Input and layout fixes to know about
Recent fixes cover the current-build selection and edit controls, battle stat labels, compact percentage inputs, dropdown chevrons, hover effects, and light-theme input contrast. If an old screenshot shows a different arrangement, use the current field label and the dedicated tool guide. Recheck the selected build before editing and rerun after changing calculation inputs.
The release notes separate calculation fixes from presentation improvements so a layout change is not mistaken for a change to game mechanics.