A Dofus Retro Osamodas MoonBot configuration must explain why it attacks, summons, buffs, heals or saves AP. Complexity comes from occupied cells, creature AI, cooldowns, resistance and combat phase rather than a long spell list.
Build the character with the Retro Osamodas guide. Confirm every name, cost, range, target and effect inside the active client before turning rotation into rules.
Define the operating scope
Record client, server, level, path, gear, ranks, zone, team and goal. A configuration is valid only for that dated set.
Automation may breach Dofus Retro terms and cause sanctions. Check applicable rules and begin with supervised trials.
Inventory active spells
For every spell record AP, range, line of sight, boostable range, cooldown, cast limit, target type, area and active-rank effect. Do not rely on another version.
Add client evidence and a date. This sheet is the configuration source of truth.
Describe combat state
The decision engine needs AP/MP, health, positions, resistance, enemies, allies, living creatures, cooldowns, effects, free cells and initiative.
Use a cautious branch when data is missing. Distance alone does not prove a line or legal target.
Separate Fire, Water and summon profiles
Fire prioritises Ghostly and safe Punch; Water organises Lashing lines; Vitality trades presence against direct action.
Create distinct versions. A single profile full of conditions becomes difficult to diagnose.
Write the action hierarchy
A starting order may be survival emergency, certain kill, mandatory mechanism, reposition, main attack, functional summon, repaid buff, fallback attack and movement.
Filter legal candidates before scoring. An impossible high priority must not stop the round.
Calculate target priority
Combine kill probability, next-round threat, healing, summoning, positioning, resistance, distance and finishing cost. Weights change by phase.
Log every score component. An unexplained target cannot be tuned reliably.
Generate summon cells
Enumerate legal cells, then remove exits, allied lines, position areas, dead ends and gratuitous exposure. Score the remainder against the likely target.
Project creature movement too. A good cast cell can become an obstacle after its turn.
Limit summon capacity
Set a maximum by scenario and phase within actual capacity. Count living creatures before every cast.
Animal Blessing may temporarily change capacity by rank; use the new slot only for a proven function.
Create a summon role table
Associate Tofu with movement, Gobball with contact, Prespic with AP testing, Boar with push, Bwork with range, Crackler with presence and Wyrmling with Fire/unbewitching under the reference.
Give each creature target, map, stop condition, allowed buff and replacement. Unlock level alone decides nothing.
Select the useful summon
Score expected action, survival, reachable target, cell, remaining duration and animation cost. Reject when no probable target exists.
Compare direct damage for the same AP. A creature should repay investment before combat ends.
Configure buffs
Bear Cry, Feline Movement, Toad, High-Energy Shot, Natural Defence and Fangs solve separate problems. Trigger each from a measured effect.
Project useful rounds and active-rank limits. Stop long buffs near finishing.
Control High-Energy Shot
Confirm exact targets and effects for the rank. Count additional legal actions rather than an abstract bonus.
Require minimum duration and a creature able to act. Otherwise Ghostly or movement takes priority.
Control Feline Movement
Project cells made reachable by extra MP. The buff earns AP only when it opens a target, block or useful exit.
Reject when mobility may close a line or pull the creature away from the plan.
Control Toad and Natural Defence
Estimate likely hits and the function retained by survival. Defence on an ignored target produces nothing.
Deduplicate team protection. Attack when the creature already survives its next action.
Control Bear Cry and Fangs
Compare added low damage over planned actions to cost and delay. Do not score one maximum.
Require minimum rounds or attacks. A direct finisher wins in a short window.
Configure Ghostly Claw
Validate range, line, Fire resistance, cast count and low damage. Score the target most reliably approaching a kill.
Keep a second target if the first loses line. Save enough MP to avoid a dead-end cell.
Configure Lashing Claw
Enable Water from level 36 only when Chance, rank and gear make it useful. Recalculate Water resistance for each target.
Add Fire, weapon or summon fallback when every Water line is rejected.
Configure Punch of the Crackler
Generate reachable cells, project every area target under active rules, then the final position. Punch unlocks at 54.
Compare useful total damage with attacks received after entry. Reject areas that remove exit or focus.
Configure Animal Healing
Confirm eligible target, missing health, threat, future actions and replacement cost. Measure health actually received.
Heal only where the creature preserves a function before the finish. Otherwise attack or prepare another cell.
Configure Whip
Verify active rank, eligible targets and exact Retro effect. Use an allowlist of cases instead of a broad “summon exists” condition.
Compare removed danger, direct attack and positioning cost. Log every use to reveal a bad target.
Manage Wyrmling and unbewitching
Red Wyrmling unlocks at 100 in the consulted reference. Its AI-driven unbewitching cannot guarantee exact timing.
List priority effects and retain a team fallback. Do not automate a critical mechanism after one successful trial.
Configure master movement
Score cells by future attack, exit, hostile distance, buffs, allied lines and creature space. Remove dead ends before damage scoring.
Save MP where next round converts it into an attack. Maximum movement is not a goal.
Program openings
Create sequences by distance and board: direct attack, summon/buff, approach or team positioning. Add a branch for occupied cells.
Revalidate state after every action. Creatures and targets may move.
Provide AP fallbacks
For every real total write two secondary actions: another Claw, weapon, summon, repaid buff, useful healing or preparatory movement. Respect limits and cooldowns.
Frequently unused AP may indicate a gear breakpoint problem rather than priority.
Create a finishing mode
When danger is low and hostile health falls within direct low damage, disable new summons, long buffs and unnecessary healing.
Select the shortest path in animations and AP. Test low rolls to avoid premature finishing.
Synchronise a team
Share initiative, focus, reserved cells, planned healing, protection and unbewitching. A creature must not cancel the following character's action.
Test profiles alone, dependent pairs, then the group. The Osamodas team guide assigns roles.
Log every decision
Keep entry state, legal candidates, rejection reasons, scores, selected action, target, cell, outcome, creature behaviour and final state.
The log should replay the first incorrect decision without guesswork.
Test in stages
Validate an isolated scenario, ten supervised fights and thirty comparable groups. Archive a control before each change.
Change one rule and compare duration, failures, unused AP, purposeless summons, bread and net. Restore control when the worst quartile falls.
Avoid configuration errors
- Filling capacity without role mapping.
- Confusing distance with line of sight.
- Buffing without a calculated extra action.
- Healing after a creature's last useful round.
- Changing spells, gear and zone together.
- Omitting a no-cell branch.
Validate the Osamodas configuration
Confirm context, spells, state, profiles, targets, cells, capacity, roles, buffs, attacks, healing, Whip, movement, openings, fallback, finishing, team and log.
It is ready when thirty fights are explainable and stable without orphan creatures or regularly lost AP.
Botting breaches the game's terms of service and carries a sanction risk. No tool can guarantee that an account will never be banned.
