Frequently Asked Questions about EZGather

In the configuration of a sequence or a circuit, the Combat row of the Activities block holds four filters: Monster level (every monster in the group must be within the range), Group size, Bestiary (a group is only attacked if all of its monsters are checked) and Minimum life (the bot only attacks above this life level).

A group is only attacked if it passes all four.

The posture sets how the bot plays: Cautious (it takes cover and fears defeat more), Balanced (a compromise between the risk taken and the speed of the fight, the default) or Offensive (it goes into melee and finishes its turns faster). Adapts itself makes it cautious below 40% life and offensive against a much weaker group.

The thinking time (Short, Normal, Long) balances fight speed against decision quality.

Both settings are found in the Combat row of the Activities block and apply to all your fights, the ones the bot starts as well as the ones where a monster attacks you.

That is the Activity priority, at the top of the Activities block: Harvest (the default: the bot harvests the map, then attacks the groups) or Combat (it attacks the groups, then harvests).

On a transit map, between two zones of the route, the bot starts no fight.

The bot only attacks a group above this life level: 50% by default, in steps of 10%. It keeps the bot from chaining fights with a character who is already worn down.

In the app's statistics: the Combat view (kamas per hour of combat, experience earned, wins and defeats, profitability by group level) and the Bestiary view (the record of every monster family you faced). The loot is estimated at your server's average price.

No. Monster farming happens in the open world, on the maps of your route.

The Aggression handling setting, in the options of the sequence or the circuit, has three positions.

Fight: the bot plays the fight itself, then resumes its route from the current map.

Surrender: as soon as a fight is detected, the bot clicks Surrender to leave it as quickly as possible. After a victory, it resumes gathering from the current map; after a defeat (teleport to the saved zaap), it resumes exactly where it was interrupted.

Manual: the bot pauses and shows a notification with a Continue / Finish dialog. Click Continue to resume gathering.

Attacking monsters on its own initiative is set separately: the Combat row of the Activities block (switch, monster level, group size, bestiary to exclude) makes monster farming an activity of the route, just like gathering.

Five conditions are required:

Any interference disrupts the way the bot works.

Two paths, depending on the platform:

Installation does not require administrator rights. On Windows, however, an authorization prompt (UAC) appears every time the application is launched — accept it to start.

On first launch, the application downloads the components it is missing: a loading screen shows the progress, and access opens once the download is complete.

Allow a few minutes depending on your connection. Later launches start directly, even offline, as long as the application version does not change.

The home screen is there to sign you in: the Continue with Discord and Continue with Google buttons open browser-based sign-in, and a QR code lets you sign in from your phone. As soon as sign-in succeeds, the application opens on the world map.

Two methods are available:

The QR code regenerates every 4 minutes. Both methods create a free EZGather account if you do not have one yet.

Four permissions are requested, and can be granted with one click on Allow from the welcome dialog or from Settings → Permissions:

A fifth one, Automation, is requested natively by macOS as soon as the world map opens (a second prompt may follow for Dofus). Without Network capture, the bot sees neither the position, nor the fights, nor the inventory. Without Screen Recording or Accessibility, it crashes as soon as it tries to use the refused capability. Without notifications, only the alerts are turned off.

Two buttons, offered in the welcome window on first start and then available in Settings → General, Recommended configuration section:

If you launch a sequence or a circuit without having applied either of the two, a window offers Apply first (configure then launch) or Launch anyway.

No: once the Recommended configuration has been applied, everything is ready to launch a first sequence.

The Settings tab then lets you customize things if needed:

By default, four movement keys: Z (up), S (down), Q (left) and D (right) on an AZERTY keyboard, that is W, S, A and D on a QWERTY keyboard — they are the same keys, only their name changes. The Recommended configuration replaces them with the ç, ), = and : keys of a French AZERTY keyboard (9, -, = and . on a US QWERTY keyboard).

