Aller au contenu
Afficher dans l'application

Une meilleure façon de naviguer. En savoir plus.

Asterobot

Une application plein écran sur votre écran d'accueil avec notifications push, badges et plus encore.

Pour installer cette application sur iOS et iPadOS
  1. Appuyez sur Icône de partage dans Safari
  2. Faites défiler le menu et appuyez sur Ajouter à l'écran d'accueil.
  3. Appuyez sur Ajouter dans le coin supérieur droit.
Pour installer cette application sur Android
  1. Appuyez sur le menu à trois points (⋮) dans le coin supérieur droit du navigateur.
  2. Appuyez sur Ajouter à l'écran d'accueil ou Installer l'application.
  3. Confirmez en appuyant sur Installer.

Reset and start over

When something is broken and nothing else helps, a reset puts part of Asterobot or Asteroboard back in a clean state. Every reset deletes something for good, so start with the smallest one that can fix your problem. The resets below go from the lightest to the most drastic.

Choose a reset

Problem Reset Section
Asteroboard shows an old version, or behaves oddly after an update Reset offline data Reset offline data
Asteroboard's language, colors or layout are wrong Reset preferences Reset preferences
A setting you changed broke something That setting's reset, or Reset all Asterobot's settings
Asterobot won't start because of a setting Edit config.toml, or run config reset Asterobot won't start because of a setting
One game version is broken, or the disk is full Verify files, Re-extract data, Uninstall, Delete or Remove all chunks Game versions
Every game version at once cache reset cache reset
One bot, account or package is broken, or Asterobot uses the wrong asterobot.net account Remove that one thing One thing at a time
Everything, as on a new computer Delete Asterobot's folders Start completely over

In your browser

Asteroboard keeps a few things in each browser you use it in. Both of these buttons are on Preferences, in the Danger zone section, and neither touches Asterobot: your bots, accounts, packages and settings stay as they are. Your browser asks you to confirm each one, then the page reloads.

Reset offline data

Deletes the copy of Asteroboard your browser keeps to open quickly and to work offline, then downloads Asteroboard again, which needs an internet connection.

  1. Click Reset offline data.
  2. Confirm "This clears all offline data cached by Asteroboard and reloads the page. Continue?"

It keeps your preferences and your Server URL. The button is greyed out when your browser can't run Asteroboard offline at all. If the reset fails, Asteroboard shows Couldn't reset offline data, with "Try again, or clear this site's data from your browser's settings."

Reset preferences

Puts Asteroboard's language, color mode, colors, radius and sidebar layout back to their defaults, and the language of game texts on the Game page back to following Asteroboard's language.

  1. Click Reset preferences.
  2. Confirm "This resets language, appearance and dashboard layout preferences back to their defaults and reloads the page. Continue?"

It keeps the Server URL, the level buttons of Server > Console, and a few other choices such as the world map layers and the music volume. Preferences compares the two buttons.

To remove everything Asteroboard stored in a browser, the Server URL included, clear the site data of asteroboard.asterobot.net in that browser's settings. Afterwards, open Asterobot's own address, http://127.0.0.1:8080 by default, to set the Server URL again.

Asterobot's settings

On Server > Config, you can reset one setting with Reset to default at the end of its row, one group with the button in its card's header, or every setting you changed with Reset all, which asks Reset every modified setting? first. A reset puts the default back and removes the value from config.toml. Settings marked Restart required take their default at the next start.

Warning

Once Asterobot is signed in to asterobot.net, its sign-in is a modified setting, website.token. Reset all, or resetting the website group, signs Asterobot out, and you'll have to confirm a new sign-in code.

Your bots, Ankama accounts, packages and game versions are kept. The Config page explains each button.

Asterobot won't start because of a setting

When a setting keeps Asterobot from starting, such as a server.listenAddress it can't listen on, Asteroboard can't reach it to change anything. Fix config.toml instead:

  1. Open config.toml with a text editor. Files and folders shows where it is.
  2. Remove the line of the setting that causes the problem. A setting without a line takes its default.
  3. Save the file and start Asterobot.

If you don't know which setting it is, use config reset.

config reset

config reset empties config.toml and puts every setting back to its default.

  1. Stop Asterobot, if it runs.

  2. Open a terminal in the folder where you put Asterobot and run:

    ./asterobot config reset

    On Windows, in PowerShell:

    .\asterobot.exe config reset

    If you start Asterobot with --config-dir or ASTEROBOT_CONFIG_DIR, give the command the same folder.

  3. When it asks Put every setting back to its default value? [y/N], type y and press Enter.

  4. It prints Resetting the configuration.. then All configuration settings have been reset to their default values.

  5. Start Asterobot, and confirm the asterobot.net sign-in code it asks for.

Any other answer to the question stops the command, and nothing changes.

It deletes It keeps
Every setting you changed Your bots
The asterobot.net sign-in Your Ankama accounts and their sign-ins
server.listenAddress, server.basicAuth and server.tls, which go back to accepting this computer only, without a password Your packages
Your MITM ports, hosts and Dofus folder, and your automatic sign-in settings Your game versions and their game data

