Every account in Account Manager shows badges for its state and has a menu of actions. A Signed in badge only means Asterobot holds the account's sign-in, not that Ankama still accepts it.
Status badges
| Badge | Meaning |
|---|---|
| Signed in | Asterobot holds a sign-in for this account, received from Ankama. |
| Not signed in | Asterobot holds no sign-in for the account. Sign it in before you use it for a bot. |
| Signs in on its own | A password is stored. Asterobot signs the account in again by itself when it needs to. |
What "Signed in" really means
Signed in only says that Asterobot has the account's tokens. Asterobot doesn't watch for them to expire, and Ankama can end them at any time, so an account can show Signed in long after its sign-in stopped working.
Two things find out for sure. Verify asks Ankama right away. And every time a bot connects with the account, Asterobot uses the sign-in for real: when it has stopped working, Asterobot renews it quietly if Ankama accepts, signs in again through the browser for an account with a stored password, and otherwise the bot's connection fails with a message that contains ankama account authorization required.
The Sign in now option of the Add a bot dialog only accepts an account that shows Signed in.
Actions
Open an account's menu with the three dots at the end of its row.
| Action | Available | What it does |
|---|---|---|
| Sign in automatically | Only when a password is stored | Signs the account in through Asterobot's browser, in one click. See Automatic sign-in. |
| Connect | For an account that isn't signed in | Opens the sign-in dialog. See Manual sign-in. |
| Reconnect | For an account that's signed in | Opens the same dialog. The account keeps its current sign-in until the new one works. |
| Verify | For a signed-in account | Checks the sign-in with Ankama right now. |
| Force refresh token | For a signed-in account | Renews the sign-in with Ankama straight away, even if it still works. |
| Disconnect | For a signed-in account | Revokes the sign-in and forgets its tokens. |
| Remove | Always | Deletes the account from Asterobot. |
Verify
Asks Ankama whether the account's sign-in works right now. When it does, Asteroboard shows Verified as followed by the account's Ankama nickname.
When the sign-in has stopped working, Verify repairs it first, the same way a connecting bot would: a quiet renewal, then a browser sign-in for an account with a stored password. If nothing works, Asteroboard shows Verification failed - try reconnecting. Use Reconnect then.
Verify connects nothing to the game.
Force refresh token
Trades the account's refresh token with Ankama for a new one, right away, whether the sign-in still works or not. Asterobot already does this on its own when a sign-in stops working, so you'll rarely need it. It's there for testing, or to replace a sign-in you'd rather not keep.
On success, Asteroboard shows Token refreshed. When Ankama refuses the refresh token, or there isn't one, it shows Couldn't refresh the token - try reconnecting, and only a new sign-in helps. Unlike Verify, this action never falls back to the browser.
Disconnect
Asks Ankama to revoke the account's sign-in, then forgets the tokens in Asterobot. The tokens are forgotten even when Ankama refuses or doesn't answer the revocation: Asteroboard shows Account disconnected and the badge turns to Not signed in either way.
Two things stay as they were:
- Bots aren't touched. Asterobot doesn't disconnect a bot that is connected with this account.
- The stored password is kept. An account with Signs in on its own signs itself in again the next time a bot connects with it. To prevent that, remove the account.
If Asteroboard shows Couldn't disconnect the account, nothing changed and the account is still signed in. Asterobot couldn't reach Ankama to prepare the request, or couldn't save its account file.
Remove
- Click Remove. The Remove this account? dialog opens.
- Click Yes, remove.
Asterobot deletes the account from accounts.toml, with its password and tokens. It doesn't revoke anything with Ankama first: click Disconnect before Remove if you want that. The account's browser profile and its last failure screenshot stay in Asterobot's folders. If removing fails, Asteroboard shows Couldn't remove the account.
Removing an account doesn't delete the bots that use it, but it changes what they can do:
- A bot already connected with the account stays connected, and a bot waiting for your game client keeps waiting. Neither needs the stored account for that.
- The next time you click Connect on such a bot, the connection fails with
account not found: LoginIDfollowed by the Login ID. - The bot's Settings can't be saved until you choose another signed-in account for it.
- When Asterobot next starts, the bot isn't brought back and disappears from Bot Manager. Its configuration stays saved, and the bot returns at a later start once the account exists again. See Disconnect, delete and restart.
Adding the account again with the same Login ID, and signing it in, undoes all of this.
Where to go next
- Add a bot with a signed-in account.
- Full socket mode, to see how a bot uses the account.
- Sign-in problems, when an account won't stay signed in.