Shooting and projectiles
Shooting connects position selection to the moment of firing. Distinguish view direction, weapon direction and the actual hit query: the camera may see a target while a wall blocks the muzzle. Traveling projectiles need readable trajectories and flight time; immediate hits need clear feedback and a consistent reticle. These overviews propose original rules and hypothetical scenarios. Godot's documentation explains ray intersection queries, not network lag compensation or a universal weapon model.
No matches
Change your query or reset the filters.
Mechanics and variants
1First-person shootersOverview and example ↗The player controls a first-person view and weapon, trading precision against speed and exposure.4
Mechanic variants
- Aim down sights: zoom trades awareness for precision.
- Hip fire: movement increases the spread of shots.
- Leading shots: slow projectiles require prediction.
- Reloading: an empty magazine creates vulnerability.
Design example. A fast corridor enemy forces a choice between a shotgun and a precise shot through a doorway. Prototype check: Test shots beside a wall: camera and muzzle lines must not produce an unexplained hit result.
2Third-person shooters and coverOverview and example ↗A camera behind the character exposes surrounding space, while cover changes firing angles and movement options.4
Mechanic variants
- Cover snapping: the character occupies a cover edge.
- Peeking: firing temporarily exposes the body.
- Shoulder swapping: the camera changes the visible angle.
- Destruction: repeated hits remove cover protection.
Design example. A flanking route forces the player to leave cover while a partner suppresses the opponent. Prototype check: Test both sides of an obstacle: seeing a target must not permit firing through geometry blocking the muzzle.
3Arena shootersOverview and example ↗An arena turns weapons, elevation and respawning resources into a route of continuous movement and control.4
Mechanic variants
- Control: strong weapons spawn in exposed locations.
- Verticality: jump pads open an elevated route.
- Duels: resource timers determine encounter timing.
- Splash fire: explosions deny an escape route.
Design example. Armor spawns on a lower platform while an opponent above can already cover the approach. Prototype check: Map resource routes and test whether one stationary position can control every important spawn.
4Tactical shootersOverview and example ↗A short elimination window makes information, positional discipline and coordinated entry central decisions.4
Mechanic variants
- Angle clearing: sequential checks limit simultaneous threats.
- Suppression: fire denies safe movement through a lane.
- Loadouts: equipment trades movement against protection.
- Rounds: limited lives increase the value of reconnaissance.
Design example. A team clears two doorways while one player watches a possible flanking route. Prototype check: Test whether players understand an elimination and can counter a defended choke point.
5Hero shootersOverview and example ↗Distinct hero abilities modify shared shooting rules and create dependencies between team roles.4
Mechanic variants
- Roles: a defender creates an opening for an attacker.
- Cooldowns: powerful skills appear in separate windows.
- Combos: an ally's mark strengthens a following attack.
- Counterpicks: changing heroes answers a specific threat.
Design example. A shield enables moving a stationary turret while temporarily exposing another team lane. Prototype check: Test a roster missing one hero: the core objective should remain solvable without a compulsory pick.
6Looter shootersOverview and example ↗Shooting produces equipment whose properties reshape later combat and target selection.4
Mechanic variants
- Affixes: conditional bonuses change preferred range.
- Rarity: an unusual item introduces a new action.
- Sets: several items connect separate abilities.
- Comparison: item stats explain a practical role change.
Design example. A rifle restores charge after a precision hit, favoring deliberate fire over sustained bursts. Prototype check: Compare items on the same target and separate increased damage numbers from genuinely new decisions.
7Extraction shootersOverview and example ↗A sortie ends only upon extraction; acquired loot raises both the value of leaving and the risk of continuing.4
Mechanic variants
- Exits: different extraction points impose different conditions.
- Noise: combat reveals position to other participants.
- Insurance: a stated rule recovers part of a loss.
- Cargo: valuable loads hinder speed and stealth.
Design example. A recovered engine slows movement, and the nearest exit requires waiting for a noisy lift. Prototype check: Test extracting early with modest loot: it should be a meaningful strategy rather than a disguised failure.
8Rail and light-gun shootersOverview and example ↗The system fixes the camera route while the player allocates attention among targets, threats and firing windows.4
Mechanic variants
- Priority: a dangerous target interrupts score collection.
- Reloading: a firing pause requires deliberate timing.
- Branches: hitting a switch changes the route.
- Cover: a separate command interrupts aiming to defend.
Design example. A train passes three towers; shooting a track switch opens a safer route. Prototype check: Replay with slower aiming and ensure threats appear before their mandatory response window begins.
9Twin-stick and multidirectional shootersOverview and example ↗Movement and firing direction are independent, enabling retreating attacks and deliberate range control.4
Mechanic variants
- Circling: movement routes around a group's center.
- Aim lock: holding direction supports sustained fire.
- Overheat: firing requires periodic cooling breaks.
- Recoil: shots assist or obstruct character movement.
Design example. The hero retreats along a spiral while shooting into a swarm and preserving an outer safety lane. Prototype check: Test independent axes and sensitivity settings: stopping movement must not unexpectedly change aim.
10Shoot ’em ups, bullet hell and bullet grazingOverview and example ↗The player reads projectile patterns and chooses safe paths; near misses can optionally grant a reward.4
Mechanic variants
- Lanes: a pattern leaves predictable safe corridors.
- Aimed volleys: movement draws a stream away.
- Grazing: passing near a bullet earns a separate resource.
- Bombs: a limited stock clears a dangerous field.
Design example. Slow rings intersect an aimed stream that the player can draw toward the screen edge. Prototype check: Display the hitbox and graze region; verify safe gaps without unreadable projectile overlaps.
Sources and examples
Sources support particular techniques or methodology, not every family variant. Design examples and mechanic combinations are illustrative.
- Godot: Ray-casting
Primary documentation of 2D and 3D ray intersection queries; implementation context for hit and line-of-sight checks.
CC BY 4.0 · gamemechanics.pro contributors