I don't believe there are any loops or jumps, and condition testing seems to be simple. The are only three statement forms - conditions, commands, and condition terminators. Conditions are naturally nested, but that's about as complicated as it gets. Each line contains a single instruction. Whitespace in the form of spaces and tabs is ignored.
Comments begin with REM .
All conditions are checked at regular intervals, I imagine. A program to provide some basic editing for script files is available in the utilities package . Action points are set in the .apt file. On a line on its own, this terminates a block of code started with one of the above conditions. This creates an empty party with the given name.