⚙️ MoonBot configuration

How to configure Cra combat in MoonBot for Dofus Retro

Cra combat configuration interface in MoonBot
Contents
  1. Create one profile per build and breakpoint
  2. Write a preflight character sheet
  3. Treat every spell as an action
  4. Order Cra buffs by return
  5. Set Fire, Earth and Air priorities
  6. Assign a targeting mode by function
  7. Build combat distance bands
  8. Move before or after the shot
  9. Set an area-effect threshold
  10. Configure pushback and MP removal
  11. Handle line of sight and minimum range
  12. Write a first-turn opening
  13. Create a compact-board fallback
  14. Add challenges after stability
  15. Configure Cra inside a team
  16. Define battle end and recovery
  17. Read useful Cra decision logs
  18. Validate and version the configuration
  19. Account for automation risk
  20. Frequent Cra configuration mistakes
  21. Checklist before enabling the profile

A strong MoonBot Cra combat configuration does not rank every spell from highest to lowest damage. It states when to buff, which enemy to select, what distance to preserve and where to end the turn so the next shot remains possible.

This tutorial converts the Dofus Retro Cra guide into observable rules. It focuses on class logic; the general combat bot guide introduces the wider configurator.

Create one profile per build and breakpoint

Separate Fire, Earth and Air rather than placing their spells in one list. Each path has a different rotation, distance and targeting logic. Create another version when AP or a major spell changes the turn.

Name the profile with element, level band, AP and context, such as “Fire Cra 90–119 8 AP solo.” The convention prevents an outdated configuration from reaching a differently equipped character.

Write a preflight character sheet

Record AP, MP, range, initiative, element, minimum damage and levelled spells before setting priorities. Add permitted board and monster profiles. Rules cannot repair a rotation that the actual sheet cannot perform.

The Cra gear guide helps identify breakpoints. When one item changes, duplicate the profile and retest instead of silently editing the stable version.

Treat every spell as an action

For each active spell, record AP cost, minimum and maximum range, line of sight, intended uses, element, area and function. Separate damage, buffs, pushback, removal and finishing.

An action belongs in the list only with an explicit condition. “Use Retreat Arrow” is incomplete; “use it when pushback prevents the next attack and retains a future line” can be tested.

Order Cra buffs by return

Distant Shooting, Critical Shooting, Powerful Shooting, Lynx Eye and Bow Skill do not have equal value every round. A buff precedes damage when its duration and future impacts repay the AP investment.

Prevent early renewal and skip a buff when battle ends before payback. Against a weak group, immediate damage often cuts total duration more effectively.

Set Fire, Earth and Air priorities

The Fire profile opens an area attack only with enough useful targets. Earth prepares heavy shots and keeps a reliable finisher. Air reserves AP needed for movement or recovery.

In every path, place a certain finish above a large spell when it removes an enemy action. Theoretical maximum damage must not leave a target barely alive.

Assign a targeting mode by function

A single-target attack can select the immediate threat, weakest enemy or compatible resistance. Area damage searches cell groups, while pushback selects the threat whose next movement will truly change.

Do not use one global order. The best finishing target differs from the best control target. Store the criterion beside each spell so MoonBot’s choice remains explainable.

Build combat distance bands

Divide space into contact, immediate danger, firing distance and out of range. Each band gets one purpose: escape, control, attack or approach a useful lane.

Values depend on enemy MP and the build’s range. Calculate safety after the opponent’s next movement, not only the distance visible at turn start.

Move before or after the shot

Moving first may open a line or area. Attacking first uses a safe current cell before retreat. Write two branches instead of one instruction to travel as far as possible.

Every destination retains an option for the next round. Near board edges, an unused MP can be worth more than a move that removes every retreat path.

Set an area-effect threshold

Define a minimum count of useful enemies and exclude allied cells where required. Two targets are not always enough: a single-target finish on the main threat may produce more value.

Count which enemies survive and what they do next. The threshold represents prevented actions rather than the raw damage sum.

