Paquets

What asterobot.json holds, which fields you write and which ones Asterobot adds, how to edit them on the Manifest card, and why Asterobot refuses a manifest. asterobot.json is the one file of a package that isn't code. It says which other packages the package depends on, which Asterobot versions it works with and what it declares it uses. Where it lives At the root of the package, next to index.js. It's optional. A new package has none, and Asterobot only writes one when there's something t

The rules for package names and version numbers, local and marketplace names, why semantic versions matter, and how several versions of a package live side by side. A package is identified by its name and its version together: my-bot 1.0.0 and my-bot 1.0.1 are two packages in your library. The way you number versions matters once other people use your package. Where a name and a version come from Neither is written in the package's files. A package gets them from how it was installed: How

Use another package's code from yours: declare the dependency, choose its version, make it installable for others, import it, and fix what Asterobot reports. A package can use the code of other packages in the library, its dependencies. That's how you share helpers between your own packages, or build on a package someone published. How dependencies work A package declares its dependencies in the dependencies field of its manifest. The key of each dependency is the exact name your code impor

Declare which Asterobot versions your package works with in compatibleVersion, write the range correctly, and know where incompatibility shows and what it blocks. compatibleVersion says which versions of Asterobot your package works with. When someone runs an Asterobot outside that range, the package is marked Incompatible and doesn't start. It's about Asterobot's version, not the game's: a Dofus update changes nothing here. After a game update covers what a game update changes for scripts. De

List what your package uses in its manifest, see where the list shows and how a script reads it, and know that Asterobot doesn't enforce it yet. A package can list permissions in its manifest: short names for what it uses. For now the list is information for the people who install your package, and Asterobot doesn't limit anything based on it. Note Coming soon. Asterobot will enforce the permissions a package declares. Until then, any package can use every function of every built-in module, w

Every part of the package editor, with its files and plan files, saving and unsaved changes, Run, the Game panel, completion and error checking, and why marketplace packages can't be edited. The editor is where you write a package's code, in Asteroboard. Create a package gave a first tour of it. Some of its parts aren't obvious: saving replaces the package's files, Run does four things in one click, and a clean error badge doesn't mean the script will run. Open it In Library Manager, open a

How a package archive is laid out, its size limit, Export and Import in detail, the library install, library list and library remove commands, and working on a package with your own code editor. A package leaves Asterobot and comes back as a .zip file: that's what Export produces, what Import a .zip reads, and what you upload to publish on asterobot.net. The command line installs packages from a folder instead, which lets you write them in the code editor you already know. What goes in a .zip