If you had clicked Log out before, that choice goes too: Asterobot asks you to sign in again by itself. Command line has more about the command.

Game versions

These actions are in each version's menu in Game Manager, except Remove all chunks, which sits above the table. From the gentlest:

Action It deletes It keeps
Verify files The files that don't match, which it downloads again Everything else
Re-extract data The game data, which it builds again from the files The files
Remove extracted data The game data, the extracted pictures and the extracted music The files and the row
Uninstall The downloaded files The row and the game data
Delete The files, the game data and the row The shared chunks
Remove all chunks Every stored chunk, for every version Every version's files and game data

Warning

None of these checks whether a bot uses the version. A bot that signs in on its own can't connect with a version that isn't ready, and a bot whose version was deleted is skipped when Asterobot starts. Move your bots first, as When Dofus updates shows.

Manage game versions explains each action.

cache reset

cache reset deletes Asterobot's whole cache folder, then creates it again, empty.

  1. Stop Asterobot with Ctrl+C in its terminal, or with Shutdown server. It must not run during the reset, and stopping it normally puts back the line it may have changed in your Dofus folder, which it can't do once its copy of the game is gone.
  2. Open a terminal in the folder where you put Asterobot and run ./asterobot cache reset, or .\asterobot.exe cache reset in PowerShell on Windows. If you start Asterobot with --cache-dir or ASTEROBOT_CACHE_DIR, give the command the same folder.
  3. When it asks Delete <folder> with everything in it? [y/N], check that <folder> is the cache folder you mean, then type y and press Enter.
  4. It prints Resetting the cache.. then All cache have been removed.
  5. Start Asterobot, then download and extract the game versions your bots use.
It deletes It keeps
Every game version, with its files and game data The settings folder: config.toml and the asterobot.net sign-in
Every stored chunk The data folder: bots, Ankama accounts and library
Ankama's download lists
The screenshots of failed automatic sign-ins

Bots set to a deleted game version are skipped when Asterobot starts, until you download and extract that version again. Command line has more about the command.

One thing at a time

To remove Where What goes What stays
A bot Delete bot in the bot's menu in Bot Manager, then Yes, delete The bot, its settings, package settings, message selection, console history and MITM attachment Its Ankama account
An Ankama account's sign-in Disconnect in the account's menu in Account Manager Its tokens. Asterobot asks Ankama to revoke them, and forgets them either way The account and its stored password
An Ankama account Remove in the account's menu in Account Manager, then Yes, remove The account, with its password and tokens. Nothing is revoked with Ankama Its browser profile, its last failure screenshot, and the bots that use it
A package version Remove in the package's menu in Library Manager, then Yes, remove That version Other versions, the packages it depends on, and the bots set to it
The asterobot.net sign-in Log out in the account button's menu Asterobot's sign-in. It stays signed out, even after a restart, until you click Sign in Everything else

What follows from each:

  • A bot that used a removed account can't connect, and it's skipped at the next start until the account is back with the same Login ID. See Account status and actions.
  • A bot set to a removed package version can't start its script until you move it to another version. See Manage your library.
  • While Asterobot is signed out, it can't add bots or download packages, and it skips every saved bot when it starts. See Your account.
  • A deleted bot only comes back if you add it again from scratch. See Disconnect, delete and restart.

Start completely over

Deleting Asterobot's folders takes it back to its first launch. Nothing is stored next to the program, so deleting or replacing the program file alone changes nothing.

Caution

These folders hold your Ankama passwords and tokens and your asterobot.net sign-in. Deleting them is final: back up anything you might need first (Files and folders).

  1. Stop Asterobot with Ctrl+C in its terminal, or with Shutdown server on Server > Status, so it puts back the line it may have changed in your Dofus folder. Once its cache folder is gone, it can no longer read the original line back.
  2. Delete the folders you want to reset. Files and folders shows where each one is on your system.
  3. Start Asterobot. It creates the folders again, empty, and asks you to sign in to asterobot.net, as on its first launch.

What each folder takes with it:

Folder Deleting it loses
Settings config.toml: every setting you changed, and the asterobot.net sign-in
Data bots.toml with every bot, accounts.toml with your Ankama accounts, your library of packages, the HTTPS certificate and the sign-in browser profiles
Cache Every game version with its game data, the stored chunks, Ankama's download lists and the screenshots of failed sign-ins

If you start Asterobot with folder options or their environment variables, the folders to delete are the ones they name (Command line).

Asteroboard's Server URL and preferences live in each browser, not in these folders. Clear them as described in In your browser if you want them gone too.

Where to go next

Compte

Navigation

Recherche

Recherche

Configurer les notifications push du navigateur

Chrome (Android)
  1. Appuyez sur l'icône de cadenas à côté de la barre d'adresse.
  2. Tap Autorisations → Notifications.
  3. Ajustez vos préférences.
Chrome (Desktop)
  1. Cliquez sur l'icône représentant un cadenas dans la barre d'adresse..
  2. Select Paramètres du site.
  3. Find Notifications et ajustez vos préférences.