g_fixSaberMoveData

TaystJK

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

Controls g_fixSaberMoveData in the game module. Consult the cited behavior reads before relying on values not listed here.

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 code-trace
Confidence high
In-game xdocs No
In-game menu No
Default 1
Value type bool
Restart No latch flag is registered.
Cheat protected No

Values

Value Meaning Evidence
0 Disabled. codemp/game/bg_saber.c:356
1 Enabled. codemp/game/bg_saber.c:356

Flags

Provenance

Origin: TaystJK

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
TaystJK 2023-10-08 2023-10-28 2023-10-29 530446764ef0 Ultimate origin
jaPRO 2023-10-08 2023-10-29 530446764ef0 Shared integration commit
OpenJK 2024-02-20 2024-02-20 142e0b71cca8 Other project appearance
rend2 2024-02-20 2024-04-09 b688bdf3ea00 Other project appearance

Immediate port-source credit: OpenJK. The earlier dated project remains the ultimate origin.

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-02-26 TaystJK cd784cbf26da · PR #157
Upstream update (#157)
Changed an exact bound cvar-variable reference. codemp/game/g_cvar.c medium

Evidence