godot-genre-shooter

Core Loop

Engage → Aim (soft-lock/cover) → Fire → Confirm → Acquire Next

NEVER Do (TPS / hybrid)

• NEVER put FPS viewmodel/bob/look recipes in this skill — route to shooter-fps.
• NEVER use process() for hit registration — physics_process + space-state queries.
• NEVER trust the client for authoritative hits — server validate / rewind.
• NEVER use Area3D overlap for bullets — ray / shape queries.
• NEVER hardcode weapon stats in logic — WeaponData Resources.
• NEVER skip excluding the shooter's RID on queries.
• NEVER use TCP for shooter net sync — ENet/UDP.

MANDATORY scripts (non-FPS paths)

Read before implementing the matching system:

1. [softlockaimassist.gd](scripts/softlockaimassist.gd) — controller/hybrid assist & sticky aim
2. [covervalidatorrays.gd](scripts/covervalidatorrays.gd) — cover / peek validity rays
3. [tpscameraspringarm.gd](scripts/tpscameraspringarm.gd) — SpringArm3D TPS camera collision

Also available: [advancedweaponcontroller.gd](scripts/advancedweaponcontroller.gd) (shared weapon controller — prefer FPS skill for FPS feel), [shooterpatterns.gd](scripts/shooterpatterns.gd), [projectile.gd](scripts/projectile.gd), [weaponrecoilpattern.gd](scripts/weaponrecoilpattern.gd) (spray Resource), [lagcompensator.gd](scripts/lagcompensator.gd) (server rewind).

Decision trees

Camera / stance

Fire mode

Net

Weapon selection (short)

Hitscan for rifles/SMGs; physical projectiles for rockets/arrows; balance in WeaponData Resources (.tres), never hardcoded on nodes.

Gunplay theory → [tps-gunplay-core.md](references/tps-gunplay-core.md). Net rewind → [advanced-meta-systems.md](references/advanced-meta-systems.md).

Recoil and feel (WHY)

Apply kick to camera rotation and spread bloom, not weapon mesh alone. Learnable spray via [weaponrecoilpattern.gd](scripts/weaponrecoilpattern.gd). Layer gunfire: mechanical + shot + reverb tail on separate 3D players.

Multiplayer (short)

Client predicts VFX/tracers; server validates hits (rpc + rewind). Never trust client damage. ENet/UDP, not TCP. Server wins on mismatch — show no-reg feedback.

Reference

Progressive disclosure: open Official Documentation links only when researching a specific API; load Related Skills when routing to a peer domain — do not preload the whole lattice.

Official Documentation

• Ray-casting — PhysicsDirectSpaceState3D.intersect_ray hitscan queries, exceptions, and collision masks for frame-rate-independent fire.
• Physics introduction — layers/masks, physics_process timing, and body types that keep hit registration deterministic.
• PhysicsDirectSpaceState3D — direct intersectray / intersect_shape for high-frequency shots without RayCast3D node overhead.
• PhysicsRayQueryParameters3D — from/to, exclude RIDs, and collisionmask for shooter-owned hitscan queries.
• CharacterBody3D — moveand_collide projectile bodies with gravity, bounce, and lifetime.
• SpringArm — collision-aware TPS camera boom and shoulder offset without clipping into cover.
• Using decals — perspective-correct bullet holes and impact marks instead of Sprite3D billboards.
• Controllers, gamepads, and joysticks — stick look input that aim-assist friction/magnetism modulates.
• High-level multiplayer — RPC authority and unreliable modes for fire events with server-validated hits.
• Camera3D — FOV punch, aim rays from -globalbasis.z, and h_offset for TPS shoulder swap.
• PhysicsShapeQueryParameters3D — sphere/shape queries for rocket/grenade AoE without Area3D spam.
• AudioStreamPlayer3D — layered shot/mechanical/tail players for punchy spatial gunfire.

Related Skills

Prerequisites

• godot-physics-3d — CharacterBody3D/RigidBody3D, collision layers, and direct space queries that hitscan and projectiles depend on.
• godot-input-handling — look/fire/reload action maps and gamepad stick curves before aim assist and recoil kick.
• godot-camera-systems — FPS/TPS camera rigs, FOV, and SpringArm patterns that weapon kick and soft-lock rotate.
• godot-project-foundations — Resource-based WeaponData, scene structure, and import defaults before balancing archetypes.

Complements

• godot-combat-system — damage events, hit zones, and health pipelines that consume shooter take_damage results.
• godot-raycasting-queries — reusable ray/shape query helpers for cover checks, LOS, and hitscan without duplicating query setup.
• godot-audio-systems — bus routing and 3D attenuation for mechanical + shot + reverb-tail gunfire layers.
• godot-multiplayer-networking — ENet peers, RPC modes, and authority so fire is predicted client-side and damage is server-validated.
• godot-adapt-single-to-multiplayer — prediction, reconciliation, and lag-compensation shells around hitscan validation.
• godot-particles — muzzle flash, tracers, and impact bursts that sell gunplay without blocking the fire path.

Downstream / consumers

• godot-monte-carlo-balancer — simulate TTK, spray patterns, and weapon asymmetry matrices so archetype damage/recoil stay competitive.
• godot-genre-shooter-fps — FPS-specialized movement and viewmodel polish that builds on this genre gunplay lattice.
• godot-genre-battle-royale — large-scale matches that reuse hitscan/projectile combat inside drop/zone loops.

Master

• godot-master — library router and mirrored module entry for cross-skill discovery.