Farm monsters in Dofus 3 with EZGather
The bot attacks the monster groups you target on your route, plays its fights itself, then goes back to gathering where it left off.
Gathering and combat on the same sequence, set up the way you want: monster level, group size, bestiary, minimum life, posture.
- 5,000
- combinations per turn, at most
- 560
- cells per map
- 17,231
- known spells
- 5,134
- known monsters
Two ways to run into a monster
Either a monster attacks you on the way, or the bot goes on the attack itself. Choose how it reacts in the first case, and which groups it targets in the second.
- ManualThe bot stops and sends you a notification. You play the fight.
- SurrenderThe bot surrenders the fight, then resumes its route where it left off.
- FightThe bot plays the fight, then resumes its route where it left off.
When the bot attacks
On every map of the sequence, the bot attacks the groups that pass your settings itself.
Choose the groups to attack
Four settings decide which groups the bot attacks. A group that fails any one of them is left alone.
- Monster levelSet the level of the monsters the bot attacks.
- Group sizeSet how many monsters a group may contain.
- BestiaryCheck the monsters the bot may attack.
- Minimum lifeSet the life below which the bot no longer attacks.
Harvest or combat first
The activity priority decides what the bot carries out first on each map.
On a transit map or a disabled map, the bot walks through without gathering or fighting.
Posture and thinking time
Two sliders set how the bot plays all your fights, whether it starts them or a monster attacks you.
- CautiousThe bot stays under cover and strikes without risk.
- BalancedThe bot balances risk and speed.
- OffensiveThe bot goes into melee with the monsters to finish faster.
The posture adapts by itself: below 40% life, the bot turns cautious again; against a weaker group, it goes on the offensive.
- Short
- Turns played without waiting.
- Normal
- The balance between speed and quality.
- Long
- Every move is weighed.
A combat engine, not a spell rotation
Each turn, the bot looks at the fight as it stands and works out the best possible turn by itself.
- No rotation to writeNo spell list to order, no script per class: you never tell the bot what to cast.
- Thousands of turns testedWhere to stand, which spells, in what order, on which target: it simulates its sequences and keeps the one that wins fastest without falling.
- A team, not a lone characterIt places the character and the companion before the fight, then plays each one's turn.
- A turn played in one goThe chosen turn is played without hesitation. If the fight drifts from the plan, the bot recalculates.
To choose who to kill first, the engine applies Smith's rule (W. E. Smith, 1956): first the monsters that deal the most damage for the least remaining life. Its chance of survival comes from a formula checked by Monte Carlo simulation, and a danger map anticipates the enemy turn.
It analyses the 560 cells of the map: range, line of sight, tackle, areas of effect. It plays any class with your character's spells, as well as its controllable summons and the companions fighting alongside it.
Once the fight is over, it closes the end screen and resumes its route on the map where it stopped. Every fight appears in the session log, with its outcome, its duration and what it earned.
What a fight brings in
Every fight is counted in the statistics, next to the harvests.
The Combat and Bestiary views of the statistics break down kamas per hour of combat, profitability by group level and the record of every monster family you faced.
Combat in each plan
Prices are shown when you choose a plan, in the app.
- Defence against an attackYou play your fights
- Monster farming
- Posture and thinking time
- Defence against an attackThe bot plays, then resumes
- Monster farming
- Posture and thinking time
- Defence against an attackThe bot plays, then resumes
- Monster farming
- Posture and thinking time
Before you farm monsters
Automating Dofus breaks Ankama's terms of use, in combat as in gathering. What gets noticed, and what EZGather does to limit it, with no promise.
Frequently asked questions
Which classes does the bot play?
Any class: the bot plays your character's spells, whatever its class.
Does the bot play the companion?
Yes. The bot plays every type of companion fighting alongside your character.
What happens after a defeat?
As in the game, the character is sent back to its saved zaap. The bot then rejoins its route and resumes where it had stopped.
Does the bot attack on a transit map?
No. On the maps linking two zones of your route, the bot walks through without starting a fight. It only fights if it is attacked, according to the reaction set in the sequence.
Does EZGather do dungeons?
No. Monster farming happens in the open world, on the maps of your route.
Where can I see the loot and experience from my fights?
In the app's statistics: the Combat view for the kamas, experience and outcome of each fight, the Bestiary view for the record by monster family.
Does combat change the ban risk?
The framework stays the same. In combat, what gets noticed is a spell sequence replayed identically. EZGather has none: it decides each turn according to the fight. That is one signal less, not a guarantee.
Ban risk, with no promises