The Osamodas in Dofus Retro delegates part of combat to summons. They block corridors, absorb attacks, chase targets or add damage while their master supports the team. That autonomy is powerful, but every creature adds animations and decisions that may slow farming.
The goal is not to summon whenever a spell is available. A strong Osamodas profile selects the creature that answers the map, preserves direct damage and applies buffs only when several future actions can repay them.
The Osamodas role
Solo, a summon creates a second presence. It attracts monsters and opens firing lanes, reducing pressure on the character. In teams, Osamodas supports allies and uses creatures to hold one cell or divert a dangerous target.
Congestion is the limit. A badly placed creature blocks Iop, closes Cra's line or prevents Pandawa from dropping a target. Define the job before casting: damage, blocking or sacrifice, never simply filling the map.
Fire, vitality and summon builds
Fire retains direct attacks and Intelligence-linked support. A vitality/summon profile relies more heavily on creatures and the master's survival. A hybrid remains useful when a summon cannot reach its target.
| Build | Benefit | Limit |
|---|---|---|
| Fire | Autonomy and support | Less summon specialization |
| Vitality | Durability in long fights | Lower direct damage |
| Summons | Several map roles | Time and congestion |
For solo progression, avoid a completely passive profile. Summon AI does not always choose an ideal path; direct damage lets Osamodas finish a target or correct the choice without waiting another turn.
Choose the right summon
Classify creatures by function. One holds, another deals damage and another provides utility. In each area, allow only roles that answer present monsters. A fragile summon against repeated area damage is not worth its AP.
Maximum summon count is not a target. Two active creatures may already occupy important cells. One or none will usually be faster in short fights. Against a boss, an additional body can instead create several safe turns.
Simple test: compare ten fights with and without the summon. Keep it only if duration, bread or win rate improves.
Make buffs profitable
A buff gains value when its target acts several times. Do not enhance a nearly dead creature or one too far away. Check whether the bonus changes its attack count or the number of turns required to finish.
In a team, an ally may be a stronger target. Prioritize the character that crosses an AP breakpoint, reaches several enemies or acts immediately afterward. Initiative order then becomes part of the build.
Spells, characteristics and gear
Level one main attack, one reference summon and one or two recurring supports. Extra points go to tools that solve the area's weakness. Intelligence and vitality provide a strong base; AP, range and summon bonuses complete the rotation.
Do not pay for an unused summon bonus. Every item should support the normal turn: summon plus attack, buff plus attack, or two direct actions. Later, add resistance and initiative so Osamodas prepares the field before allies become exposed.
Suitable XP areas
Choose maps where creatures reach enemies without long detours. Narrow corridors create traffic jams; huge maps extend movement. Predictable damage helps select a summon that survives long enough.
Measure duration with every animation. A safe victory can still offer poor hourly XP when five summons act each turn. Read the MoonBot XP guides and test a minimal profile before adding creatures.
Team synergy and placement
Feca protects summons that must hold a cell. Eniripsa extends an important creature, while Cra exploits the obstacle to preserve range. Pandawa can correct placement but needs empty cells.
Reserve corridors for melee characters and limit summons on small maps. In multi-account play, let Osamodas act before attackers when distributing buffs, or after the positioner when filling a precise cell.
Configure Osamodas in MoonBot
Create a distinct rule per summon: target distance, enemy count, sufficient map space and no identical creature already active. Add a global cap to prevent overcrowding. Buffs should inspect remaining health, proximity and expected future turns.
Keep a default attack and safe range. Test small and large maps, then configure health, bread and bank rules. The combat bot guide explains condition design.
Frequent mistakes
- Maxing summons without measuring animations.
- Buffing a creature that will die or reach nobody.
- Blocking ally lines and destination cells.
- Building a profile with no direct fallback attack.
- Using identical summons against every group.
Recommended progression plan
Begin with a Fire build that can attack, one main summon and one support. Measure their contribution over ten fights. Add vitality, AP and another summon only when the scenario requires it. In automation, three reliable decisions beat ten weak conditions.
The best summoner does not fill the map; it casts the creature that changes the fight.
Botting breaches the game's terms of service and carries a sanction risk. No tool can guarantee that an account will never be banned.
