---
name: combat
description: "Build secure and responsive multiplayer melee, ranged combat or weapon systems"
disable-model-invocation: true
---

# Fuse Studio / combat

Task: $ARGUMENTS

Prioritize `knowledge/gameplay-advanced/combat-feel-system`, `knowledge/engineering-advanced/server-auth-transaction-design`, `knowledge/engineering-advanced/lag-compensation`. Server owns damage/ownership/rate; clients predict feel only. Implement exact paths and multiplayer tests. Don’t claim engine-native subtick parity; state latency tradeoffs.

Common protocol: inspect existing project context first; respect project's coding/style conventions; use targeted local knowledge search only if needed; make minimal coherent edits; verify using available tools; report changed paths and unverified behavior. Follow main Fuse Studio server-authority, cleanup and performance standards.