The keyboard layout is detected automatically: in Settings → General → Navigation, each key shows the name it has on your keyboard. These keys are synced to Dofus as soon as you click the Settings button of the Recommended configuration for the first time; any later change propagates automatically, with no extra action.

EZGather detects new versions automatically. A mandatory update shows a blocking window, with no close button, until it is installed. An available update stays closable and can be postponed for four hours, through a window with a close button or a floating panel in the sidebar.

The download and the installation only start on an explicit click (the Install button or the floating panel); the application restarts automatically once it is done.

A sequence is a predefined route of maps that the bot follows in a loop to gather and fight: each map carries a movement direction and, if needed, a gathering action, and the route always comes back to its starting point.

It is the basic building block of automation in EZGather: the bot moves forward map after map, returns to the start, then starts over.

The world map opens right after sign-in: it shows every sequence, across all professions. The navigation panel, on the left, lets you switch between Sequences mode and Circuits mode.

A circuit chains several sequences in a defined order — see the “Circuits” section for how it works.

Two equivalent keyboard shortcuts scroll through the sequences or the circuits displayed on the world map, one by one, in catalog order:

Clicking a catalog block directly, on the right, selects a specific sequence or circuit in the same way.

The Filter button, to the right of the catalog's search field, opens a panel with two groups: Professions (Miner, Lumberjack, Alchemist, Fisherman, Farmer) and Fauna (the game's monster families). Tick a box to keep only the matching routes; on the map, sequences outside the filter stay visible, simply grayed out. Both groups filter at the same time, and nothing ticked means no filter.

On the map, Ctrl reveals resources and Shift reveals monsters, following the filter.

This filter is purely visual, to spot an area you are interested in. Which resources are actually gathered is set separately, with per-sequence, per-circuit or global granularity.

A marker — a blue silhouette with a pulsing halo at its feet — shows your character's position live, on every map view. It moves at each map change, with a slight delay.

It appears as soon as the game is open and no sequence or circuit is running; a run hides it until the next map change. When your position moves out of the visible area, a bubble slides along the edge with a chevron: click it to recenter the map.

A reference sequence is a sequence shipped with the application, calibrated and maintained by the team: EZGather provides 41 of them, on a selection of key mines and caves of the World of Twelve.

A padlock to the right of the title marks it out: it can be viewed, used and added to a circuit, but stays read-only in the library — a guarantee of quality. Your own sequences remain editable and deletable, through the dedicated route editor (Free draw and Areas modes), for every profession.

The route editor, opened on the world map, offers two modes that can be combined:

The route always forms a loop that comes back to its starting point; Save stores it. For a personal sequence, the … menu of the configuration panel offers Edit sequence and Delete (with a confirmation step). A reference sequence shows a padlock instead.

Click a sequence's marker on the world map to open its configuration — or its block in the catalog on the right rail, or from an Advanced search result.

The Activities block holds two rows, each with its own switch: Gathering (choice of resources) and Combat (posture, thinking time and monster farming: level, group size, bestiary to exclude). You disable maps with one click on their tile (or on their row in the Maps covered list), and set the session options: loop, automatic pauses, session length, inventory handling and aggression handling.

Right-click a tile of the route, on the map, to switch that map to transit; a left click re-enables it. A disabled map is covered by a dark veil.

The bot still crosses it to reach the following maps, without gathering or starting a fight there. If the route only made a detour to it, the bot no longer goes there; on the way to an active map, it crosses it in transit.

This action is unavailable during a run or on a locked reference sequence.

In the sequence configuration, Activities block, set the Exploration mode to Camping, then click the map where the bot should stay. It goes there, harvests, and waits for the respawn instead of travelling through the rest of the sequence.

Clicking another map moves the camp, a right click on the camp map removes it. A sequence with a single map always runs in Camping.

Camping mode does not apply to a sequence launched inside a circuit.

Four methods launch a sequence:

The run screen then appears with real-time statistics — same principle for a circuit.

