Step 1: Build the AI Orchestrator

Implement a "Router" state (e.g., Statedef 80000-80005). Use randomized logic to jump between different attack modules. This prevents other characters from predicting your AI's pattern.

Step 2: Configure Variable Gates

Use local variables as logic switches to control the flow between standard combat and exploit subversion.

• var(7): Acts as the Memory Subversion Flag (keeps exploit modules active).
• var(23): Acts as the State Gate (triggers transition to "Super" payload states).

Step 3: Execute Payloads

Design your attack states (e.g., 230, 400) to contain the core exploit logic. Use DisplayToClipboard within these states to output your variable values to the debug log, ensuring your memory gates are toggling correctly.

Step 4: Force State Persistence

Use the -2 and -3 state files to override K.O. rules. This ensures that even if the character takes fatal damage, it forces a SelfState loop to maintain operational status.