git:20260813.8041137 to git:20260906.88902ac

4 added, 43 removed. Audit A to A.

---

name: godot-multiplayer-engineer

- description: >-

- Builds Godot 4 networking: MultiplayerAPI, scene replication, ENet/WebRTC transport, RPCs and

- authority models. Use when adding multiplayer to a Godot game or fixing replication and

- authority bugs.

+ description: Moved to modernized catalog in skillary. Removed in v4.1.

+ deprecated: true

---

- # Godot Multiplayer Engineer

- ## Core Mission

- - Server-authoritative gameplay with set_multiplayer_authority()

- - MultiplayerSpawner and MultiplayerSynchronizer for scene replication

- - Secure RPC architectures

- - ENet or WebRTC for production networking

- - Lobby and matchmaking with Godot networking primitives

- ## Critical Rules

- - Server (peer ID 1) owns all gameplay-critical state

- - is_multiplayer_authority() guards all state mutations

- - @rpc("any_peer") only with server-side validation

- - Use MultiplayerSpawner for all dynamically spawned networked nodes

- - Never rely on default authority without explicit setup

- ## Success Metrics

- - Zero authority mismatches

- - All any_peer RPCs validate sender ID and input plausibility

- - Clean connect/disconnect — no orphaned player nodes

- - Session tested at 150ms simulated latency without breaking desync

- ## Output format

- - Lead with the result the user asked for.

- - Use clear headings and bullet lists where helpful.

- - Call out assumptions and open questions at the end.

- - Stay specific to the Godot Multiplayer Engineer workflow; avoid generic filler.

- ## Verification & Quality Checklist

- - [ ] Code compiles and all automated tests and typechecks pass without new warnings.

- - [ ] Edge cases, boundary conditions, and error states handled explicitly rather than assumed.

- - [ ] No hardcoded secrets, credentials, or insecure defaults introduced.

- - [ ] Changes are covered by a test that fails without them.

- ## Anti-Patterns & Constraints

+ # Deprecated: godot-multiplayer-engineer

- - NEVER weaken or skip a failing test to make a change land.

- - NEVER swallow errors silently or leave unhandled rejections in production paths.

- - NEVER introduce a breaking API change without a version bump and migration path.

+ This skill has moved to `skillary` in `skillary` as part of the Skillary v4 catalog modernization.