⚙️ Combat configuration

How to configure Enutrof combat in MoonBot for Dofus Retro

MoonBot combat configuration screen for Enutrof in Dofus Retro
Contents
  1. Create one profile per role and context
  2. Complete the preflight sheet
  3. Build an action inventory
  4. Define turn states
  5. Calculate target scores
  6. Use real distance and paths
  7. Configure Water rotations
  8. Calculate Chance payback
  9. Handle finishing and unused AP
  10. Define the Clumsiness threshold
  11. Configure Reducing Key
  12. Configure Mass Clumsiness
  13. Configure Acceleration
  14. Maintain a summon register
  15. Configure Living Bag
  16. Configure Living Shovel
  17. Configure Corruption
  18. Configure Living Chest
  19. Control Pandora’s Box and Greed
  20. Handle small boards
  21. Synchronise team and initiative
  22. Filter groups and boards
  23. Define health, food, pods and banking
  24. Require replayable logs
  25. Test and version
  26. Avoid configuration mistakes
  27. Validate Enutrof configuration

A reliable MoonBot Enutrof combat configuration for Dofus Retro must trade Water damage, distance, removal, summons and loot value. A simple spell priority may cast Chance in a finished fight, remove MP from a neutralised enemy or summon Living Chest in a loop too short to repay it.

This page converts the Enutrof plan into observable rules. The combat bot guide covers the general framework. Automation can breach game terms and lead to sanctions.

Create one profile per role and context

Separate direct Water, MP removal, solo, team and loot. Add versions for every AP/MP total, spell rank and board type. A double-Judgement profile must not run silently with missing gear.

Name each version with element, level, AP, MP, role, family and date. Retain the control version for rollback after regression.

Complete the preflight sheet

Record Chance, Wisdom, damage, prospecting, AP, MP, range, initiative, Vitality, resistance, summon capacity and actual rank for every spell.

Compare with Enutrof gear and the spell order. Reject a profile where a mandatory rotation lacks prerequisites.

Build an action inventory

For every spell, record cost, minimum and maximum range, line, sight, cooldown, limit, element, low damage and purpose. Separate attack, buff, removal, range reduction, movement, summon, denial and loot.

Add a usage condition and rejection reason. Logs should state “target already neutralised” or “Chance not repaid,” never merely “spell ignored.”

Define turn states

Use immediate hit, approach, required control, emergency control, finishing, retreat and loot preparation. Select state before a compatible action.

Recalculate after every death, removal or movement. Once danger disappears, return to damage rather than following an obsolete defensive sequence.

Calculate target scores

Combine next-round threat, low-roll actions to kill, Water resistance, access, movement, range, healing, summoning and particular value. Reward finishing where it removes more actions than fresh control.

Lock a target only during an indivisible combination. Living Shovel or an ally may change its cell before the next action.

Use real distance and paths

Distance follows routes around obstacles and occupied cells. Classify a target as immediate range, short movement, control required or inaccessible.

Preserve a retreat cell and ceiling on enemies able to answer after movement. Advancing for Coins fails when several monsters then attack.

Configure Water rotations

The Water profile uses Coins for distributed finishes, Judgement at its AP breakpoint and Slaughtering from a low estimate. Create one combination per actual total.

Compare useful damage after overkill. A stronger Slaughtering should not replace cheaper Coins that finishes with margin and leaves AP for another target.

Calculate Chance payback

Before Chance, estimate remaining Water attacks during duration and extra low damage. Permit the spell where gain repays AP before predicted end.

Attack directly in short fights. Recalculate after an unexpected death because a buff planned for four rounds may no longer pay.

Handle finishing and unused AP

Select the cheapest action killing with low-roll margin. Reassign remaining AP to another target, required removal or a safe cell.

Every unused AP receives a reason: range, line, limit, cooldown, absent target, reservation or defect. Generic “end turn” blocks diagnosis.

Define the Clumsiness threshold

For each family, store starting MP, path, attack cell, range and minimum removal. Cast only while the target can still execute the dangerous action.

The MP-removal build measures denied actions. Recalculate cells after every attempt instead of using a fixed cast count.

Configure Reducing Key

Permit it where lost range removes a line or forces movement. Check current position and likely next cell before spending AP.

Do not automatically stack Key and Clumsiness. Test whether one suffices and return released AP to damage.

Configure Mass Clumsiness

Count enemies whose real sequence changes after AP removal and allies affected under current rules. Set a minimum useful-target count.

