🕸️ Class mechanics

Dofus Retro Sram trap networks with Invisibility, Double and AI

Invisible Sram and Double preparing a trap network in Dofus Retro
Contents
  1. Define the network result
  2. Inventory available traps
  3. Turn the board into a path graph
  4. Validate free cells
  5. Project trigger order
  6. Begin with two traps
  7. Use Repelling Trap
  8. Use Fear as a trigger
  9. Use Tricky Blow before Fear
  10. Constrain routes with Double
  11. Test Double as a trigger
  12. Prepare while invisible
  13. Plan the Invisibility exit
  14. Observe AI without assuming it
  15. Handle an enemy avoiding the trap
  16. Handle teleports and leaps
  17. Handle hostile summons
  18. Place Mass Trap
  19. Place Poisoned Trap
  20. Place Paralyzing Trap
  21. Place Trap of Silence
  22. Integrate Lethal Trap
  23. Choose manual trigger or waiting
  24. Secure networks in teams
  25. Set a setup limit
  26. Score the network
  27. Log every network
  28. Measure reliability
  29. Configure a network in MoonBot
  30. Avoid network errors
  31. Validate a Sram network

A Dofus Retro Sram trap network is a position sequence, not a collection of hidden cells. It becomes reliable when the target has few exits, trigger order is projected and a push or hostile movement converts setup into measured damage.

This guide complements Earth Sram and Air Sram with an element-independent method.

Define the network result

Choose damage, removal, displacement, path denial or finishing setup. Every trap should approach that result.

Set maximum AP and rounds too. An unlimited construction can cost more than its target.

Inventory available traps

Record AP, range, line, linear cast, area, cooldown, free-cell rule, effect and element at the active rank. Use the Retro client sheet.

Tricky, Mass, Poisoned, Paralyzing, Silence, Repelling and Lethal traps serve different functions. One damage score cannot replace them.

Turn the board into a path graph

Treat reachable cells as nodes and legal moves as edges. Obstacles, lock, MP, borders and units remove options.

The best cell is often a mandatory passage, not the nearest square. Count routes remaining after placement.

Validate free cells

A cast may fail where the cell contains a unit, invisible entity or incompatible object under active rules. Verify state before spending the sequence.

Keep a secondary cell. A profile stopping at the first obstacle loses the round.

Project trigger order

Write entry cell, first effect, resulting cell and next effect. Displacement immediately changes available actions.

Test exact order in the client. Similar traps may lead elsewhere through placement and rules.

Begin with two traps

Pair movement with damage or two areas where the first forces the second. The chain should work from a simple diagram.

Measure success before adding a third piece. Complexity multiplies assumptions.

Use Repelling Trap

Available at 54, Repelling Trap changes a unit's cell relative to position. Draw destinations and possible collisions.

Reserve safe allied destinations. A push outside the network cancels setup.

Use Fear as a trigger

Fear at 60 offers controlled push where axis, range and cells permit. It reduces reliance on spontaneous AI choice.

Lay the trap, preserve AP and recheck position. An interposed unit can invalidate push.

Use Tricky Blow before Fear

Before 60, Tricky Blow can create a push chain by rank. It also combines direct damage and exposure under active rules.

Compare AP, possible reveal and final cell. Plan replacement when Fear arrives.

Constrain routes with Double

Double occupies a cell and may close the shortest route. Reduce paths without blocking trigger or Sram exit.

Observe actual lock, health, resistance and movement. A wrong Double assumption changes the graph.

Test Double as a trigger

Under a trap's target rules an allied summon may interact with its area. Verify in an isolated scenario before important combat.

Do not sacrifice Double where future blocking has greater value. Compare triggered damage and diverted actions.

Prepare while invisible

Invisibility supplies placement rounds and angles. After each action, move to retain several plausible final cells.

Define the intended network before casting. Searching for perfection while hidden destroys efficiency.

Plan the Invisibility exit

Define round, cell, target and visible action: Fear, attack, daggers or movement. Keep fallback when the network is bypassed.

Confirm which active actions reveal. Order indirect effects first.

Observe AI without assuming it

