A single event is identified by the event type name and the values of all fields as defined by that type. Event type names must be ‘fully-qualified’ by prefixing the package name into which the corresponding event type was injected, unless the event was injected into the default package

Each event is given on a separate line, separated by a new-line character. Only single-line comments are allowed. Start each comment line with / / or #. Any blank lines are ignored.

For example, the following:

are three valid events given the following event type definition (injected into the default package):

If the above events were saved in an .evt file, engine_send would send each event in turn, as soon as the previous event finished transmission. This behavior can optionally be modified in two ways: specifying that events should be sent in a ‘batch’ and specifying timing data forcing events to be sent at specific time intervals.