The main functions of the AS debug are:

1. The scrs_debug console command.
2. The st_entity_stats console command or the AS Stats Info Window.
3. The req_debug console command.

1. The scrs_debug <type> Console Command

<type> is a bitmask defining what output you’re going to receive in debug.

Mask values:

efilter_none			= 0, 
efilter_motion			= 1 << 0, 
efilter_delta			= 1 << 1, 
efilter_state			= 1 << 2, 
efilter_blender			= 1 << 3, 
efilter_procedural		= 1 << 4, 
efilter_all				= u32(-1),

For this to work, an object must be selected. There are no restrictions on the number of objects.

For example, in order for the motion and delta debug information to appear, the result of the following operation should be sent to output:

result = efilter_motion | efilter_delta = (1 << 0) | (1 << 1) = 0b00000001 | 0b00000010 = 0b00000011 = 3 (decimal)

Thus, the complete command will look like "scrs_debug 3".

As a result, you have an idea of what the AS debug will look like when you request it.

AS is a multi-level graph of animated states displayed according to their nesting levels. By default, this command is entered and the AS currently playing will appear on the selected NPC.

2. The st_entity_stats <value> Console Command or AS Stats Info Window

Both of these will output the data provided by scrs_debug but in a different way.

st_entity_stats <value> - 1/0, debug state, on / off

This allows you to read an object’s AS without looking at the object.

Limited to a single object.

To select an object in runtime, you can use the console command "select <name>".

3. The req_debug <value> Console Command

req_debug <value> – 1/0, debug state, on/off.

For this to work, an object must be selected.

This is limited to a single object.

To select an object in runtime, you can use the console command "select <name>".

The instruction’s goal is to track requests in AS.

All outputs are redirected to the log. There will be a lot, so filtering will be necessary.

The main messages are:

• request completed already – request already completed.
• request confirmed – request confirmed and will be completed.
• INDIRECT request confirmed – indirect request confirmed (this means that the target is not in the current state).
• request began0 – request execution started.
• request step processed – information on status of the request.
• request completed – request completed.