Fight profile format

The exact JSON format of a fight profile, every field with its type, values and default, conditions, actions and targets, how extends merges, and every error and warning Asterobot reports.

A fight profile is a JSON object. Players write them on the Fight Profiles page, where the editor shows the same JSON (Fight profiles), and packages ship them as files, one per profile, in their fightprofiles folder (Ship fight profiles). This page is the complete format. What each setting does in a fight is explained, for players, in Profile settings and Rules and conditions.

Every field is optional but name. A field left out plays its default, and a field Asterobot doesn't know is kept and ignored, so a profile written for a newer Asterobot still loads.

{
  "version": 1,
  "name": "Air Cra",
  "role": "damage",
  "range": "ranged",
  "elements": ["air"],
  "risk": 40,
  "positioning": "kite",
  "spells": [{ "id": 32465, "use": "prefer" }],
  "rules": [
    { "when": { "self.life": { "below": "30%" } }, "do": { "retreat": { "to": "outOfReach" } } }
  ]
}

Fields

An empty string in a field that takes a word, such as "role": "", is the same as leaving it out. A word the field doesn't take is an error.

parts

Writing parts with some fields leaves the others true.

weapon

spells

Each entry says what the profile does with one spell.

opening

A step is a spell's id, "weapon", or { "spell": <id or "weapon">, "target": <target> } with a target. Steps are cast in order, each when it can be; a step that can't be cast is passed over. A spell listed twice is cast twice.

monsters

Each entry needs id or race. It applies to every enemy it matches.

weights

An object of numbers, 0 or more, by scoring term: damage, kill, heal, control, buff, summon, safety, position, waste, allyHarm and mark. A term left out keeps the role's weight. How a turn is scored gives each role's weights.

Rules

rules is an array of rules, applied in order. Each rule is an object:

Actions

do holds one of these keys:

Every matching modifier applies. Of the movement rules, the first matching one applies. Of the forcing actions, the opening's steps come first and then the rules in order, and the first one that can be played now is the character's next action. How rules apply describes it in full.

Targets

A target is one of these strings, or an object:

Ties go to the lowest fighter id.

Conditions

A condition is an object whose keys are subjects, each with its test, and the groups all, any and not. It holds when every test and every group in it holds.

{
  "self.life": { "below": "50%" },
  "any": [{ "enemies.within": { "cells": 1, "atLeast": 1 } }, { "fight.round": { "atLeast": 5 } }],
  "not": { "self.state": { "is": 42 } }
}

A test is an object with some of these fields:

Each subject takes only its own test fields, at least one of them, and within needs cells of 1 or more: anything else is refused, naming the subject. self.ap, self.mp and target.distance take numbers, not percents. A subject the module doesn't know never holds, with a warning, and so do target.life and target.distance in a rule's when, and challenge, reserved for challenges, until the module plays them.

How extends merges

A profile with extends starts from the profile it names and writes its own fields over it:

The extended profile can't extend another one. A profile that extends a package's profile plays it from the newest version of that package installed.

Errors

Asterobot refuses a profile it can't play: the editor won't save it, an import is refused, and a pool file or a package's profile shows Can't be played on the Fight Profiles page, a bot set to it playing the default profile. The reason starts with fight: malformed profile:, followed by the field, in the JSON's own path, and what's wrong. Only the first problem is reported.

spells[i] is the entry's place in the list, counted from 0, as in spells[0].use. A target's field is written in full, such as rules[2].do.attack.target or opening.firstTurn[0].target.

Pool profiles have their own name errors when they're saved: fightprofiles: a profile's name can't be empty, start with @, or hold / or a character a file name can't, and fightprofiles: a profile already has this name.

Warnings

Warnings don't stop a profile from playing. The Fight Profiles page counts them and the editor lists them.