g_unlagged

jaPRO

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

Bitvalue. 1=Unlagged projectiles. 2=Unlagged hitscan. 4=Unlagged push/pull.

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 bitmask
Restart Yes; the value is latched.
Cheat protected No

Values

Value Meaning Evidence
1 Unlagged projectiles. docs/japro_docs.md:88
2 Unlagged hitscan. docs/japro_docs.md:88
4 Unlagged push/pull. docs/japro_docs.md:88

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
2024-01-03 jaPRO 9e120086add8 · PR #71
Japro update (#71)
Changed an exact bound cvar-variable reference. codemp/game/g_missile.c high
2024-05-28 jaPRO 87145eba654c · PR #206
Japro update (#206)
Changed an exact bound cvar-variable reference. codemp/game/g_weapon.c high

Evidence