Guide

Game fire mode selector systems explained

Harbor Outpost shipped a tight SMG corridor where three enemies spawned at staggered ranges between eight and eighteen meters. Every rifle-class weapon defaulted to full-auto with a 900 RPM cap and identical recoil bloom whether the player tapped or held trigger. Telemetry showed 58% of squads wiped in that corridor: players dumped entire 30-round magazines into the first target, reloaded in the open while adds closed distance, and missed head-glance shots because spread never recovered between bursts. Expert players manually feathered the trigger, but the game never taught that skill. The refactor added a per-weapon fire mode selector — semi-auto, three-round burst, and full-auto — each with authored RPM, first-shot accuracy bonuses, and recoil recovery curves. Corridor squad wipe rate fell to 19%, average ammo spent per clearance dropped 41%, and weapon mastery achievements for “burst-only clearance” gave experts a visible skill ceiling.

A fire mode selector is the authored rule set that decides how repeated shots leave the barrel when the player presses fire: one round per trigger action (semi), a fixed burst count per press (burst), or continuous fire while held (full-auto). It sits between input handling and ranged combat damage resolution, and it tightly couples to ammo economy, ADS spread, and encounter pacing. This guide covers mode taxonomy, FSM design, per-mode tuning tables, input semantics, multiplayer fairness, integration with reload and swap systems, the Harbor Outpost refactor, a technique decision table, pitfalls, and a production checklist.

What fire mode selectors are (and are not)

Fire mode selectors answer: given one fire input, how many shots fire and at what cadence? They are distinct from:

  • Charge attacks — hold-to-power single releases, not sustained fire cadence.
  • Alt-fire underbarrel — separate weapon channels (grenade launcher) with their own ammo pools.
  • Fire rate upgrades — meta progression that changes one mode’s RPM globally, not player-toggleable modes.
  • Input buffering — when queued shots fire, not how many per press.

Real-world rifles expose selector switches; games abstract that into a keybind, scroll wheel segment, or weapon inspection animation. The design goal is readable tradeoffs: precision and ammo efficiency versus volume and suppression.

Mode taxonomy

Semi-automatic (semi-auto)

One shot per discrete trigger pull. Holding fire does not repeat until release and re-press (unless you deliberately implement auto-semi for accessibility). Best for: DMRs, pistols, medium-range precision, conserving ammo. Tuning knobs: trigger reset time, max semi RPM cap (prevents macro abuse), first-shot accuracy bonus.

Burst fire

Fixed N-round burst per trigger pull (commonly 2, 3, or 5). Firing stops when burst completes even if trigger remains held; next burst requires release or a refractory window. Variants:

  • Strict burst — always exactly N rounds.
  • Hyper burst — very high intra-burst RPM, slow between-burst cooldown (competitive SMGs).
  • Adaptive burst — fewer rounds if magazine low (rare; can confuse UI).

Full-automatic (full-auto)

Continuous fire while trigger held, subject to RPM cap and overheating rules. Best for: CQB, suppression, horde modes. Risk: ammo drain and uncontrollable bloom if not paired with recoil systems.

Less common modes

  • Binary / two-stage — light press semi, deep press auto (hardware-style; rare on mouse).
  • Slug or single-load — shotguns with switchable pellet vs slug (ammo type change, not RPM).
  • Safe / blocked — competitive rule sets that prevent accidental discharge in spawn.

Fire mode FSM and input semantics

Implement fire modes as a small state machine on the weapon instance, not scattered booleans in the player controller.

Core states

  • Idle — ready to accept fire input.
  • Firing — shot(s) in flight; respects RPM timer.
  • BurstActive — counting rounds toward burst quota.
  • Cooldown — between-burst or overheat recovery.
  • Reloading / Swapping — fire input ignored or cancels per your reload rules.

Mode switch behavior

When the player cycles modes mid-fight:

  • Finish current burst then switch (fair, predictable).
  • Instant switch on next shot boundary (common for competitive latency).
  • Animated switch with 200–400 ms commit (tactical sims); show HUD icon change immediately.

Persist selected mode per weapon slot in save data so players do not re-toggle every respawn unless design demands reset on death.

Input: hold vs tap

Semi and burst modes need clear input contracts. Semi on controller often uses hair triggers; on mouse, document that hold does nothing. Burst on hold can either fire one burst per press only, or repeat bursts while held after cooldown — the latter feels like “auto-burst” and must be tuned separately from full-auto RPM.

Per-mode tuning: RPM, damage, and recoil

Modes should not share one stat block with only RPM changed. Players perceive mode choice when each option has a distinct identity:

ParameterSemi typicalBurst typicalFull-auto typical
RPM feelPlayer-limited, cap ~360–450Intra-burst 900–1100, gap 0.3–0.5 s600–900 sustained
First-shot accuracyStrong bonusBonus on burst round 1Moderate or none
Recoil per shotLower vertical kickStacked then reset between burstsAccumulating bloom
Damage multiplier1.0–1.1× (precision reward)1.0×0.9× optional tradeoff
Ammo per kill (medium range)LowestMediumHighest

