Add an account

A bot in Full socket mode signs in to Ankama on its own, so it needs an Ankama account stored in Asterobot. You add it in Account Manager, with or without its password. If your bots only use MITM mode, short for man-in-the-middle, where a bot relays the game you play yourself, you don't need any of this: those bots never use a stored account.

Open Account Manager

In the sidebar, click Account Manager. The page lists your stored accounts, one per row:

Type in Filter... to find an account in a long list. Before you add anything, the table reads "No accounts stored yet."

Add the account

1. Click Add an account. The Add a bot account dialog opens.
2. In Login ID, type the login you use on Ankama's sign-in page. Spaces around it are removed.
3. Fill in Ankama password (optional) only if you want Asterobot to sign this account in by itself. The next section explains the difference.
4. Click Add. It stays greyed out while Login ID is empty.

The account appears in the table as Not signed in. Adding it doesn't contact Ankama at all, so a wrong login or password isn't detected at this point. Sign the account in next, with Automatic sign-in if you stored a password, or Manual sign-in otherwise.

If Asteroboard shows Couldn't add the account, the usual reason is that an account with the same Login ID is already stored. A Login ID can only be stored once.

You don't have to leave the Add a bot dialog to do this. The button next to its Account field opens the same dialog, then the sign-in dialog, and selects the new account for the bot. See Add a bot.

With or without a password

The password is the whole switch for automatic sign-in. There's no other setting to turn it on.

With a password, the account gets the Signs in on its own badge. You can sign it in with one click, and when a bot later needs the account and its sign-in has stopped working, Asterobot signs it in again by itself, through a browser it drives. Asterobot always tries a quiet renewal with Ankama first and only opens that browser when the renewal is refused.

Without a password, the account works exactly the same while its sign-in is valid. The difference shows up when that sign-in stops working and can't be renewed quietly: a person then has to sign it in again, and a bot that tries to connect before that fails.

You can store a password later, or replace it, from the sign-in dialog. See Manual sign-in. Asteroboard can't clear a stored password, though: to turn automatic sign-in off again, remove the account and add it back without one.

What Asterobot keeps, and where

Asterobot saves your accounts in a file called accounts.toml, in its data folder. Files and folders shows where that folder is on each system. For each account, the file holds:

• the Login ID;
• the password, if you stored one;
• the sign-in Ankama gave Asterobot: an access token and a refresh token, with when they were issued and when they expire.

The password is not encrypted. It's written in the file as plain text, because Asterobot has to type it into Ankama's sign-in page. On Linux and macOS, Asterobot restricts the file so only your user account can read or change it, and applies that restriction again every time it starts. On Windows that restriction has no effect. In every case, anyone who can open files as your user, or who gets a copy of the file, can read the password and use the tokens.

Accounts that sign in automatically leave two more things behind:

• A browser profile per account, in the zaapmanager/browser-profiles folder of Asterobot's data folder. It holds the account's Ankama session in the sign-in browser, which is what lets a later sign-in skip Ankama's form. On Linux and macOS, only your user can open it. Treat it like the password.
• A screenshot of the last failed automatic sign-in, in the zaapmanager folder of Asterobot's cache folder. There's one per account, replaced at each new failure. Automatic sign-in explains what it's for.

Asterobot never sends the password back to Asteroboard: all it tells Asteroboard about an account is whether a password is stored and whether the account is signed in.

One bot per account

An Ankama account can belong to one bot only. Dofus allows one game session per account, and Asterobot enforces the same rule: adding a second bot with an account that already has one fails with Couldn't add the bot, and choosing it on a bot's Settings page is refused with this account is already associated with a bot. To run several bots in Full socket mode, store one account for each. See Many bots.

Accounts and MITM mode

A bot in MITM mode never uses a stored account, even when it has one: you sign in yourself, in Dofus, and the bot relays that session. That's why accounts protected by Ankama Shield or two-factor authentication can still be used in MITM mode. See Shield and two-factor authentication.

Where to go next

• Automatic sign-in, if you stored a password.
• Manual sign-in, to sign the account in yourself.
• Add a bot, once the account shows Signed in.