The Advanced search, reachable from the left sidebar or from the catalog's magnifier (Sequences or Circuits view), finds a sequence or a circuit by name, by profession and resource subtype, or by gathering level range. The scope (Sequences, Circuits, or both) can be changed at any time.

Results are ranked by match strength (Strong, Medium, Weak), and each card offers a quick launch, its configuration and its statistics, directly from there.

A circuit is an automated route that chains several sequences, automatically linked by transports, in a defined order.

It is made up of four block types:

A single global configuration drives the whole circuit: activities (resources gathered, monsters farmed), inventory handling, aggression handling and automatic pauses. The bot repeats the circuit in a loop until the run is stopped.

Click New circuit to open the editor; from an existing circuit, the “…” menu in the header (Edit circuit) does the same.

Add a block from the Add a step accordion in the right rail (Diagram tab), or click an element directly in the Map tab: a sequence or a bank in one click, a zaap or a transporter in two clicks (departure, then arrival). Reorder the blocks by drag and drop or with the reordering arrows.

Once the composition is ready and the loop is closed, click Save.

A circuit is made up of four block types:

The transport block is inserted automatically between two sequences, but it can also be added or reconfigured manually, just like the bank deposit and the pause.

The choice is made in two steps, in the transport block panel of the circuit editor:

The panel offers a filter by transport type (zaaps, boats, brigandins), a “Recommended” badge to the right of each destination and its cost in kamas. This setting is independent of the transport profile (Fast, Balanced, Economical), which applies to the transports calculated automatically between sequences.

The Map tab is the default view of the circuit editor, even for an empty circuit: it shows the routes of the sequences on the world map, linked by blue connections.

The Diagram tab shows the composition as blocks lined up in execution order, each type on its own row (sequences, transports, deposits, pauses).

Add a block from the Add a step accordion in the right rail, or by clicking an element directly in the Map tab (sequence, bank, zaap, transporter).

Click the circuit's marker (map, right-rail catalog or advanced search) to open its settings, split into two sections: Activities (Gathering and Combat rows, each with its own switch — resources to gather and monsters to farm, pooled across all member sequences; posture and thinking time) and Options (infinite loop, automatic pauses, session length, inventory handling, aggression handling).

A Scheduling button in the toolbar sets up weekly time slots.

The “…” menu in the header groups together Edit circuit, Reset settings and Delete.

Click the sequence's marker, from the circuit configuration view, to open its configuration — clicking again closes it. It uses the same layout as a standalone sequence, with the resources read-only (set at circuit level) and only the route of the open sequence still active.

Three settings remain specific to this member:

A Reset button restores this member to its default values.

That is normal. A sequence embedded in a circuit keeps the same layout as in standalone mode, but some settings come under the circuit's control: the choice of resources to gather and the transport strategy are set at circuit level, hence the resources shown as read-only.

Only Repetitions, Pauses and Maps covered remain specific to the member sequence, as detailed in the previous question.

The optimized path follows the sequence's route: it removes detours to disabled maps and crosses the others without gathering or engaging in combat there (transit mode), never taking a passage that is not on the route — details in section 3.

On a circuit, the “Automatic transports” switch calculates the trips between sequences, adjustable through a seven-position slider between Fast (paid zaaps and transporters), Balanced and Economical (on foot).

Yes, if the “Smart zaap save” toggle (switch) is enabled: before each sequence, the bot automatically saves the nearest zaap as the respawn point, so that if the character dies in combat it respawns as close as possible to its route.

This setting is found in the sequence options and in the circuit's global options.

With the toggle disabled, the respawn point stays the one saved manually.

Scheduling automatically programs the launch of your circuits and sequences across the week, from the Scheduler view: a rail of entities on the left, a weekly calendar on the right.

There is no limit on the number of slots per day. Once a slot is reached, the bot starts and stops on its own; a scheduling banner with a countdown stays visible at the top.

Drag an entity from the rail onto a calendar cell, or click the add button on its card, to create a slot (2 hours by default, adjustable in 15-minute steps).

