g_flagDrag

jaPRO

Needs review. The inventory/provenance evidence is recorded, but some behavior, options, or attribution still lacks a direct user-facing source.

Add air friction to flag carrier.

At a glance

Field Value
Category Gameplay & combat
Module game
Also registered in game
Renderer All / not renderer-specific
Network scope server-authoritative — Owned or enforced by the server.
Derivation documented
Confidence medium
In-game xdocs No
In-game menu No
Default 0
Value type float
Restart No latch flag is registered.
Cheat protected No

Values

No discrete value list is enforced or documented in the inspected source.

Flags

Provenance

Origin: jaPRO

Dated project introductions

Authored dates come from the exact registration’s first content commit, PR dates identify when work was proposed to each project, and integration dates come from each first-parent mainline. A project merging first does not override earlier upstream authorship or submission.

Project Authored PR opened Integrated Commit Relationship
EternalJK 2014-01-11 2018-01-01 d9d510063ce6 Shared integration commit
TaystJK 2014-01-11 2018-01-01 d9d510063ce6 Shared integration commit
jaPRO 2014-01-11 2018-01-01 d9d510063ce6 Ultimate origin
Vulkan 2014-01-11 2018-01-01 d9d510063ce6 Shared integration commit

Later changes

These commits occur after the ultimate-origin introduction on TaystJK’s inherited first-parent lineage. Registration evidence is exact; behavior evidence requires a changed bound cvar reference or a changed registered command-handler hunk.

Date Change source Commit / subject Evidence Confidence
2023-12-21 jaPRO edec69cec7d0 · PR #58
Japro update (#58)
Changed an exact bound cvar-variable reference. codemp/game/bg_pmove.c high

Evidence