Bot doesn't connect

A Full socket bot, which Asterobot signs in on its own, can get stuck anywhere from Add bot refusing to a bot that shows Connected to game server and still never enters the game. For a bot that waits for your Dofus client, see MITM problems.

Find the reason

When a connection fails, Asteroboard shows Couldn't connect the bot with the reason, and the same reason stays in a Couldn't connect this bot alert under the bot's header, on every tab. Copy puts it on your clipboard. The bot's Console tab narrates each stage of the connection, so its last lines tell you where it stopped.

Two failures come without any reason: Couldn't add the bot, and a bot that disappears from Bot Manager. Their causes are listed below.

Couldn't add the bot

Asterobot refused the new bot, and Asteroboard doesn't say why. The dialog stays open with your choices. The causes:

• The name is already taken by a bot in Bot Manager.
• The account already belongs to another bot. An Ankama account can only belong to one bot.
• Asterobot couldn't confirm your asterobot.net account, for example because it isn't signed in. See this installation is not entitled to start bots.
• Your asterobot.net account's bot limit is reached. Every bot listed in Bot Manager counts, connected or not.

1. Check the account button at the bottom of the sidebar: it should show your asterobot.net name.
2. Check that no bot in Bot Manager has the same name, and that no other bot uses the account.
3. If you have many bots, delete one you no longer use.
4. Click Add bot again.

Add bot stays greyed out

The dialog waits until everything it needs is set, such as a game version that's ready, a signed-in account for Sign in now, which is selected when the dialog opens, or a server for Always this server. Add a bot lists every condition.

Connect is greyed out

• The bot isn't Disconnected. While the bot connects, waits or is connected, the header shows Disconnect instead. Click it first.
• The bot has no Ankama account. The tooltip says "This bot has no Ankama account to sign in with." It can only relay a game you play, in MITM mode. To let it sign in on its own, pick a signed-in account on its Settings tab while it's disconnected.

Bot's game version isn't ready yet

Asteroboard shows Bot's game version isn't ready yet, with "Its game files or extracted data aren't fully ready - check the Game Manager for this version." The reason in the alert is this bot's game version is not ready to connect yet. Asterobot checks this before anything goes out to the network.

1. Open Game Manager and find the bot's version. Its Ready column says Not ready.
2. If files are missing, open the version's menu and click Download more files, with the default filter.
3. Once the download is done, click Extract data in the same menu, and wait for Ready for bot.
4. Click Connect again.

Game download problems helps when the download or the extraction fails.

Reasons a connection fails

this installation is not entitled to start bots

Asterobot couldn't confirm your asterobot.net account. That happens when Asterobot isn't signed in, when it hasn't reached asterobot.net for more than an hour, or when asterobot.net refused it. Asterobot checks this when you add a bot, change a bot's account or game version, click Connect, and when it brings bots back as it starts. Putting a bot in waiting for your Dofus client isn't affected.

1. Look at the account button at the bottom of the sidebar. If it doesn't show your asterobot.net name, sign in as Sign in with asterobot.net explains.
2. Make sure the computer where Asterobot runs can reach asterobot.net, and check https://status.asterobot.net.
3. Click Connect again.
4. If it keeps happening while Asterobot is signed in and online, ask on the forum at https://asterobot.net/forums/ or on Discord at https://discord.asterobot.net.

this account's bot limit has been reached

You already have as many bots as your asterobot.net account allows. Every bot in Bot Manager counts, disconnected ones included. Delete a bot you don't use any more, then try again. If the count looks wrong to you, ask on the forum or on Discord.

ankama account authorization required

The bot's Ankama account no longer has a working sign-in, and Asterobot couldn't renew it: Ankama refused the quiet renewal, and the account either has no stored password or its automatic sign-in failed.

1. Open Account Manager and click Reconnect in the account's menu.
2. Sign the account in. Sign-in problems helps if that fails.
3. Click Connect on the bot again.

account not found

The bot's account was removed from Account Manager. The reason is followed by the Login ID.

• Add the account again with the same Login ID and sign it in, then click Connect.
• Or pick another signed-in account on the bot's Settings tab, while the bot is disconnected.

identification was refused: account already connected elsewhere

The account is already in the game: in Dofus, or through another bot, including a bot that relays your Dofus in MITM mode.

1. Close the other session: quit Dofus, or disconnect the other bot.
2. Wait a moment, then click Connect again.

When the reason reads identification was refused: followed by something else, that's Ankama's own reason for refusing the account. Accounts protected by Ankama Shield or two-factor authentication can end here: see Shield and two-factor authentication.

