⚙️ Combat configuration

Dofus Retro Sram combat configuration in MoonBot

MoonBot combat configuration interface for a Dofus Retro Sram
Contents
  1. Set a measurable objective
  2. Version the Sram profile
  3. Design a combat state machine
  4. Capture a fresh decision snapshot
  5. Maintain a trap registry
  6. Generate candidate cells
  7. Bound AI prediction
  8. Reserve escape AP and MP
  9. Choose the opening
  10. Configure Invisibility
  11. Configure Double
  12. Configure Fear and triggering
  13. Cap trap-network construction
  14. Score target priority
  15. Separate Earth and Air profiles
  16. Create a finishing state
  17. Design explicit fallback branches
  18. Write an explainable combat log
  19. Test through controlled stages
  20. Read useful indicators
  21. Validate the Sram configuration

A useful Dofus Retro Sram combat configuration in MoonBot reasons about cells and state instead of replaying a spell list. A trap promises future damage, Invisibility changes exposure, Double alters paths and Fear moves the problem. Reliable logic evaluates the board again after every action.

Start from the Retro Sram guide and confirm costs, ranges and cooldowns in the active client. Automation may violate game terms and lead to account sanctions; investigate those rules and remain responsible for use.

Set a measurable objective

Select net XP, resources, safety or maximum duration. Add one secondary priority, such as lower bread use when two choices have similar speed.

Attach a metric: median battle time, first kill, incoming damage or realised sales. Without a goal, the system cannot trade one setup round against direct pressure.

Version the Sram profile

Store date, server, path, level, equipment, characteristics, spells, area and sample. One initiative or MP change can invalidate several rules without a code defect.

Change a single condition per experiment. Keep the previous version to compare equal boards and roll back a regression immediately.

Design a combat state machine

Use named states: opening, invisible setup, Double control, network, trigger, direct focus, retreat, finishing and emergency. Each has entry requirements, legal actions and an exit.

Forbid unlimited loops. Two or three network rounds, one placement attempt or a waited cooldown must transition somewhere else.

Capture a fresh decision snapshot

Collect positions, AP, MP, range, resistance, health, effects, cooldowns, invisible units, summons, known traps and reachable cells. Treat it as the only source for that decision.

Recompute after movement, push or summon. Reusing candidates from the start of a turn creates stale paths and illegal lines.

Maintain a trap registry

Store type, cell, placement round, area, owner, planned entrance and eligible target for every trap. Remove it after activation or an observation proving disappearance.

The registry prevents duplicates, pushes toward empty cells and unsafe allied routing. Distinguish confirmed knowledge from an inferred location.

Generate candidate cells

Begin with legally targetable cells, then filter occupancy, line, range, existing effects and escape. Score entry likelihood, damage, denied movement and setup cost last.

Do not select the nearest square by default. A slightly distant cell may merge two routes and preserve a Fear line.

Bound AI prediction

Log target, path, MP spent, avoided cells and response to Double by monster family. Derive confidence only from comparable observations.

Use confidence as a filter, never certainty. Below the chosen threshold, require a manual trigger or choose direct damage.

Reserve escape AP and MP

Calculate full sequence cost and movement needed to finish outside danger. Subtract this safety budget before ranking offensive actions.

If lock, a low roll or an obstacle removes the exit, transition to retreat. Another trap does not justify ending in exposed melee.

Choose the opening

Rank direct damage, Invisibility, Double and first trap using starting distance, next-round threat and predicted encounter length. Small packs frequently deserve immediate attacks.

Choose Invisibility when it avoids a peak or creates a repaid angle. Choose Double only where its cell changes a named hostile action.

Configure Invisibility

Define entry conditions, maximum hidden rounds, allowed actions, reserved MP and exit cell. Model exposure caused by attacks under the active rule set.

Leave the state as soon as its expected benefit ends, even if the effect remains. Damage avoided matters more than hidden-round count.

Configure Double

Generate cells where Double closes a corridor, holds one target or absorbs an identified attack. Remove cells blocking Sram, partners, pushes or support routes.

Add a branch for enemies walking around, pushing or ignoring it. Survival time alone is not the objective.

Configure Fear and triggering

Simulate the final position, crossed traps, collisions and the post-push board. Approve the cast only after computing damage or control.

If pushing removes every finishing line, compare an immediate strike. A trigger should shorten combat or suppress a threat.

Cap trap-network construction

Set maximum traps, setup rounds and expected minimum damage. The Sram trap network retains a named entrance and trigger.

At the cap, transition to direct focus automatically. This prevents visually impressive but unprofitable farming patterns.

Score target priority

Weight next-round threat, healing, summons, detection, movement, resistance, health and finishing cost. Add a bonus when delayed damage already commits to that enemy.

Lock focus until a significant event changes the ranking. Minor health variation should not scatter poison and traps.

Separate Earth and Air profiles

Earth values Deviousness lines, Fear conversion and Lethal Attack finishing. Air values Insidious Poison, Agility, Mistake and Con according to level.

Do not hide both paths behind vague weights. Create two testable configurations with versioned spells, ranges, thresholds and gear.

Create a finishing state

Once reliable minimum damage is lethal, disable new traps, Invisibility, Double and slow effects. Rank AP, probability, animation and final cell.

Keep a fallback for a low roll or missed resistance. Cleanup of small packs controls much of hourly output.

Design explicit fallback branches

Handle missing line, short range, occupied cell, lock, absent target, consumed trap and insufficient MP. Every rejection must lead to another legal action.

The final fallback protects, retreats or deals safe damage. It must not attempt the same impossible candidate indefinitely.

Write an explainable combat log

Keep state, snapshot, candidates, score, rejection rules, selected action, final cell, trap registry and outcome. Stable identifiers make rounds comparable.

During an incident, locate the earliest decision that departed from plan. Late symptoms such as death or slow recovery often begin with the opening.

Test through controlled stages

Start on a fixed board with simple cases, move to ten supervised fights and then thirty comparable encounters. Introduce teleports, summons and open geometry progressively.

Test no-cell, consumed-trap, blocked-Double and target-change cases. Reliability requires evidence from rare branches too.

Read useful indicators

Measure duration, first kill, traps placed and triggered, damage avoided under Invisibility, actions changed by Double, retreats, bread, errors and setup rounds.

Compare median and worst quartile with the prior version. A higher average paired with more failures is not a robust improvement.

Validate the Sram configuration

Confirm goal, version, states, snapshot, registry, candidates, prediction, budgets, opening, Invisibility, Double, Fear, network, focus, finishing, fallbacks, logs and sample.

The profile is ready when every action is legal and explainable, no loop is unbounded and thirty fights remain stable on approved boards.

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 I configure a Sram in MoonBot?

Build explicit states, a trap registry, AP/MP safety budgets, target scoring and legal fallback branches.

How can a Sram trap network be automated?

Store every cell, entrance and trigger, cap setup at two or three rounds and require minimum confidence.

When should automatic Invisibility be used?

Only when it avoids measured danger or creates a profitable angle with an exit cell already selected.

What belongs in a combat log?

State, positions, AP/MP, candidates, rejections, scores, traps, target, final cell, action and outcome.

Is bot use free of account risk?

No. Automation may breach Dofus Retro terms and result in account sanctions.

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