⚙️ MoonBot configuration

Dofus Retro Sacrier combat configuration for MoonBot

MoonBot combat configuration for a Dofus Retro Sacrier
Contents
  1. Capture the reference
  2. Define states
  3. Score targets
  4. Configure the Water opening
  5. Configure the Air opening
  6. Configure Earth and Fire
  7. Encode punishments
  8. Encode Attraction
  9. Encode Swap
  10. Encode Cooperation and Transposition
  11. Set Dissolution’s minimum
  12. Set a Fury cap
  13. Detect Punishment’s window
  14. Bound Sacrifice
  15. Manage Flying Sword
  16. Create recovery state
  17. Create retreat
  18. Create finishing
  19. Add safety limits
  20. Structure logs
  21. Test and validate
  22. Maintain configuration
  23. Validate the Sacrier profile

A MoonBot Sacrier configuration for Dofus Retro must know when to approach, absorb, attack, recover and leave. A static “punishment then attack” priority ignores boards, health, resistance and remaining rounds.

This method expands the Retro Sacrier guide. Adapt field names to the installed MoonBot release.

Capture the reference

Record level, path, characteristics, gear, rolls, AP/MP, initiative, resistance, spells, area, packs and software version. Date everything.

A configuration without reference cannot be compared after an item or rank change.

Define states

Use opening, approach, exposure, attack, positioning, Punishment, recovery, retreat and finishing. Every state has entry, priority, exit and round limit.

Prevent no-damage loops. After too many movements, switch target or stop.

Score targets

Combine danger, distance, resistance, health, escape, pushback, unbewitching and area potential. Separate kill and positioning targets.

Provide an accessible backup. Sacrier should not cross the board chasing a priority that became poor.

Configure the Water opening

Identify central cell, converging enemies and the target to pull. Cast Bold Punishment only where impacts and Water attacks remain.

Enter the area only if Dissolution can be cast now or health supports waiting.

Configure the Air opening

Test an Assault line and an ending cell with productive lock. Use Attraction where it adds an attack.

Nimble Punishment receives minimum impacts and future actions. Conditional Agility cannot be required for first escape.

Configure Earth and Fire

Earth checks Foot or weapon contact; Fire checks Absorption’s line. Both need a high-resistance branch.

Cast elemental punishment where later attacks beat an immediate strike.

Encode punishments

Store minimum enemies, predicted impacts, remaining rounds, linked attack, health floor and stop condition for every punishment.

The punishment guide separates produced and consumed boosts.

Encode Attraction

Require Attraction to create an attack, area or useful block. Check axis, obstacles, ending distance and remaining AP.

Forbid it where the target arrives naturally or exposes Sacrier before recovery.

Encode Swap

Give Swap an expected starting and destination cell. Permit it for freeing, filling an area or opening a line.

Recalculate target and exit immediately after exchange. Do not let the old path trigger a return loop.

Encode Cooperation and Transposition

Map Cooperation to an enemy and Transposition to an ally or summon. Define ending cell and next action first.

Log cooldown and retain a missing-target variant. An absent dependency must not freeze the turn.

Set Dissolution’s minimum

Define target count by resistance, health and danger. Permit a single target only for finishing or emergency recovery.

Calculate net outcome after expected enemy attacks. Gross healing is insufficient.

Set a Fury cap

Limit repetitions by health, useful remaining damage gain and offensive rounds. Stop before retreat.

Log health cost and strengthened attacks. Unconverted Fury is a direct loss.

Detect Punishment’s window

Use current health percentage, minimum damage, accessible target and AP. Project earlier life steal or healing in the same round.

Keep a replacement attack. Never seek health loss solely to trigger the branch.

Bound Sacrifice

Define eligible allies, combined damage, active protection, health floor, duration and cancellation. Evaluate several sources in one round.

Disable solo. In parties, coordinate initiative with healing and protection.

Manage Flying Sword

Permit the summon where it creates a Transposition target, diverts an enemy or supports recovery. Reserve its cell.

Measure behaviour, blockage and animation. Forbid it where it closes retreat.

Create recovery state

Choose Dissolution, Absorption, Bloodthirsty Madness or retreat by path, target and health. Recovery must not add more danger than healing.

Set a round limit. Afterward stop or change plan instead of extending without damage.

Create retreat

Base the threshold on plausible next-round damage, available AP/MP and a free cell. Reserve resources before attacking.

With no exit, Evasion, protection or stopping occurs earlier. High Vitality does not replace the branch.

Create finishing

When the last target falls below guaranteed minimum damage, disable punishments, long positioning, Sacrifice and unnecessary summons.

Select the cheapest attack and retain a short correction. Use a low-roll threshold.

Add safety limits

Set health, duration, no-damage rounds, movement, unused punishments, supplies and failures. Every limit triggers alert, retreat or stop.

Trigger bounds deliberately in a small sample. An unused limit is unverified.

Structure logs

Record round, state, target, cell, AP/MP, health, spell, outcome, impacts, boost, area, healing and transition reason. Add version and time.

Capture the three decisions preceding an error. Diagnostics needs the chain.

Test and validate

Create isolated cases for blocked line, useless punishment, insufficient area, dead exchange target, low health and finishing. Verify the expected exit.

Then run thirty comparable fights and log duration, health, food, errors and failures. Compare median and worst quartile.

Maintain configuration

Revalidate after spell, gear, reset, area or software changes. Preserve the last stable version and a change log.

Automation may breach Dofus Retro terms and result in sanctions. Check rules and retain human oversight.

Validate the Sacrier profile

Confirm reference, states, targets, openings, punishments, movement, areas, Punishment, Sacrifice, recovery, retreat, limits, logs and tests.

The profile is ready where every branch attacks, recovers, exits or stops cleanly without loops.

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 a Sacrier punishment be configured?

Define predicted impacts, remaining rounds, linked attack, health floor and stop condition.

When should Attraction be used?

Only where it creates an attack, area or useful block with enough remaining AP.

How can Punishment be automated?

Check health percentage, accessible target, minimum damage, AP and planned healing, with a backup attack.

How can Sacrifice be secured?

Limit allies, combined damage, protection, duration and health floor before casting.

Which tests are required?

Test each branch in isolation, then run thirty comparable fights with median and worst quartile.

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