connect to login server: timed out waiting for a response

The game's login server didn't answer within 30 seconds. Check the internet connection of the computer where Asterobot runs, and whether the game servers are in maintenance, then try again.

server selection was refused:

The login server refused the server the bot picked, with its own reason after the colon. Try again later, or set Server selection to Ask me each time on the bot's Settings tab and pick another server.

connect bot to game server:

The login stage worked, but the bot couldn't open its connection to the game server it was sent to. Check the internet connection and the firewall of the computer where Asterobot runs, then click Disconnect and Connect again.

a connection attempt is already in progress

A bot runs one connection attempt at a time, and a second one arrived, usually from another open Asteroboard tab. Wait for the first attempt to end, or click Disconnect and start again from a single tab.

bot must be disconnected before starting a new login connection and this bot is relaying a session: stop it before signing in on its own are the same kind of refusal: the bot is already connected, or waiting for your game client. Click Disconnect first.

After a Dofus update

Right after an Ankama patch, a bot on the new version may not connect until your release of Asterobot supports it. When Dofus updates lists what you may see, including a reason that tells you to update Asterobot.

Stuck on Connecting…

• An automatic Ankama sign-in is running. When the account's sign-in stopped working and a password is stored, Asterobot signs in again through the browser, which can take up to two minutes.
• Another account is signing in. Ankama sign-ins happen one at a time across all your accounts, so a bot waits for the one before it.
• The login server is slow. Each exchange with it has a 30-second limit, after which the connection fails with a reason.

To give up, click Disconnect: it cancels the attempt at any stage.

Stuck on Awaiting your answer

The bot waits for you to pick a server in the Pick a server card, under its header. It asks when its Server selection is Ask me each time, when the server chosen with Always this server is offline or not open to the account, and when no server at all is online and open to the account. Asterobot sets no time limit on the question.

1. Open the bot's page. A notification such as Bot "my-bot" needs your input has a Go to bot button that opens it.
2. Click a server that isn't greyed out.

If Asteroboard shows Couldn't send your answer, the server may have gone offline in the meantime: pick another one, or click Disconnect, then Connect. See Full socket mode.

Connected to game server, but the bot never enters the game

This is the most common surprise in Full socket mode. Connected to game server means the connection to the game server is open, nothing more. Asterobot doesn't identify the bot on the game server and doesn't pick a character: a connection script, a package the bot plays, has to do that. The status reads the same whether the script did its job or not.

Go through these checks:

1. Is a script running? The header shows the package and Stop while it runs, and the Behavior column of Bot Manager says Running. With No package selected, or Play still showing, nothing identifies the bot: load a connection script and click Play. See Run a package.
2. Is the package a connection script? A package made for something else, such as logging the chat, doesn't identify the bot. Neither does the starter code New package creates.
3. What does the bot's Console say? The script's own lines tell you how the identification went.
4. Did the script stop? A The behavior stopped with an error alert under the header gives the error. With IdentificationRequest.token: unknown protobuf field, the script was copied from an old example that sends token and lang: it needs the identification block of Identify and run. If you didn't write the package, ask its author for an update. Package errors covers the other errors.

The status goes back to Connected to login server

The bot's game connection closed. The console shows Game connection lost, and the status stays on Connected to login server instead of Disconnected. A running script stops, with The behavior stopped with an error and a message that mentions Game session closed.

Nothing reconnects by itself:

1. Click Disconnect.
2. Click Connect, and wait for Connected to game server.
3. Click Play.

If the connection drops again right after Play, read the script's lines in the bot's console to see what it sent.

A bot disappeared from Bot Manager

• After Asterobot started. Asterobot skipped the bot, because its Ankama account or its game version is missing, because it couldn't prepare Ankama sign-ins, or because it couldn't confirm your asterobot.net account in its first seconds. In that last case, every bot is skipped. The terminal shows a warning starting with skipping bot restore:, with the reason. The bot's configuration is kept: fix the cause and restart Asterobot. See Disconnect, delete and restart.
• Right after you saved its settings. When Asterobot refuses a new account or game version, for example with this account is already associated with a bot, or can't confirm your asterobot.net account at that moment, the bot disappears until Asterobot restarts, and comes back with its previous settings. See Bot settings.

Couldn't save the settings

Asteroboard shows the reason under Couldn't save the settings. The ones you'll meet most are this account is already associated with a bot, when another bot uses the account you picked, and this installation is not entitled to start bots, covered above. Bot settings lists when Save settings stays greyed out.

Where to go next

• States and controls
• Full socket mode
• Package errors