The Chevalier is one of Dofus Retro's most durable farming targets, scaling from level 50 all the way to 200. That wide level range makes it a reliable source of experience across dozens of hours of gameplay β something very few monsters can claim.
What sets it apart mechanically is its perfectly balanced resistance profile, which flips the usual element-selection logic on its head.
Why the Chevalier is worth farming
Few monsters in Dofus Retro remain relevant from the mid-50s all the way to level 200. The Chevalier is one of them. Its experience output stays competitive across that entire range, meaning you won't need to swap targets as your character grows β a real convenience for automated farm sessions.
On the kamas side, its drops feed the market consistently. Building up a stack over a long session and selling at the auction house can translate into meaningful income, especially for players running multiple accounts.
Reading the resistances: a perfectly armored foe
The Chevalier's resistance profile is unique in Dofus Retro: every element β Neutral, Earth, Fire, Water, and Air β sits at exactly the same value (see the resistance table). There is no exploitable weakness, no immunity to avoid, and no vulnerability to amplify.
This means element selection is purely character-driven. Play whichever element your build is optimized for. An Iop going Neutral/Earth should stay that course; a Sram running Fire spells has no reason to switch. The Chevalier will take equal damage from any source.
- No immunity β all elements deal damage
- No vulnerability β no bonus damage either
- Best element = whatever your character is built around
Chaining fights efficiently
The Chevalier's high level and solid stats mean that sustaining a long farm session requires preparation: life regeneration consumables when needed, careful positioning at fight start to limit incoming damage, and a consistent action-point rotation to end fights quickly.
Players who care about maximizing fights per hour typically turn to automation at this point. Manually clicking through every engagement adds up to significant lost time. MoonBot handles the full loop β engagement, combat, cooldown β so the session runs at peak efficiency without human intervention.
Profitability: strong XP, bonus kamas
A high-level Chevalier delivers solid experience per fight. Compounded over a multi-hour session, this makes it one of the better options for pushing through the notoriously slow 100-170 level range where XP sources become scarce.
The accumulated drops from an overnight automated session can be liquidated at the auction house for a steady kamas income. The exact return depends on the server's economy, but regular farming beats sporadic play every time.
Automate with MoonBot: the Chevalier script
MoonBot's Lua scripting engine lets you define the full farming loop: target selection, combat strategy, wait times between fights, and automatic restart after each victory. The script in this guide uses Neutral as the element β swap the `element` value to match your character's build.
Import the script into MoonBot, select your account, and let the loop run. Whether you're farming overnight or during a work break, the bot keeps the session going at a consistent pace.
Chevalier resistances
Resistance profile from the game data (β = weakness, β = immunity, Γ2 = vulnerable):
| Element | Resistance | Note |
|---|---|---|
| Neutre / Neutral / Neutro | 60 % | β |
| Terre / Earth / Tierra | 60 % | β |
| Feu / Fire / Fuego | 60 % | β |
| Eau / Water / Agua | 60 % | β |
| Air / Air / Aire | 60 % | β |
Ready-to-use Lua script
Paste this script into MoonBot to automate it:
-- Farm Chevalier en boucle (tous elements a 60%, on joue Neutre) -- Target monsters: Chevalier 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




