⚙️ MoonBot configuration

Dofus Retro Xelor combat configuration for MoonBot

MoonBot combat configuration screen for a Dofus Retro Xelor
Contents
  1. Capture profile prerequisites
  2. Define combat states
  3. Rank targets
  4. Configure the Fire opening
  5. Configure the Water/Wisdom opening
  6. Configure Air and Earth paths
  7. Encode the AP-removal threshold
  8. Create the Devotion branch
  9. Create the unboosted turn
  10. Manage range and line of sight
  11. Order Flight and Teleportation
  12. Trigger protection spells
  13. Manage Xelor summons
  14. Create finishing mode
  15. Reserve required AP
  16. Add safety limits
  17. Structure logs
  18. Test each rule in isolation
  19. Validate across thirty fights
  20. Maintain the Xelor profile
  21. Validate the Xelor configuration

A MoonBot Xelor configuration for Dofus Retro must separate attacks, useful AP removal, boosts, movement and escape. A flat spell list fails because the same Slow Down can rescue a round or waste AP depending on the enemy’s remaining actions.

This operational guide extends the Retro Xelor pillar. Check exact field names in the installed MoonBot release before adapting examples.

Capture profile prerequisites

Record level, path, characteristics, equipment, rolls, AP/MP, range, initiative, Wisdom, resistance and spell ranks. Add monster family and permitted boards.

Assign a version identifier and date. A profile without a reference state cannot be diagnosed after change.

Define combat states

Use at least opening, control, damage, retreat, protection and finishing. Every state has an entry condition, priority action and exit condition.

Prevent a state from triggering itself without progress. Limit rounds or attempts before switching to a safe branch.

Rank targets

Score enemies by dangerous action, distance, elemental resistance, AP dodge, health and ability to break position. Separate kill and control targets.

Provide a backup when the primary leaves range. The logic should not cross the entire board to chase a priority that became poor.

Configure the Fire opening

Test a Hand or Sandglass line before moving. Use Temporal Dust only when its area reaches the required target count without ally danger.

Keep a high-Fire-resistance branch: secondary attack, productive control or target switch. Repeating ineffective damage is not fallback.

Configure the Water/Wisdom opening

Clock attacks and interacts with AP, yet the plan must work without gain. Calculate the initial-capital rotation first and add a success branch afterward.

Cap removal attempts against resistant targets. Switch to damage or escape after the threshold.

Configure Air and Earth paths

Air checks Frostbite or Shrivelling lines and values contact escape without Flight. Earth needs Punch’s axis and exact distance.

Add a refusal rule when geometry cannot be reached this round. Several movements for one attack damage throughput.

Encode the AP-removal threshold

Associate each family with its dangerous-action cost and required AP loss. Stop Slow Down, Sandglass or Time Theft once that action becomes impossible.

The Xelor AP-removal guide measures attempts and prevented actions. Reassess after Wisdom changes.

Create the Devotion branch

Cast Devotion only when its bonus adds an action to Xelor or reached allies. Check area, initiative order, duration and remaining AP after cast.

Document the complete boosted turn. “Cast when available” can delay the first kill without producing another action.

Create the unboosted turn

Keep a sequence independent from Devotion: attack plus removal, reduced double attack or attack plus escape. It becomes the baseline for every calculation.

If no line spends base AP correctly, fix gear or spell order before adding complex conditions.

Manage range and line of sight

For each attack define minimum and maximum distance, linear constraints, obstacles and cast count. Calculate the ending cell before movement.

Prefer a position retaining a line next round. The shortest path does not always end on the best cell.

Order Flight and Teleportation

Flight solves contact or short correction; Teleportation performs a wider reset with cooldown. Give each a distinct distance threshold.

Forbid the cast where movement creates no attack, safe exit or placement objective. Log the cells before and after.

Trigger protection spells

Counter, Blinding Protection and Mummification should answer predicted damage, proximity or death risk. Avoid one shared health threshold for all three.

Include duration, cooldown and opportunity cost. Good protection saves more resources than the extra rounds it creates.

Manage Xelor summons

Homing Hand and Dial occupy cells and follow their own behaviour. Permit them only where the cell blocks, attracts or supports a named action.

Measure animation and targeting mistakes too. A theoretically useful summon may reduce hourly output.

Create finishing mode

When the final target drops below guaranteed minimum damage, disable excess removal, group boosts and long protection. Choose the cheapest conclusive attack.

Base the threshold on a low roll, never average critical damage. Keep a second attack where resistance changes.

Reserve required AP

Budget escape, protection or finishing before attempting control. Another removal attempt must not consume the only retreat.

Log starting AP, gains, spending and balance. Any difference exposes a false rotation assumption.

Add safety limits

Set minimum health, maximum duration, rounds without damage, consecutive removal without prevention, supplies and failures. Each threshold triggers retreat, stop or alert.

These bounds protect a session from unknown boards and missing states. Trigger them deliberately before long execution.

Structure logs

Record round, state, target, distance, AP, attempted spell, outcome, AP removed, action prevented, movement, health and transition reason.

Add profile version and timestamp. A readable log reconstructs the decision without video.

Test each rule in isolation

Create short cases for blocked lines, dodged removal, unavailable Devotion, contact, low health and final target. Verify one expected exit per case.

Do not patch several branches together. A unit change avoids moving the defect elsewhere.

Validate across thirty fights

Keep family, board and pack band comparable. Record duration, first kill, unused AP, prevented actions, movement, protections, health, food and errors.

Compare median and worst quartile with the prior version. Roll back when a new rule reduces stability.

Maintain the Xelor profile

Revalidate after spell rank, equipment, reset, new area or software change. Preserve the latest stable version and a change log.

Automation may violate Dofus Retro terms and expose the account to sanctions. Check applicable rules and retain human oversight.

Validate the Xelor configuration

Confirm reference state, targets, unboosted turn, removal threshold, Devotion, lines, movement, protection, finishing, reserves, limits, logs and tests.

The profile is ready when every branch finishes, retreats or stops cleanly and thirty fights show no critical AP waste.

Botting breaches the game's terms of service and carries a sanction risk. No tool can guarantee that an account will never be banned.

Frequently asked questions

How should Xelor AP removal be configured in MoonBot?

Map every enemy to a dangerous action, cap attempts and stop once its cost becomes impossible.

Should Devotion be cast whenever available?

No. Cast only when its bonus adds a useful action for Xelor or a correctly positioned ally.

How should Flight and Teleportation differ?

Use Flight for contact or a short correction and Teleportation for a wider reset.

Which logs should be retained?

Round, state, target, distance, AP, spell, outcome, removal, movement, health, version and transition reason.

How many fights validate the profile?

Test isolated rules first, then run at least thirty comparable fights before a long session.

Ready to automate Dofus Retro?

Create an account, add your characters and launch your first automation from a browser. There is no software or VPS to install.

Try MoonBot See pricing