Across ten trials record start, MP, selected target, available paths, avoided cells and attempted attack. Classify by monster family.

A trend is not a guarantee. Reliable networks retain Fear correction or direct damage.

Handle an enemy avoiding the trap

Find which alternative became cheaper through distance, line, allied target or observed trap response. Change one cell.

Do not cover every exit immediately. Reduce them with Double, obstacles or positioning, or attack.

Handle teleports and leaps

Non-walking movement can ignore intermediate cells. Identify range, target and cooldown before relying on a path.

Build around the probable destination or reject the group. More path traps cannot fix teleportation.

Handle hostile summons

A creature may trigger, occupy or divert a network meant for its master. Score probability and cost.

Finish the summoner, adapt focus or reserve another path. The network needs eligible targets.

Place Mass Trap

Its area can affect several units on trigger. Project every ally and enemy at that exact time.

Use it as a certain destination, not decoration. Count useful damage rather than surface.

Place Poisoned Trap

Delayed value requires a living target. Put it early only where later triggers remain probable.

Do not let poison duration delay finishing. Measure applied effects.

Place Paralyzing Trap

It may reduce exits and improve next-round prediction. MP removal must cross an action or distance threshold.

Recalculate the graph with remaining MP. Do not count removal that denies nothing.

Place Trap of Silence

Verify exact client effect and AP the target will spend. Value comes from changed action or applied damage.

Remove it where combat ends early or the target can switch behaviour.

Integrate Lethal Trap

At 100, Lethal Trap can form the damage core, but placement and cooldown constraints remain. Build outward from its cell.

One certain push beats several guessed paths. Keep direct fallback for failed placement.

Choose manual trigger or waiting

Compare Fear AP, waiting risk, future damage and natural probability. Trigger manually when uncertainty costs more than push.

Wait only when the target is constrained and saved AP opens another useful action.

Secure networks in teams

Announce cells, areas, order and trigger. Reserve allied, summon and position routes before placement.

Add cancellation when Pandawa, Sacrier or another actor moves the target. An obsolete network must not dictate focus.

Set a setup limit

Choose two or three maximum rounds according to content, targets and danger. At the limit calculate best direct attack.

This avoids sunk-cost bias. A placed trap does not require completing a poor network.

Score the network

Add probable low damage, denied actions and saved health; subtract AP, rounds, animations, allied risk and failure probability.

Compare with Deviousness, Con, Lethal Attack or weapon over the same window.

Log every network

Keep board, target, traps, placement order, cells, paths, trigger, result, unused effects and first AI divergence.

A final screenshot is insufficient. Diagnosis needs state before every decision.

Measure reliability

Across thirty groups log started, completed, natural, forced and avoided networks, AP invested, damage, duration, bread and failures.

Calculate trigger rate and useful damage per setup round. Compare against a direct control.

Configure a network in MoonBot

Version board templates, allowed cells, active traps, order, target, Double, Invisibility, Fear, round cap, fallback and detailed logs.

Start with a supervised two-trap chain. Automation may breach Dofus Retro terms and cause sanctions.

Avoid network errors

  • Placing before defining the trigger cell.
  • Assuming deterministic AI.
  • Forgetting invisible or occupied cells.
  • Closing Sram's exit with Double.
  • Continuing beyond setup limit.
  • Measuring theoretical rather than triggered damage.

Validate a Sram network

Confirm result, target, graph, free cells, order, movement, Double, Invisibility, exit, trigger, team, limit, fallback and measure.

It is ready when repeatable on its board class, correctable and better scored than direct attack.

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 Sram trap network begin?

Define one destination cell and link only two effects, including controlled movement or push.

How can triggering be made reliable?

Reduce routes with obstacles or Double, keep Fear as a manual trigger and preserve direct fallback.

What does Invisibility do for networks?

It supplies placement rounds and angles, but requires a setup cap and planned exit cell.

How should monster AI be measured?

Across identical trials log paths, target, MP, avoided cells and first divergence without treating a trend as guaranteed.

When should a network be abandoned?

Stop at the setup cap, after an uncorrectable bypass or as soon as direct attack scores higher.

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