Before you publish

Once your package is on asterobot.net, people install it on their own Asterobot, with their own bots and their own settings, and a version they installed stays as it is. So go through this list before you upload anything. Each item links to the page that explains it.

It runs on both kinds of bot

• The script identifies a Full socket bot on its initial launch, with the lines from Identify and run. Without them, a Full socket bot never gets into the game.
• You tested it on a MITM bot (man-in-the-middle: the bot relays the game session of a Dofus client someone plays), and on a Full socket bot when what the package does allows it.
• Every await inside a handler sits in try/catch, and every wait() has a timeout. An error that escapes a handler stops the script: see Errors.
• The editor's error badge shows no error.
• The script says so on the bot's console when something it expects doesn't happen, and never writes session.gameToken anywhere.

Settings and actions

• Package settings, on a bot set to your package, shows your cards and not Couldn't read this package's settings.
• Every setting has a label, a sensible default, a description when the label isn't enough, and a unit for a number that has one. See Declare settings.
• The keys of your settings are the ones you'll keep. Renaming a setting in a later version loses the values people saved: see Read settings.
• Each action works while the script runs, and its key reads well in the toasts that end with finished and failed.

Dependencies and manifest

• Every dependency is published, has the URL of its file on asterobot.net, its marketplace name and an exact version. See Dependencies.
• If the package declares a compatibleVersion, its page shows Compatible on your Asterobot. See Compatibility.
• The permissions list what the package really uses. See Permissions.
• The manifest has no sourceId and no integrity. A package created, copied or imported in Asteroboard never has them.

Version and name

• The version is a semantic version, three numbers such as 1.0.0. See Names and versions.
• You never published different code under this version. See Publish an update.
• The title you'll give the file, and your asterobot.net name, contain letters from a to z or digits, since the package's name is built from them. See How your package is named.

The archive

• You exported the version you tested, with Export in Library Manager. See Zip files and the command line.
• The archive weighs less than 32 MiB.
• You imported the exported .zip under another local name, such as my-bot-check, and that package starts on a bot. That's the code people will install. Remove the check package afterwards.

Next, Publish on asterobot.net.