Réglages et actions

Declare the settings your package shows on a bot's Settings tab, with every field, the six types, choices, bounds, defaults, the errors Asterobot reports and editor typing. Settings let the people who run your package change what it does without touching its code. Add a setting showed the basics, and Declarations keeps the compact schema with the full list of error texts. Where the declaration goes A package declares its settings in one place: an object exported as parameters from its index.j

Read your package's current settings with values, react when someone applies new ones with onChange and offChange, and know what happens to saved values when your package changes. Once your package declares settings, its script reads their current values from asterobot:parameters. It can also react the moment someone applies a change. asterobot:parameters is the reference for the module. values import { values } from "asterobot:parameters"; values has one property per setting your package dec

Put buttons on a bot's Settings tab with export const actions, with their fields, the run function and its arguments, what the person clicking sees, and when a button can be used. An action is a button your package adds to the bot's page. Clicking it calls a function of the running script, with values the person can fill in first. Actions suit one-off things someone decides while the bot plays: report something, say something, move on to the next step. For a choice that should last, declare a s

How the settings and actions of the packages your package depends on are scoped, shown on the bot's page and saved, and how to write a package that others can configure. A package can use other packages of the library, its dependencies, and each of them can declare settings and actions of its own. A script only reads the settings of its own package, and a bot's Settings tab shows each package's settings apart. Dependencies covers declaring and importing them. Each package reads its own setting

Give your package's own functions to the Studio with export const steps and export const conditions, with their fields, what run receives and returns, the ref field that asks for game data, and the errors Asterobot reports. The Studio is where a plan is drawn: places on the world map, the order the bot visits them in, and what it does at each one. What a plan can do in the game comes from packages. A step is something done on a map, such as gathering, and a condition is a yes/no question, such

Ship fight profiles in a package as JSON files in its fightprofiles folder, so everyone who installs it can play them, with naming, versions, extends, how Asterobot reads them, testing and every error. A fight profile tells Asterobot's fight module how a bot plays its fights. Players make their own on the Fight Profiles page (Fight profiles), and a package can ship some too: a farming package can come with the profiles its fights are tuned for, and a package can exist only to share profiles. On