The Protecteur des Kwaks de Glace is a special case in the Dofus Retro bestiary. Unlike the vast majority of monsters, this guardian shows 100% resistance to every element in the game β Neutral, Earth, Fire, Water and Air included.
In plain terms, no damage spell will ever remove a single hit point from it. Before wasting your AP on it, read this guide to understand what it is, when you encounter it, and what to do instead.
A guardian monster unlike any other
The Protecteur des Kwaks de Glace spans levels 1 to 5, which might tempt newer players into thinking it is an easy target. It is a classic trap: its resistance stats (see the resistance table) show that every element sits at 100%, the exact definition of total immunity.
In practice, your damage spells will never deal a single point of damage against it. This type of monster is designed to fill a narrative or guardian role in a specific area, not to serve as a conventional xp source.
What 100% immunity actually means
In Dofus Retro, 100% resistance to an element means all damage of that element is reduced to zero. When all five elements reach that threshold simultaneously, no direct damage spell can hurt the monster.
That is exactly the situation with the Protecteur des Kwaks de Glace: Neutral, Earth, Fire, Water and Air all at 100%. Switching elements hoping to find a gap is pointless β there is none. This information is valuable precisely because it saves you from wasting turns, resources, or worse, losing a fight while blaming your build.
- Neutral: 100% β no physical damage
- Earth, Fire, Water, Air: 100% each β all magic elements useless
- Result: every direct damage spell is ineffective
What to do when you face it
If you encounter this monster unintentionally, the best option is to end the fight as quickly as possible through other means: spell reflection, summons, or simply passing turns and fleeing if that option is available.
For xp and kamas farming, just skip it entirely. Focus on regular Kwaks or other monsters in the area that have real exploitable elemental weaknesses.
Better xp alternatives at the same level range
Levels 1 to 5 offer plenty of far more accessible monsters for progression. Tofus, Gobballs and other early-game creatures have standard resistances with genuine weaknesses. Look for monsters that show 0% or negative values on at least one element: those are the ones that give the best fights-won to xp-earned ratio.
Reading resistance tables is a fundamental skill in Dofus Retro. The Protecteur des Kwaks de Glace case is an excellent lesson: it illustrates perfectly why you should always check a monster's resistances before engaging it for the first time.
MoonBot and immune monsters
When setting up a farm script with MoonBot, targeting fully immune monsters is a mistake to avoid: fights either last indefinitely or end in defeat, halting your progression and burning resources for nothing.
Best practice is to list precisely the monster names you want to engage in your Lua script. By excluding the Protecteur des Kwaks de Glace and targeting regular Kwaks or other monsters in the area, MoonBot only chains profitable fights and naturally avoids immune guardians.
Protecteur des Kwaks de Glace resistances
Resistance profile from the game data (β = weakness, β = immunity, Γ2 = vulnerable):
| Element | Resistance | Note |
|---|---|---|
| Neutre / Neutral / Neutro | 100 % | β |
| Terre / Earth / Tierra | 100 % | β |
| Feu / Fire / Fuego | 100 % | β |
| Eau / Water / Agua | 100 % | β |
| Air / Air / Aire | 100 % | β |
Ready-to-use Lua script
Paste this script into MoonBot to automate it:
-- Protecteur des Kwaks de Glace : immunite totale a tous les elements -- Ce monstre ne peut pas prendre de degats classiques -- Target monsters: Kwak de Glace 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