Drag it to another day or another time to move it; pull its handles up or down to adjust its length.

To delete it, select it then click the trash icon in the action bar or press Delete — a confirmation appears if the session is running.

One minute before the launch (thirty seconds for a resume), the application comes back to the foreground with an alert window: a countdown, a Cancel this slot button and a Postpone by X min button.

With no response, the slot starts normally when the countdown expires and the application switches to the session tracking panel, with a Scheduled badge next to the name.

No, not entirely.

As long as scheduling is active and the application is open, a sleep blocker prevents the machine from sleeping through inactivity. On a laptop, it also keeps the machine awake with the lid closed (on a Mac, once you grant permission with your administrator password). A critical battery level will still put the machine to sleep, and a locked screen (automatic locking, password-protected screen saver) prevents the bot from acting: in both cases the missed slot is reported in the Log.

Turn off automatic locking and the screen saver in your system settings for reliable scheduling.

The run overlay opens automatically on top of the map when a sequence or a circuit is launched.

It shows six live indicators: gathers per hour, loops, fights, deposits, total cost in kamas and total time. A ring segmented by profession shows the resources gathered; other sections (Gathering pressure, Timeline, Efficiency, and Gathering per sequence for a circuit) fill in progressively over the course of the session.

Three means of travel, tried in this order:

Zaap or transporter trips cost kamas, counted in the overlay's total cost.

The character walks to each available resource and harvests it automatically with Shift+click, in order of proximity.

A map with no resource at all is crossed without stopping. With mouse navigation, the map exit is pre-clicked during gathering, to move on to the next map with no dead time.

Automatic mode (default): as soon as fewer than 50 pods are left, the bot interrupts its route, travels to the nearest bank, deposits everything, then resumes it exactly where it left off.

Manual mode: the bot goes into pause and shows a Continue / Finish dialog. Once the deposit has been made by hand, click Continue to resume.

Five sources:

• ●manual pause (sequence, between two sequences of a circuit, or navigation)
• ●combat/inventory interruption in manual mode
• ●periodic pause
• ●waiting for a scheduled slot
• ●loss of focus on Dofus

Resuming:

• ●manual pauses through Resume (or F8)
• ●periodic pause at the end of the countdown or through that same button
• ●interruption through Continue / Finish
• ●slot at the next scheduled time
• ●loss of focus, on its own after one minute, or through Resume / Keep paused

The bot briefly opens the haven bag at the start of each navigation sequence to confirm its position, then closes it again right away before resuming.

If navigation gets stuck repeatedly, it attempts an emergency teleport by typing the /zaap command in the game chat, to a known zaap close to the route — limited in number of uses and charged in kamas. If it fails or is not possible, the bot restarts the game.

The bot automatically closes any popup (small pop-up window — an announcement, an invitation) that appears on top of the game, checked at every step of the route, during long trips and map changes.

After a route incident, a blocking popup is dismissed before resuming. Windows opened by the bot itself (bank, zaap, transporter, combat, disconnection) stay handled by the operation in progress.

On reconnection, a window that takes over the login screen is confirmed automatically; if it persists, the bot fully restarts the game.

A dedicated crash screen replaces the whole display — the same scenery and EZGather mascot as the loading screen, in a “broken down” version.

Two actions: Reload the application, or Report the problem. The technical details are never displayed; they go out with the report if you click.

No session data (gathers, fights, settings, history) is transmitted; a minimal, anonymous technical signal is sent automatically for stability monitoring, and the error is written to the Log in any case.

Yes: turn on the Automatic reply switch in the sequence or circuit options.

The bot reads the private messages it receives and prepares an AI-generated reply, short and in the tone of the person writing, sent at the next map change or before a bank stop, with human-like typing.

A given player receives at most 8 replies per session. After three consecutive generation failures, the bot falls back to predefined phrases for the rest of the session.

Open the Statistics view from the dedicated button of a sequence or a circuit, also reachable from the world map catalog or from the advanced search.

