Publication

A checklist to go through before you upload a package to asterobot.net, so that it installs, starts and keeps working for the people who download it. 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 in

Submit your package as a file in the Library category of asterobot.net, fill in what Asterobot reads from it, check that it installs, and share the link. The marketplace is the Library category of asterobot.net, and any asterobot.net member can publish a package there. Publishing means submitting a file on the website with your exported .zip attached. You need an asterobot.net account, as Create an asterobot.net account explains, and the .zip of your package, exported once you've gone through

Publish a new version of your package on the same asterobot.net file, understand how people and the packages that depend on yours get it, and why a version number must never be reused. A package on asterobot.net changes by getting new versions on the same file. The people who installed it see the update the next time they check for updates, and choose when to move their bots to it. Prepare the new version In Library Manager, open your package's menu and choose Copy to a new version, with a h

How Asterobot builds the @author:title name of a package installed from asterobot.net, why the name stays after a rename, what happens when the author or the official mark changes, and how official packages are named. Every package installed from the marketplace gets a name of the form @publisher:name, built from its file on asterobot.net. You don't type that name anywhere, but you choose what it's built from. The name at first install The first time someone installs a file, Asterobot builds