Tie recoil profiles to mode in data tables so designers can A/B without code changes. When ADS is active, apply mode-specific spread multipliers — burst often shines in mid-range ADS bands where full-auto bloom would punish tracking.

Ammo economy and encounter coupling

Fire mode is an ammo pacing lever. If full-auto TTK matches burst TTK but burns triple the rounds, corridor encounters become reload puzzles — which may be intentional, but must be authored with pickup placement and tactical reload windows.

  • Magazine sizing — burst-friendly mags often use multiples of burst count (30 = 10 bursts).
  • Reserve pools — semi-focused loadouts can carry fewer total rounds if damage per bullet is higher.
  • UI feedback — show mode icon, RPM readout in gunsmith, and optional “ammo to empty” on weapon inspect.
  • AI mirroring — enemies using burst at medium range teach players the same cadence.

Harbor Outpost refactor (worked example)

Problem: SMG corridor, three enemies, 30-round mag, full-auto only. Average engagement: 22 rounds fired, 11 hits, 1.8 reloads per squad, 58% wipe rate.

Changes:

  1. Added B / bumper cycle: semi → 3-round burst → full-auto with 150 ms switch delay on animation.
  2. Burst: 3× 95 damage at 1000 RPM intra-burst, 0.4 s between-burst recovery, −30% spread on round 1.
  3. Semi: 110 damage, 0.22 s min shot interval, full spread recovery between shots.
  4. Full-auto: unchanged DPS ceiling but −10% damage per bullet vs semi to reward precision.
  5. Tutorial prompt on first corridor entry; gunsmith default set to burst for SMG class.

Results: 19% wipe rate, 13 rounds average fired, 0.3 reloads per clearance, burst mode selected 71% of attempts after week one.

Multiplayer and competitive considerations

  • Mode switch latency must be identical across clients; no animation-gated advantage in ranked.
  • Macro detection — semi RPM caps and burst refractory windows limit single-key full-auto emulation.
  • Weapon class restrictions — some competitive rules ban full-auto on DMR slots; enforce in data, not UI alone.
  • Audio telegraph — distinct burst cadence helps counter-play and spectator readability.
  • Cross-platform — burst repeat-on-hold may need separate tuning for trigger stop vs mouse click.

Technique decision table

ApproachBest forWeak when
Semi-only weaponsSnipers, pistols, hardcore realismHorde modes needing volume
Burst-only (no full-auto)Competitive integrity, controller parityPower fantasy CQB fantasy
Full-auto onlyArcade shooters, young audiencesAmmo-scarce tactical corridors
Tri-mode selector per weaponTactical shooters, RPG gunplay depthFast TTK arena with 20+ weapons
Global fire-mode keybindPC muscle memory, esportsGamepad-only titles without paddles
Per-weapon inspect toggleImmersion, slower tactical simsRanked sub-second TTK duels
Manual trigger feather (no modes) Minimal UI, skill expression for expertsTeaching average players efficient cadence

Common pitfalls

  • Identical stats across modes — players never switch; selector becomes clutter.
  • Burst that is strictly worse DPS than full-auto — no reason to exist except achievements.
  • Mode reset on reload or swap — frustrates muscle memory; persist per slot.
  • Hidden switch delay in ranked — feels like input lag; show animation or remove delay.
  • Full-auto bloom without recoil recovery — modes cannot fix broken base spread.
  • No HUD indicator — players fire burst thinking semi and waste ammo.
  • Burst count not dividing mag size — awkward 29-round leftover burst behavior.
  • Accessibility gap — offer optional auto-burst or single-fire toggle for motor limitations without PvP advantage.

Production checklist

  • Define mode list per weapon class in data (semi / burst / auto).
  • Author per-mode RPM, damage, spread, and recoil tables.
  • Implement weapon-local fire FSM with burst counter and cooldown.
  • Specify mode switch policy (instant vs animated) per game mode.
  • Persist selected mode per weapon slot across sessions.
  • Bind cycle input with remapping support and gamepad parity.
  • HUD: mode icon, optional ammo-to-empty, switch feedback SFX.
  • Sync mode state in multiplayer replication.
  • Telemetry: mode usage, shots per kill, reload rate by encounter ID.
  • Playtest corridor + long-range on each mode; verify distinct roles.
  • Document semi RPM cap for anti-cheat review.
  • Gunsmith defaults and tutorial callout for new players.

Key takeaways

  • Fire modes change cadence and economy, not just a label — tune RPM, recoil, and damage per mode.
  • Burst bridges semi precision and auto volume — ideal for mid-range controller-friendly play.
  • FSM clarity prevents double-fire and reload bugs — centralize on the weapon instance.
  • Persist player mode choice — respect muscle memory across reloads and respawns.
  • Telemetry proves whether modes matter — if everyone stays on auto, rebalance or cut complexity.

Related reading