The left column lists the sessions; the right panel shows the Global view by default: key indicators (gathers/hour, fights, deposits, cost, time), then the Resources, Gathering pressure, Efficiency per session and Route summary sections.

Click a session to show its details in the same place.

Click a session in the list to show its details in the right panel: header (name, status, date, length), then six indicators (gathers per hour, loops, fights, deposits, cost, total time).

Then come the Timeline of events, the Resources of the session, the Gathering pressure (with a Per map ranking), the Gathering per sequence and the Efficiency per loop.

To go back to the Global view, click the selected session again, use the Global view / Session toggle, or press Esc.

While a sequence or a circuit is running, a run overlay opens on top of the map and reuses the sections of a session's details: indicators, Resources, Gathering pressure, Timeline, Gathering per sequence and Efficiency, fed live in the same format as a past session.

An activity header shows the current block, the character's position and the loop number. The time and the gathering rate update second by second; when paused, the time shows a countdown and freezes.

The Log is the global history of the application's events:

Open it from the Log entry in the sidebar. Events are shown on a timeline grouped by day, the most recent first, with a filter rail on the left (period, severity, category, keywords). There are six categories, checked by default except System.

Each event shows its severity with a gray, amber or red dot; on the sidebar side, a red dot flags the ones not yet read. History kept for 90 days.

EZ Remote is EZGather's remote: an app that drives EZGather on your machine when you're not in front of it.

You pick a route on the map, start the session, follow it live, then pause, resume or stop it. Your statistics and the machine's Journal can be viewed there too.

It is designed for a phone and also works on a tablet. It opens in a computer's browser as well, with a layout made for a small screen.

In Settings, Remote control tab, turn on Enable remote control. The remote is off by default and is turned on machine by machine.

The switch stays greyed out until the machine is ready: a system permission is missing, Dofus's Recommended configuration has never been applied, or a mandatory update is waiting. A Remote control unavailable banner says what is missing.

On the machine, click Pair a device. Two methods:

The code and the QR code are valid for 5 minutes. Generate a new code gives you another one.

EZ Remote opens right in the browser. To have it on your home screen, choose Add to Home Screen in the browser's share menu: it then opens full screen, like an app.

On iPhone and iPad, the app added to the home screen keeps its own data, separate from Safari: pair it by entering the code from the installed app.

The remote brings together everything you need to follow and drive a session. Four areas:

The machine's warnings (fight, full inventory, maintenance…) also show on the remote.

The session starts on the machine with no window to confirm in front of the screen, like a scheduled session.

Your route settings are used, except for anything that would wait for you: the game opens and logs your character in (a Dofus already open with other settings is closed and restarted), a full inventory goes to the bank, and an aggression set to "Manual" is fought. Your saved settings stay as they are.

Yes. A phone or tablet can be paired with ten machines: it opens on their list, with the status of each. A machine accepts five devices.

Yes, in Settings → Remote control → Usage limits, on the machine. Three switches, on by default:

These limits apply to every device paired with the machine.

The machine must be on, connected to the Internet, with EZGather open and Enable remote control turned on. In Settings, the indicator next to the switch should read Machine reachable.

If a system permission was removed, the switch turns itself off: the Remote control unavailable banner says what to restore.

From the machine: Settings → Remote control → Paired devices, Remove button. From the device: Options tab, Unpair this machine.

Turning off the machine's switch simply disconnects it: the devices stay paired and find it again as soon as it is back on.

Four quotas compare the Free, Essential and Ultimate plans:

The Essential plan adds resource filtering, map disabling, Camping mode, transport between sequences, circuit creation and the automations (bank, fights played or surrendered when a monster attacks you, with a Balanced posture and Short thinking, pauses, connection). The Ultimate plan adds advanced transport, scheduling, Zaap saving, Automatic reply, monster farming and the combat settings (posture, thinking time), which apply to all fights.

Support answers according to plan: no guaranteed response time, within 48 hours, or within 24 hours with priority.

