SGDK combat

Start with the game's combat rules, then connect its existing action clocks and collision queries to a damage resolver. SGDK draws sprites and plays sound; attack ownership, guard, damage and recovery are application C code.

Keep responsibilities clear

Read skill boundaries when the task spans animation, collision, AI, RPG systems or multiplayer. Reuse the project's conventions and implementations instead of adding a second action clock, input reader, collision solver or player registry. Related skills are optional companions; this skill and its Lab install independently.

Agree on teams/friendly fire, what counts as front guard, repeated-hit rules, invulnerability, simultaneous attacks and interruption. Decide whether defeated actors' projectiles persist, and what losing the last player means. These are game policies, not universal SGDK behavior. Art, audio, combat style, camera, timings and difficulty in the Lab are illustrative, never prescriptions.