Some Dofus Retro monsters simply have high resistances. The Bitolder goes further, issuing a flat prohibition from the moment you glance at its elemental profile: Fire is completely off the table. Its Fire resistance is so extreme it constitutes functional immunity — every flame spell you cast is a wasted action point.
Earth, on the other hand, remains open — the relative weak point in an otherwise defensive profile. This guide explains how to capitalise on that narrow window to maximise XP and earnings at one of the most significant level milestones in Retro progression.
The Fire immunity: the mistake every newcomer makes
The Bitolder sits at level 100 — a symbolic threshold where many players arrive with a firmly established build, often centred around a dominant element. If that element is Fire, the encounter turns into a disaster: the Bitolder's Fire resistance is so extreme it grants functional immunity. Your flame spells deal essentially zero damage, regardless of your raw power stat or equipment level.
This is not a tactical exaggeration — it is a mechanical reality you must internalise before your first pull. A pure-Fire Iop or Sacrier who ignores this warning will watch their fights drag endlessly and their XP per hour evaporate. Check the resistance table: the Fire number speaks for itself.
- Fire: near-total immunity — zero or near-zero damage regardless of gear
- Never engage a Bitolder with a purely Fire build: it is wasted time
Resistance table: Earth as the only real entry point
Beyond the Fire immunity, the Bitolder carries moderate resistances on Neutral, Water, and Air — meaningful, but not prohibitive for a class that has not gone all-in on those elements. Earth, at a resistance of only 10%, is clearly the path of least resistance.
A 10% Earth resistance is not a spectacular vulnerability, but it stands in sharp contrast to the rest of the profile. An Earth-built character — Pandawa, Sadida, Earth Osamodas, or an Earth Iop — will spend AP with decent returns and finish fights in a reasonable timeframe. Other elements work, but less efficiently. Earth is the pure-logic choice.
- Earth: 10% resistance — the relative weakness, the element to prioritise above all
- Neutral, Water, Air: moderate resistances — viable with strong equipment
- Fire: immunity — zero damage, must be excluded entirely from your rotation
Level-100 combat strategy: discipline and efficiency
At level 100, the Bitolder is not an enemy to underestimate even with Earth. Its moderate resistances on Neutral, Water, and Air mean a hybrid character must make disciplined choices about rotation — limiting non-Earth spells to those that still offer decent returns.
Positioning matters: the Bitolder may have movement abilities or attacks that punish close-range characters. Assess your class's options to stay within optimal range for your Earth spells while avoiding the most punishing counter-attacks. Where possible, open with a positional advantage and save your high-AP Earth spells for the first turns, before the enemy has acted.
Profitability at level 100: top-tier XP and worthwhile drops
Level 100 is one of the most important caps in Dofus Retro, and the Bitolder contributes to that progression meaningfully. XP per fight ranks among the highest in its category — provided you finish fights quickly, which Earth enables precisely through its relative weakness advantage.
On the kamas side, Bitolder drops include resources sought by high-level crafters. Without citing specific rates, consistency is the master principle: steady farming over several hours, free of elemental mistakes (and therefore free of the dragged-out fights that Fire would cause), generates a predictable resource flow that converts into reliable kamas. Avoiding Fire means avoiding slow fights — and slow fights are the hidden cost most players underestimate.
Preparing your character: which class suits this spot?
Not all Earth characters are equal against the Bitolder. The ideal class has Earth spells with good range, capable of sustaining damage over multiple consecutive turns without relying on risky melee positioning. Pandawa Earth — with smart keg placement — is particularly effective here. Sadida can use its dolls as shields while dealing consistent Earth damage from safety.
For hybrid classes that cannot go fully Earth, the alternative is to accept a slight efficiency loss on non-Fire spells (Neutral, Water, Air all pass with moderate resistances) while rigorously avoiding every Fire spell. The golden rule remains unchanged: Fire equals zero damage equals wasted AP.
MoonBot and the Bitolder: never touch Fire, automatically
One of the most concrete risks of manually farming the Bitolder is inattention: after a long session, a moment of distraction is all it takes to fire off a reflexive Fire spell and burn a full turn. MoonBot eliminates that risk at the root by locking the Earth elemental strategy from the outset.
The script bundled with this guide explicitly sets the Earth element, engages only Bitolders, and loops without supervision. You will never accidentally trigger a Fire spell, fights stay efficient, and XP accumulates at the optimal pace — even during extended absences.
Bitolder resistances
Resistance profile from the game data (★ = weakness, ∞ = immunity, ×2 = vulnerable):
| Element | Resistance | Note |
|---|---|---|
| Neutre / Neutral / Neutro | 25 % | — |
| Terre / Earth / Tierra | 10 % | ★ |
| Feu / Fire / Fuego | 1480 % | ∞ |
| Eau / Water / Agua | 30 % | — |
| Air / Air / Aire | 30 % | — |
Ready-to-use Lua script
Paste this script into MoonBot to automate it:
-- Farm Bitolder : Feu INTERDIT (immunité 1480%), Terre = faiblesse (10%) -- L'élément Feu inflige 0 dégât : ne JAMAIS l'utiliser contre un Bitolder -- Target monsters: Bitolder function move() config.setBankThreshold(90) -- back to the bank at 90% pods return { { map = "MAP_1", path = "right", fight = true }, { map = "MAP_2", path = "right", fight = true }, { map = "MAP_3", path = "bottom", fight = true }, } end function bank() return { { map = "BANK_MAP", npcBank = true } } end function phoenix() return { { map = "PHOENIX_MAP", phoenix = true } } end -- Replace MAP_1, MAP_2… with the “x,y” coordinates of your maps.
Watch on YouTube