Respect cooldown and provide fallback. A large graphical area does not justify the spell where every monster retains its main attack.

Configure Acceleration

Acceleration requires a different final cell, open line, safe escape or ally able to finish. Compare path before and after the bonus.

Reject when extra MP ends unused. In a team, define the recipient and prevent duplicate movement buffs.

Maintain a summon register

Store type, cell, health, target, summoning round and purpose for Bag, Shovel and Chest. Reject duplicates while the same role remains active.

Clear state upon death and recalculate paths and lines. A free cell may make Coins or Judgement immediately superior.

Configure Living Bag

Permit Bag where it absorbs an attack, closes a passage or protects Enutrof for enough rounds. Its cell must not block the main line or retreat.

Estimate death and resulting path. Direct attacks remain first against a group defeated before acting.

Configure Living Shovel

Living Shovel needs a useful push direction, target whose MP-loss resistance matters and a long enough battle. Ban cells bringing a threat closer or breaking allied area damage.

Read all positions after its action. Do not cast Judgement at the old cell or retain a newly inaccessible target.

Configure Corruption

Define allowed target, dangerous round, acceptable healing, maximum post-effect health, cooldown and finishing plan. Select Corruption only where the denied action exceeds hits added by healing.

Provide fallback where the target is nearly dead or an ally already finishes it. An emergency button without restart logic creates endless battles.

Configure Living Chest

Chest receives group-value threshold, minimum predicted duration, safe cell and survival condition. Its cost and animation belong to calculation.

Use the prospecting guide to compare net kamas with and without it. Do not default to Chest in short fights.

Control Pandora’s Box and Greed

Permit Pandora’s Box where every possible outcome remains compatible and duration repays cost. The profile never depends on a favourable result.

Greed calculates allied gain and enemy danger. Solo uses a strict threshold; team play needs beneficiary and enemy lists.

Handle small boards

At melee start, prioritise finishing, escape cell or control preventing most damage. Bag, Acceleration, Shovel and Corruption answer distinct emergencies.

Reject the board where no sequence ends at safe distance. A win with heavy food does not validate configuration.

Synchronise team and initiative

In an Enutrof team, store positioner, removal owner, finisher, reserved cells and actual order. Read allies before every push or control action.

Gear reversing two initiatives requires a new version. Do not assume Pandawa positioned when its turn follows Enutrof.

Filter groups and boards

Define families, variants, Water resistance, size, level, board, distance, danger and maximum duration. Every rejection retains a reason to distinguish scarcity from an excessive filter.

The Enutrof area guide supplies benchmarking. Expand only after supervised boundary-composition trials.

Define health, food, pods and banking

Set continue, defensive and stop thresholds from plausible worst damage. After battle, define recovery, minimum food, free capacity, collection and bank return.

A badly wounded win or saturated inventory may be an economic failure. Measure the complete cycle.

Require replayable logs

Record round, positions, paths, candidates, scores, AP/MP, resistance, low damage, rejected spells, removal, summons, effects, health and expected value.

Logs should expose the first decision differing from intent without video. Keep labels stable between versions.

Test and version

Begin with ten supervised fights, then thirty with the same gear, boards and comparable groups. Measure median duration, worst quartile, first hit, unused AP, denied actions, summons, food and failures.

Change one rule per version and retain the control. An improvement on one board must not damage all others.

Avoid configuration mistakes

  • Sharing a profile across AP totals.
  • Casting Chance without payback calculation.
  • Removing MP after neutralisation.
  • Pushing a target outside allied lines.
  • Corrupting a nearly finished enemy without a plan.
  • Summoning Chest without a value threshold.

Validate Enutrof configuration

Check version, stats, ranks, rotations, low damage, target, distance, removal threshold, Key, Acceleration, Bag, Shovel, Corruption, Chest, allies, health, inventory and logs.

A good configuration returns to damage as soon as control produces its result and explains every AP, movement and summon.

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 do I configure Enutrof in MoonBot?

Create profiles by role and breakpoint, then define Water rotations, distance, removal, summons, health and logs.

How do I prevent useless MP removal?

Store the neutralisation threshold and recalculate reachable cells after every attempt.

When should Living Chest be configured?

Only where group value and duration exceed its cost, animation and risk.

How should Corruption be configured?

Define target, dangerous round, acceptable healing and finishing plan before permitting it.

How many fights should test a profile?

Ten supervised fights find faults, then thirty constant fights support comparison.

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