An effective Dofus Retro Sram team composition does more than stack buffs around a damage dealer. Partners must deliver targets to useful cells, preserve an escape for the Sram and finish enemies before a trap network becomes an obstacle. Invisibility, Double, Fear and delayed damage need a shared plan.
Use this page with the complete Retro Sram guide. Spell values and monster behaviour can differ across active servers, so confirm them in the client.
Choose one primary Sram role
Assign Earth finisher, Air damage dealer, Fear positioner, corridor controller or network builder before the fight. A build may cover a secondary job, yet its opening should not chase every function simultaneously.
Define an observable result: remove the first target by round three, deny one attack, expose a line or save a vulnerable ally. This is more useful than judging the Sram only through total damage.
Reserve trap cells for the party
Partners need to know the network entry, trigger and forbidden squares. A stable convention based on map side, effect type or placement order prevents accidental movement and summons from consuming the route.
Never close every firing and healing line for one extra trap. Useful control leaves a push lane, support path and retreat cell for the next round.
Set party initiative
A positioner should act first when it can deliver a target to an immediate trap. Sram leads when Double, ally Invisibility or a corridor must exist before the other characters choose their actions.
Test both sequences on equal groups. Compare the first kill round and AP lost while waiting, because a neat theoretical order can perform badly on actual boards.
Pair Sram with Pandawa
Pandawa provides accurate displacement: isolate an enemy and put it next to the declared network entrance. The Sram must name the final cell rather than ask for an imprecise move toward the party.
Keep a branch for turns when carry or throw is unavailable. Fear, Repelling Trap and direct attacks should complete the play without total dependence on Pandawa.
Pair Sram with Sacrier
Sacrier pulls, swaps positions and carries pressure while setup develops. The duo performs well on boards where an attraction through a known axis creates an immediate focus target.
Do not place Double on a square required by Cooperation or Transposition. Decide who remains in melee after the trigger and which character owns the escape tool.
Pair Sram with Cra
Cra controls range, removes MP and covers distant lines. Traps become borders that punish the remaining path after a push instead of bets on random AI movement.
The usual failure is split pressure. Mark one priority so Cra does not repel an enemy while Sram constructs around another and leaves both threats alive.
Pair Sram with Feca
Feca protects setup rounds through armour and glyph control. The layers should complement each other: a glyph removes the safe option while a trap taxes the open route.
Stacking every defensive effect often wastes cooldowns. Compare one protected setup round followed by damage with a long lock that delays the kill.
Pair Sram with Eniripsa
Healing lowers the cost of contact, while additional AP may combine trap placement, Fear and an attack. Allocate the AP to an exact threshold; a bonus with no new combination adds little.
Move Eniripsa outside the hostile corridor before Sram vanishes. Otherwise every visible enemy turns toward the healer and cancels the defensive value of Invisibility.
Pair Sram with Iop
Iop supplies direct finishing against targets softened or presented by Sram. Fear and Double can align an enemy or hold it during preparation for a decisive damage turn.
Choose whether the trap is damage or placement. If Iop already reaches the killing threshold, two construction rounds are an avoidable tax.
Pair Sram with Enutrof
MP removal stretches the timeline and makes routes easier to forecast. Sram can place fewer traps with a higher likelihood of activation, while Enutrof supports resource-oriented sessions.
An enemy rooted outside the network still takes no trap damage. Retain range or a displacement action to convert control before it expires.
Pair Sram with Sadida
Sadida reduces MP, fills space with dolls and spreads pressure. This protects setup angles, but summons can occupy trigger cells and alter hostile pathfinding.
Separate the summoning area from the trap lane. Decide whether Block or Double anchors the entrance; using both in the same narrow passage is usually redundant.
Build a four-character Sram party
A balanced core contains Sram, positioner, support and finisher. Sram–Pandawa–Eniripsa–Iop favours decisive focus, whereas Sram–Cra–Enutrof–Feca controls open terrain and incoming pressure.
Every character needs a productive action while its signature spell is unavailable. Audit direct damage, recovery, protection, displacement, range and answers to hostile summons.
Use Sram in an eight-character team
With eight allies, animations and occupied squares reduce the return from long networks. Sram often becomes a direct finisher, occasional positioner or protector through Invisibility of Others.
Allocate areas of the board: push axis, melee lane, summon space and fallback. A trap should contribute before the next full initiative cycle, not demand that seven allies wait.
Use Invisibility of Others deliberately
Hide a threatened healer, a finisher waiting on cooldown or a positioner that must survive. Predict where enemy targeting transfers among the characters that remain visible.
Announce duration, purpose and return cell. An invisible ally still occupies space and can silently obstruct an essential route.
Place Double without blocking partners
Double should close a route, hold a target or absorb a named attack. Check firing lines, throw cells, glyphs, summons and the healer’s path before casting it.
Keep a response if the enemy walks around or pushes it. Value Double by hostile actions changed rather than the number of rounds it survives.
Coordinate party focus
Rank immediate threat, healing, summons, resistance, movement and finishing cost. Delayed and direct damage should converge on the enemy whose action will actually disappear.
Create a switch threshold: below that health, stop adding traps and use reliable direct damage. This prevents a field full of nearly defeated enemies.
Benchmark candidate compositions
Run twenty comparable fights for each variant. Log duration, first kill, incoming damage, bread, allies obstructed, traps activated and rounds without a productive action.
Read the median and worst quartile. The strongest Sram group stays functional on poor boards instead of looking exceptional only under perfect alignment.
Model the party in MoonBot
Version initiative, assigned roles, reserved cells, focus, Invisibility conditions, Double, network cap, pushes, healing, cooldowns and finishing mode. Each dependency needs a clear fallback.
Supervise initial battles and locate the earliest divergence in the log. Automation may violate Dofus Retro terms and put accounts at risk of sanctions.
Validate the final Sram composition
Confirm objective, party size, Sram function, order, positioner, support, damage, forbidden cells, target, escape, cooldowns and measurement. Include at least one unfavourable board.
The team is ready when every trap has a trigger, every partner retains a useful turn and finishing happens without extending the network for its own sake.
Botting breaches the game's terms of service and carries a sanction risk. No tool can guarantee that an account will never be banned.
