A package can fail at several moments: while you install it, when a bot starts it, or while it runs. If you write packages, Error messages in the developer docs lists every text with its cause.
Find the reason first
Several package messages come without their reason, which is always somewhere else:
| Where | What you find there |
|---|---|
| The behavior stopped with an error, under the bot's header | The full error of a script that started, then failed. Copy puts it on your clipboard. |
| The bot's Settings tab, under Package settings | Couldn't read this package's settings, with the reason, when the bot's package can't be loaded at all. |
| The editor of a local package | The error badge in its top bar, such as "3 error(s)", which counts the problems across every file of the package. |
| The bot's Console tab | What the script itself writes, warnings included. |
Couldn't start the behavior
You clicked Play, and the script couldn't even start. The notification gives no reason, and the bot's page shows no alert.
- Check that the bot is Connected to game server. Load a package and play it on a bot that isn't connected loads the package, then shows this message.
- Open the bot's Settings tab and click Package settings. When the package can't be loaded, Couldn't read this package's settings shows the reason.
- Find that reason in Reasons a package can't load.
Three other messages work the same way, without a reason: Couldn't load the selection after loading a package, Couldn't switch version after picking another version in the bot's header, and Couldn't run the package after Run in the editor. Look under Package settings for each.
Reasons a package can't load
requires asterobot
The text reads like package "<name>" requires asterobot <range>, running <version>. The package states which versions of Asterobot it works with, and yours isn't one of them. Library Manager marks it Incompatible, and its name turns orange in the bot's header.
- If the range asks for a newer Asterobot, update it: see Updating Asterobot.
- If another installed version of the package is compatible, move the bot to it: see Switch to another version.
- For a marketplace package, click Check for updates in Library Manager: a newer version may support your Asterobot.
- Otherwise, contact the author.
has an invalid compatibleVersion constraint means the author wrote that range wrong. Only the author can fix it.
package source integrity mismatch
The files of a package installed from the marketplace no longer match the ones Asterobot downloaded, for example because they were edited by hand. Asterobot refuses to load it.
- In Library Manager, open the package's menu, click Remove, then Yes, remove.
- Install it again from the marketplace, with the same file link. See Install from the marketplace.
- Move the bot back to that version if it changed.
Trusting a package explains the check.
read package or is not installed
The package, or one of the packages it depends on, isn't in your library at the version the bot needs. The text names the missing one, as in read package <name>@<version> sources:. It happens after a package or a dependency was removed, or when installing a dependency failed.
- For a marketplace package, install it again from the marketplace: Asterobot downloads the dependencies it lacks along with it.
- If you removed that version on purpose, move the bot to a version that's installed.
parse module or resolve
A text that contains parse module or resolve means the package's code has an error: a syntax mistake, or an import that points at nothing.
- For a package from the marketplace, check for an update, and tell its author, with the full text.
- For a local package, open it with Edit code: the error badge leads you to the problem. Error messages explains each text.
The behavior stopped with an error
The script started, then failed. The alert shows its full error, and the Behavior column of Bot Manager says Failed. The bot stays connected, and a relayed game keeps playing. These are the texts players meet most:
| The text contains | What it means | What to do |
|---|---|---|
Game session closed |
The game connection closed while the script ran: you quit Dofus, the bot was disconnected, or the connection dropped. | Bring the bot back online, then click Play. |
IdentificationRequest.token: unknown protobuf field |
The script was built from an old example that sends the wrong fields to enter the game. | Update the package, or ask its author to. Authors: see Identify and run. |
JavaScript execution deadline exceeded |
The script worked for more than 250 ms without a pause. | Tell the author. |
behavior event-loop queue overflow |
The script couldn't keep up with the messages it receives. | Tell the author. |
unhandled Promise rejection: |
An error in the script that nothing caught. | Tell the author, with the full text. |
behavior requested Game disconnect |
The script disconnected the bot on purpose. | Nothing, if the package is meant to do that. |
the game engine is not available: |
Asterobot couldn't read the game's messages. | See When Dofus updates. |
To start the script again, click Play. If the same error comes back, the package needs a fix.
Installing from the marketplace
| Message | What to do |
|---|---|
Not a valid file ID or asterobot.net file URL. |
Copy the address of the file's own page on asterobot.net, or its number, not the address of the category. |
File not found, or you don't have permission to view it. |
Check the address. Then check the account button at the bottom of the sidebar: Asterobot has to be signed in to asterobot.net to ask about a file. |
You don't have permission to download this file. |
Your asterobot.net account isn't allowed to download this file, and nothing in Asterobot changes that. |
| Couldn't install the package | The download or the installation failed, without a reason. The file may not be a package, have more than one attachment, weigh more than 32 MiB, or have a dependency that can't be installed. |
When a dependency failed, the package itself may already be in your library without it, and it won't start. Install from the marketplace has the details.
Updating
- Couldn't check for updates: the check didn't go through. Check that Asteroboard is connected and that Asterobot is signed in to asterobot.net, then try again.
- Couldn't install the update: the same causes as a first installation, and no reason either.
- No Update to button, although the author published a new version: nothing is checked by itself, so click Check for updates. A version lower than yours isn't offered, and a file that can't be read on asterobot.net any more is skipped without a message.
See Update packages.
Importing and removing
- Couldn't import the package, without a reason: the file may not be a
.zip, have noindex.js, weigh more than 32 MiB, or contain an invalidasterobot.json. The name messages of the import dialog are in Manage your library. - Couldn't remove the script: nothing was removed. Try again.
- After you removed a version, a bot set to it keeps running its script until the script stops, then gets Couldn't start the behavior at the next Play. Move the bot to another version.
Package settings and actions
These appear on the bot's Settings tab, under Package settings:
| Message | What it means | What to do |
|---|---|---|
| Couldn't apply the settings, with a reason | A value doesn't fit what the package expects. Nothing from the form was saved. | Correct the value the reason names, then click Apply again. |
Couldn't start the action, with no behavior is running on this bot |
Actions only run while the package plays. | Click Play, then the action. |
| Couldn't start the action, with another reason | An argument doesn't fit, or the running script doesn't have that action. | Correct the value, or click Stop and Play so the running script matches the package. |
The action's name followed by failed |
The action's own code failed. The script keeps running. | Tell the author. |
Action buttons stay greyed out with "The bot has to be playing a behavior before an action can run." while no script runs. See Package settings and actions.
Contact the author
Only its author can fix the code of a marketplace package.
- In Library Manager, click the package's name.
- In its details, click View on asterobot.net, in the Source row. It opens the file the package came from.
- Contact the author from there, or ask on the forum at https://asterobot.net/forums/. Include the full error text copied with Copy, the package's version, your Asterobot version from Server > Status, and the bot's game version.
Never include your config.toml, a token or a password. Getting help lists what must stay private.
Where to go next
- Run a package
- Manage your library
- Error messages, for script authors