How BBS works in-game

Generic states

The battle state manager looks for, and uses, several default states. This means the developers don't have to explicitly handle generic state transitions. If a standing move ends, characters start looping CmnActStand. If a character gets hit, they'll go into the state that matches the hit reaction.

The battle state manager is also able to affect program flow within those default states.

beginState: s32(CmnActJump) {
	label: s32(_Upper)
	label: s32(upperloop)
	sprite: s32(kfs021_00), 3
	sprite: s32(kfs021_01), 3
	sprite: s32(kfs021_02), 3
	spriteEnd:
	gotoLabel: s32(upperloop)
	label: s32(_UpperToTop)
	sprite: s32(kfs021_03), 2
	sprite: s32(kfs021_04), 2
	sprite: s32(kfs022_00), 2
	sprite: s32(kfs022_01), 2147483647
	label: s32(_Top)
	sprite: s32(kfs022_02), 2147483647
	label: s32(_TopToDown)
	sprite: s32(kfs022_03), 3
	sprite: s32(kfs022_04), 2147483647
	label: s32(_Down)
	label: s32(downloop)
	sprite: s32(kfs022_05), 3
	sprite: s32(kfs022_06), 3
	sprite: s32(kfs022_07), 3
	spriteEnd:
	gotoLabel: s32(downloop)
} endState:

As you can see, there are several different labels in this CmnActJump state, but you won't ever find a function that actually jumps to _TopToDown. Instead, the battle state manager does so itself when the proper conditions are met (e.g. airborne, Y-speed less than 0).

The battle state manager can also add function calls whenever it detects certain active state names. For example, DBFZ's CmnActMikiwameMove (Vanish) will initiate a worldStop, even if all relevant calls in the script have been deleted.

Generic subroutines

The battle state manager is also able to call a subroutine for an object on it's own accord. Here are a few notable ones:

For DBFZ, OnIdling is called even for assist characters that are off-screen.