Skip to content

Zenkai Opcode StackTestPartyMemberFlag

Johnathon edited this page Sep 20, 2026 · 2 revisions

StackTestPartyMemberFlag

Pops two values in push order and calls PartyState_TestMemberFlag(&g_PartyState, a, b), pushing the result.

CONFIRMED 2026-09-19 (disasm of 0x8009628): argument order was previously unconfirmed, now settled — the first-pushed value (deeper on the stack) becomes a, the second/top-of-stack becomes b. There is no separate category selector: PartyState_TestMemberFlag brute-force scans all 68 entries of g_PartyMemberFlagCategories for a descriptor matching the exact (a, b) pair.

Distinct from StackTestStoryFlag (opcode 19) — a completely different, single-id flag test against a different storage region. Despite once sharing similar "Quest"/"PartyFlag" names, these two systems never overlap; see the Quest Log page for which one actually drives the in-game Quest Log (story flags, not this one).

Syntax

StackTestPartyMemberFlag(a, b)

Parameters

a
Integer
First key part, pushed first (deeper on the stack).

b
Integer
Second key part, pushed last (top of stack).

Remarks

Pushes a boolean onto the VM stack.

Examples

Minimal illustrative encoding (synthetic, not from a real ROM script):

0x00, N           // PushByte(a)
0x00, N           // PushByte(b)
0x02, 0x17        // Step -> BytecodeVM_StackTestPartyMemberFlag

See Also

Applies To

Game Notes
Legacy of Goku 2 Supported

Clone this wiki locally