Configure pushback and MP removal

Control gains priority when it changes expected contact into an attack-free enemy turn. It is wasteful against an opponent already too far away, blocked or certain to die before movement.

Reserve AP for the fallback branch on compact maps. If removal fails, move or finish instead of repeating the same action blindly.

Handle line of sight and minimum range

Add a fallback when the first spell lacks a line: move, select another target or use a compatible attack. The choice must preserve AP for the remaining sequence.

Test diagonal obstacles and enemies that begin too close. Perfect open-board range does not prove the profile can escape a blind angle.

Write a first-turn opening

The opening may combine a buff, shot and final placement. Keep a short branch for weak groups and a preparation branch for durable enemies.

Initiative and starting cells change the choice. Do not advance merely to spend MP when no attack exists; select the cell that creates the strongest second turn.

Create a compact-board fallback

When starting distance falls below the threshold, activate a safety rotation: nearest threat, push or control, lateral movement and damage with remaining AP. The accepted-health requirement may also rise.

Test the branch against the Cra solo PvM plan. An unmastered close board remains rejected rather than becoming a random case.

Add challenges after stability

Disable optional constraints while validating normal combat. Then add one challenge at a time with an abandonment condition when compliance creates danger or exceeds maximum duration.

A bonus cannot compensate for a falling win rate. Keep separate measurements with and without challenges to prove net gain.

Configure Cra inside a team

The team profile knows which buffs, placements and control actions precede its turn. Cra does not push a target Pandawa must place or occupy the finisher’s cell.

Align initiative with the Cra team composition. If one ally is missing, stop or use an explicitly validated degraded profile.

Define battle end and recovery

Set health thresholds for engagement, healing and loop termination. Add food, pods and required consumables. The end of one fight always prepares the state of the next.

After a defeat, retain board, group, round and last branch. Block the failing case until review instead of returning automatically to the same engagement.

Read useful Cra decision logs

Keep chosen target, rejected spell, missing line, remaining AP, movement, minimum damage, health loss and turn duration. These events connect an outcome with one rule.

Search for repeated patterns: unused AP, late buffs, ineffective pushback or movement toward an edge. One isolated anomaly does not justify a profile rewrite.

Validate and version the configuration

Run ten very easy battles, ten open boards and ten boundary cases. Change one rule between versions and keep the old profile until the new one improves win rate, duration or consumption.

Attach profile name, gear sheet and test area to results. This prevents a gear or group difference from being misattributed to targeting.

Account for automation risk

Automation violates the game’s terms of use and can lead to sanctions. No setting eliminates that risk. Make an informed decision and begin with short supervised sessions.

Add safe stops for unknown behaviour, movement loops, disconnected accounts and inconsistent results. A reliable profile stops cleanly when it can no longer decide.

Frequent Cra configuration mistakes

  • Mixing elements and gear breakpoints in one profile.
  • Ranking spells by damage without target conditions.
  • Renewing a buff before it is needed.
  • Pushing an enemy that could not attack anyway.
  • Testing only on a favourable open board.
  • Changing gear and rules in the same series.

Checklist before enabling the profile

Verify version, element, AP, MP, range, levelled spells, buff order, targeting, distance bands, area threshold, close fallback, health, pods and error stop.

The profile is ready when thirty representative battles explain their choices, do not waste AP without reason and return to a safe state after every known exception.

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 Cra spells be configured in MoonBot?

Give every spell a function, priority, target, distance and condition rather than using a simple list.

Does each element need a separate profile?

Yes, because Fire, Earth and Air use different rotations, areas, distance and targeting criteria.

When should Retreat Arrow be automated?

Use it when pushback prevents a future attack or restores a line without breaking the rotation.

How should a Cra profile be tested?

Validate ten easy fights, ten open boards and ten boundary cases while changing one rule at a time.

Is Dofus Retro automation risk-free?

No. Automation violates the game terms and may be sanctioned; no setting removes that risk.

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