Diagnosing Dofus Retro Xelor mistakes requires separating symptoms from causes. Slow combat may come from gear, excess AP removal, poor focus or a lost line, so more damage does not necessarily fix the right problem.
This guide follows the MoonBot Xelor configuration. Apply one correction at a time and preserve the last stable version.
Capture the reference state
Record level, path, characteristics, equipment, rolls, spells, AP/MP, range, initiative, Wisdom, area, packs, profile version and date. Retain raw logs.
Without this snapshot, an apparent improvement may come from another item, board or target.
Classify the main symptom
Select duration, defeat, supplies, immobility, unused AP, wrong target, unproductive removal or logical loop. Give it a measure and frequency.
“Xelor plays badly” cannot be tested. “Three rounds in ten end with at least two AP” defines an observable defect.
Fix unused AP
First check whether remaining AP was reserved for escape. Otherwise find an expensive attack, missing range, impossible condition or incorrect gear breakpoint.
Write an unboosted and a Devotion rotation. Expected balance must match the log in every branch.
Fix excess AP removal
The symptom is large AP loss without fewer enemy actions or shorter duration. Missing enemy-specific thresholds are the usual cause.
Map control to one exact attack and stop when it becomes impossible. Reassign remaining AP to damage or placement.
Fix insufficient removal
When danger still happens, compare Wisdom, enemy resistance, attempt count, cast order and Loss of Motivation availability. Separate statistical failure from poor priority.
The AP-removal guide helps set a ceiling. Some targets should simply be killed earlier.
Diagnose unproductive Devotion
Count extra actions actually cast by every beneficiary. If bonus turns use identical spells and end with more AP, Devotion delays combat.
Change the AP breakpoint, positioning, initiative or cast condition. Retain an unboosted branch for low-return rounds.
Fix a wrong target
Compare danger, distance, health, resistance, AP dodge and positional power for every enemy. The nearest creature is not always the strongest first kill.
Separate damage and control targets. A slowed creature may remain secondary while the party finishes an accessible threat.
Break a movement loop
Xelor advances, retreats or uses Flight without creating an attack. Look for contradictory distance rules, late endpoint calculation or impossible line.
Set a movement maximum before attack or retreat. Log distance and ending cell after each decision.
Fix wasted Teleportation
Teleportation should not solve an adjustment handled more cheaply by MP or Flight. Reserve it for large gaps, critical exits or decisive lines.
Measure damage or health saved over the next two rounds. Increase its trigger distance when there is no gain.
Reduce excessive protection
Counter, Blinding Protection and Mummification may consume the turn without sufficient threat. Symptoms combine low damage, long duration and nearly full ending health.
Trigger from predicted damage and exposure rather than one health percentage. Include food saved in the outcome.
Fix late protection
If defence begins after position or health is lost, inspect initiative and the next enemy turn projection. The trigger reacts too late.
Add proximity, hostile line or unavailable escape conditions. Retest on the same dangerous boards.
Diagnose a disruptive summon
Homing Hand or Dial can occupy the attack axis, alter AI or extend animations. Compare battles with and without the summon.
Permit it only on specified cells and phases. Restrict the rule when its contribution does not change an action.
Detect incompatible gear
Sound logic fails when actual AP, range, initiative or characteristics differ from reference. Verify the loaded set after each exchange or defeat.
The Xelor gear guide recalculates rotations by breakpoint rather than aggregate score.
Diagnose initiative
If enemies break the line before the opening or allies act before Devotion, order is incorrect. Record values for packs actually encountered.
Add only necessary margin. Surplus initiative may cost damage, Wisdom or resistance without benefit.
Analyse slow combat
Split line search, boosting, control, first kill and finishing. Give the next experiment to the longest phase.
When finishing dominates, disable late removal and boosts. When opening dominates, improve range, initiative or board selection.
Analyse apparently random failures
Group failures by board, enemy, dodged removal, critical hit, blocked line and late trigger. A pattern often appears after ten incidents.
Create a graceful-degradation branch through retreat, protection, target switch or stop. Rotation cannot rely on the best roll.
Read minimum logs
Require round, state, target, AP, distance, spell, outcome, removal, prevented action, movement, health, equipment and version. Sort fights by symptom.
An error line without context is insufficient. Capture the three preceding decisions to find the origin.
Write a testable hypothesis
State: “changing X will move metric Y by Z on this family”. Define the accepting and rejecting outcomes before testing.
This prevents keeping a modification because one battle happened to improve.
Run an A/B test
Compare old and new versions on similar packs, boards and times. Target thirty fights per variant to read median and worst quartile.
Change one priority, threshold, spell or item. Include rejected boards in total time.
Prepare rollback
Save file, equipment, spell order and metrics before correction. Never overwrite the latest version completing the protocol.
Roll back if critical errors, failures or consumption rise even when mean damage improves.
Bound diagnostic tests
Use supervised short batches with ceilings for duration, health, supplies and repetition. Stop on unclassified behaviour.
Automation may breach Dofus Retro terms and result in sanctions. Check applicable rules and retain human oversight.
Validate the Xelor correction
Confirm reference, measured symptom, cause, hypothesis, single variable, metric, thirty trials, worst quartile, safety and rollback.
The fix is valid when it durably reduces the symptom without moving cost into failures, supplies or another phase.
Botting breaches the game's terms of service and carries a sanction risk. No tool can guarantee that an account will never be banned.
