Packages

What a package gives your bots, where packages come from, and how to read the badges Library Manager shows for each one. A bot on its own connects to Dofus and nothing more. What it does once it's in the game comes from a package: you install packages in your library, then give one to each bot. What a package holds A package is a small set of JavaScript files, its script, that Asterobot runs for a bot. You don't need to read or write that code to use a package. Besides the script, a package

Find a package on asterobot.net, check what it will install as, and add it to your library from Library Manager or straight from a bot's package picker. The marketplace is the Library category of asterobot.net, where players share packages. You browse it on the website, then paste a file's link or ID into Asteroboard, and Asterobot downloads the package into your library, with the packages it depends on. Asterobot downloads files with your asterobot.net account, so it must be signed in first.

Give a bot a package, start and stop its script, switch it to another version, run a quick inline script, and know what's kept after a restart. A bot plays one package at a time. You choose which one and the bot remembers it; its script then runs each time you press Play, as long as the bot is connected to a game. Script authors will find what happens inside the script in Play, stop and reload. Set, and running What a bot is set to play and whether it plays it are two separate things. The b

Change the options a package declares for a bot, apply them while the bot runs, and use the buttons a package adds. Many packages let you adjust what they do without touching their code: which resource to gather, how long to wait, a list of names to answer. Those options are the package settings, and the buttons a package adds are its actions. Both are on the bot's Settings tab, and both come from the package the bot is set to play. When time slots of the bot's schedule play other packages, a l

Check asterobot.net for new versions of your marketplace packages, install them next to the old ones, move your bots over and clean up. When an author publishes a new version of a package on asterobot.net, nothing changes in your library until you ask. You check for updates, install the new version next to the one you have, move your bots to it when it suits you, then remove the old version. Only packages installed from the marketplace can be updated this way. Base updates by itself @asterobo

Everything in Library Manager and on a package's page, including importing and exporting .zip files, copying packages and removing them. Library Manager lists every package installed in your Asterobot. From there you install, create, import, copy, export and remove packages, and each package has a page of its own with its details. The Library Manager page The buttons at the top are Check for updates on the left, and Import a .zip, Download package and New package on the right. Under them, a

What a package's script can and can't do with your bot and your game session, how Asterobot checks marketplace packages, and how to decide whether to run one. A package is code someone else wrote, running with your bot's game session. Before you play a package you didn't write, know what it can reach. What a package can do When a bot plays a package, its script can do the following. Everything here also applies to the packages it depends on, since their code runs in the same script. It ca

Draw what a bot does on the world map, without code: where it goes, in which order, what it does at each stop, and what happens when something fails. The Studio is the part of the package editor where you draw what a bot does instead of writing it. You draw a plan on the world map: the stops the bot goes to, the order it goes round them in, and at each stop the steps it runs there, such as waiting or playing another plan. Conditions, such as how full the bags are, decide whether a stop or a ste