Implement Sonic 3&K Boss

To implement a ROM-accurate Sonic 3 & Knuckles boss, you model the arena constraints, build the routine state machine for multi-phase patterns, and validate the hit handling and defeat sequences against the s3k-disasm-guide.

Setting up a Sonic 3 & Knuckles boss arena involves configuring camera boundaries and arena constraints to reproduce authentic boss zones. You instantiate a new zone boss instance and register it with the object registry.

Yes, this approach applies across all zones with mini-bosses and end-bosses variants, specifically including Knuckles variants and multi-phase patterns to ensure authentic disassembly behaviors.

The best way to manage boss lifecycle states is by implementing the routine and routine_secondary state machines, which control multi-phase patterns and handle authentic defeat transitions for the game engine.

Yes, you need to reference the s3k-disasm-guide to cross-check boss logic and ensure ROM accuracy. Validation tooling compares your boss implementation directly against the disassembly structure.

For non-boss components in a Sonic 3 & Knuckles level, you should use the s3k-implement-object sister skill. The current boss implementation focuses strictly on arena setup, hit handling, and defeat sequences.