No: using EZGather only requires an account (sign-in through Discord or Google) — no payment details are required.

The Usage tab of Settings shows your statistics (sessions launched, play time, gathers, average rate) and your current quotas — sequences and circuits created, play time left before the daily reset.

An exceeded quota turns its gauge amber and adds a warning dot.

Three mechanisms, depending on the quota exceeded:

The License and Plan tab of Settings lists your connected devices against your plan's quota.

A device takes a slot when it starts a session and gives it back when the session stops: beyond the limit, starting is refused while a session is running elsewhere. Stopping the session on the other device is enough to free its slot.

Manage your subscription from the plan management page of the website, reachable from the License and Plan tab of Settings (“Change subscription” button).

A cancellation takes effect at the end of the current period; access stays active until then, and then your account goes back to no subscription.

No refund is granted: since access is provided immediately after payment, you waive your right of withdrawal when you subscribe (see the Terms of Sale). Cancelling is the way to stop the charges. A goodwill gesture remains possible in exceptional cases — double billing, a charge after cancellation, an extended service outage — by writing to [email protected].

Join the EZGather Discord server: the AI assistant in the #faq-bot channel answers instantly, the /ticket command opens a categorized ticket, and #bugs-report is there to report a bug. For billing or account matters, write to [email protected].

Yes. With a SOCKS5 or HTTP proxy, the bot follows the game just as it does on a direct connection, on Windows and macOS.

There is nothing to set up in the application.

To keep your accounts apart. Ankama sees the IP address of every connection and can link accounts that share the same address: a sanction on one can then spread to the others. With a proxy, the account that uses the bot connects from an address different from that of your main account.

Two limits to be aware of: Ankama's Terms of Use forbid proxies and VPNs, and a proxy does not make the bot undetectable. Prefer an address reserved for your account: a shared address exposes you to the sanctions of the other players who use it.

The proxy is set up outside EZGather, with a tool such as Proxifier.

Create a rule that sends Dofus and the Ankama Launcher to your proxy, and leave the rest of the computer on a direct connection. Then start your session as usual.

SOCKS5 proxies and HTTP proxies (the latter called “HTTPS” in Proxifier), with or without credentials.

With a proxy reached over an encrypted link, or over IPv6 on macOS, the bot also works, but it follows the game on screen, more slowly.

Ankama refuses the addresses it recognizes as hidden: those of VPNs and data centers and, from our tests, those located in a country other than yours. The connection then fails with a message saying that your IP address is hidden.

EZGather cannot do anything about it: you need an address located in your country that Ankama does not recognize as a proxy.

EZGather never asks you for them: they stay in your proxy tool.

They appear neither in the logs nor in the bug reports.

Yes: EZGather writes Dofus configuration files.

In Settings → General, Recommended configuration section (also reachable from the welcome window on first sign-in), the Settings button applies the standard Dofus preset and pushes the keyboard shortcuts; the Interface button writes the Farm and Combat layouts to every detected Dofus account, in a single click for all characters.

These writes are only triggered by a click on one of the two buttons.

The honest answer: a risk exists.

The Dofus Terms of Use forbid bots, and a ban is technically possible. EZGather limits that risk by never touching the Dofus process: it simulates clicks and key presses like a player, without sending or modifying any game packet.

Recommendation: if you are not ready to accept this residual risk, do not use the bot on your main account.

Nine tips for reducing the risks:

Yes, your Dofus account stays private.

EZGather transmits only the data needed for your license, your settings, your personal sequences and your circuits, synced to the cloud so that they stay available on all your devices. No game data is transmitted — no position, no inventory, no fights.

Two exceptions, on a deliberate action from you: the private messages received in the game if you turn on Automatic reply, and the technical logs attached to a bug report you send.

No. Your machine stays unreachable from the Internet, and only the devices you have paired can control it.

A code typed by hand must be authorized on the machine, and the Paired devices list shows each device, where it connected from and its last connection.