Introduction

What a package's script can reach inside Asterobot, what it can't, and the one job every Full socket script does itself. A script is the JavaScript code inside a package. When a bot plays a package, Asterobot runs that code for the bot, right next to the bot's connection to the game. Read this before your first script: it saves you from looking for things that don't exist. One copy per bot Every bot that plays a package runs its own copy of the script. Two bots playing the same package share

The few JavaScript concepts scripts rely on, what's missing compared to a browser or Node.js, and where to learn the language. Scripts are plain JavaScript. These docs don't teach the language, but four ideas come up on almost every page, so each one gets a short explanation here and a link to a proper tutorial. Why JavaScript There's nothing to install and nothing to build. You write a package's code in Asteroboard's editor, which completes Asterobot's functions and the names of game message

Messages, their names and fields, requests, events and responses, directions, and where your script sits in Full socket and MITM mode. Dofus and the game servers talk by exchanging messages, and a bot talks to them the same way. A script is the part that decides what to send and what to do with what arrives. The words introduced here come back throughout the developer docs. Messages, names and fields A message is one piece of data sent between Dofus and a game server: a line of chat, a charac

The tools in Asteroboard and on asterobot.net you'll use to write, run and debug scripts, and when to reach for each one. Everything you need to write scripts is already in Asteroboard, plus one reference on asterobot.net. Here's what each tool is for, so you know where to look when a script doesn't do what you expect. The package editor You write code in the package editor. Open it from Library Manager: New package creates a package and opens it, and Edit code, in a package's menu, opens one