A reliable MoonBot combat configuration for a Dofus Retro Iop does more than rank spells by damage. It decides when to advance, which target to close, how much AP to preserve and when an impossible sequence must be abandoned.
This guide converts the Iop game plan into testable rules. Read the general combat and levelling bot guide for the wider framework. Automation can breach game terms and lead to sanctions.
Create one profile per element and context
Separate Earth, Fire and Air, then create a version for every AP/MP breakpoint and board type. Rules written for nine AP must never drive an eight-AP set. A solo profile cannot inherit team priorities without review.
Name each version with element, level, AP, MP, role and date. This prevents a small-board improvement from quietly damaging an open route.
Complete the preflight sheet
Before testing, record AP, MP, useful range, initiative, main element, damage, resistance, health and the real rank of every spell. Include health thresholds for recovery, retreat or session termination.
Compare the sheet with the Iop gear progression and Iop spell order. A high-priority action at the wrong rank creates a false diagnosis.
Build an action inventory
For every spell, record AP cost, minimum and maximum range, line of sight, linear cast, area, per-target limit, element and purpose. Separate attack, approach, push, placement, buff and finisher.
Add both a use condition and a rejection reason. MoonBot can then report “target outside line” or “AP reserved for finisher” instead of producing an opaque turn.
Split the board into distance bands
Use at least four states: contact, immediate attack, profitable approach and unreachable this turn. Calculate the actual path around obstacles rather than straight cell distance.
Give each band an objective. At contact, finish or push; in range, attack; during profitable approach, gain ground without exposure; when unreachable, attract, take cover or replace the target.
Choose movement or Jump
Walking has priority when it leaves enough AP for a meaningful attack and a safe ending. Use Jump only when it opens a hit, avoids a critical threat or prepares a measurably better next round.
Ban automatic Jump toward the nearest enemy. Inspect the landing cell, lock, incoming attackers, escape and remaining AP. A Jump without damage must produce a recorded benefit.
Define target priority
The score combines danger next turn, actions required to kill, elemental resistance, accessibility and disruption. A distant low-health unit falls behind a dangerous enemy Iop can finish now.
Recalculate after every movement, death or push. Lock only for the duration of a combo; otherwise the profile wastes AP on an objective that has become poor.
Control finishing and overkill
Estimate a low damage range rather than an optimistic average roll. Select the cheapest combination that finishes with a safety margin, then reassign remaining AP.
Set an overkill ceiling. A large attack becomes secondary when Pressure or Concentration is enough. Log enemies left at very low health so the safety margin can be corrected.
Earth Iop profile rules
The Earth Iop build uses Pressure for repeatable close attacks, Concentration when its restrictions are satisfied and Sword of Iop for reach or aligned targets from level 90.
Create combinations matching the exact AP total: approach plus attack, repeated hits or attack plus disengage. Iop’s Wrath remains a separate state, never merely the highest-damage action.
Fire Iop profile rules
The Fire Iop build protects Strengthstorm lines and notably exploits a nine-AP breakpoint when spell rank and game version support the intended sequence. Cut applies when its reach or effect improves the exchange.
Measure how many Strengthstorms may actually hit the same target. Do not spend approach AP when the destination blocks the combo or exposes Iop to several attackers.
Air Iop profile rules
The Air Iop build scores Celestial Sword by useful targets, potential allied damage and exit cell. A theoretical three-enemy area has no value when only one should be struck.
Set different minimum target counts by remaining health. Permit a single target when it finishes or prevents a dangerous turn, while requiring a richer area against healthy enemies.
Order Power and other buffs
Cast a buff when attacks remaining during its duration repay the AP. Power precedes damage when its gain crosses a finishing threshold; it waits when the fight ends immediately.
Mutilation supports physical Neutral and Earth damage in this game version, so do not insert it blindly into Fire or Air profiles. Apply the same present-cost versus future-attacks test to every boost.
Use Intimidation and Blow as fallbacks
Intimidation breaks contact, pushes into a relevant obstacle or frees a line. Blow corrects a formation when displacement changes the following action.
Neither spell is a default AP dump. Require an outcome: removed threat, accessible target, created area or freed ally. Otherwise preserve AP or select an attack.
Handle small boards and the first round
On a small board, restrict forward movement when several enemies can surround Iop. The opening round chooses between an immediate finish, a profitable buff and a waiting cell behind cover.
Create a special rule for contact starts while retaining the same danger criteria. Close placement does not automatically justify spending every AP offensively.
Synchronise team initiative and placement
In an Iop-centred team, record the actual character order. A positioner acts before the combo it enables, while protection and vulnerability must remain active at the correct round.
Reserve cells expected by allies and avoid pushes that break their line. A team profile can accept a less immediate target to focus everybody’s damage.
Model the Iop’s Wrath calendar
Store the cast round, next window, intended target, estimated health and access obstacles. On every round, confirm that the target still exists and that a replacement can be reached.
Preserve AP and position only while execution remains likely. If the calendar breaks, return to the normal Earth plan instead of losing several rounds while chasing an impossible Wrath.
Define health, recovery and ending rules
Set three thresholds: continue, play defensively and end the session. Base them on plausible worst incoming damage rather than an average. Include food expenditure in profitability.
Post-combat rules specify collection, delay, recovery and restart conditions. A win at one health is not an operational success when it destroys route safety or yield.
Require readable combat logs
Record round, position, candidate targets, selected score, path, AP before and after, expected and actual damage, rejected spells and final health. Include every fallback trigger.
A log should reconstruct the decision without a screen recording. Stable labels make two profile versions comparable.
Test and version the profile
Begin with ten supervised fights against one family, followed by thirty measured fights without changing equipment. Compare median duration, no-damage rounds, overkill, food, retreats and defeats.
Change one rule in each version. Retain the previous profile, its preflight sheet and sample; one faster record does not prove an improvement.
Frequent configuration mistakes
- Sharing a profile between different AP totals.
- Using Jump without testing the attack and landing cell.
- Ranking spells by maximum damage alone.
- Casting Mutilation for non-physical paths.
- Treating Iop’s Wrath as an ordinary attack.
- Changing several rules during a benchmark.
Checklist before the session
Verify version, element, AP/MP, ranks, initiative, board, distance bands, walking, Jump, priority, finishing, buffs, push, Wrath, health thresholds and logging.
Run only under supervision, on a small sample and within the risk framework you accept. A stable configuration explains every choice and returns cleanly to a fallback plan.
Botting breaches the game's terms of service and carries a sanction risk. No tool can guarantee that an account will never be banned.
