`g_saberDisable`

jaPRO

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

Configured with /saberDisable command.

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	No latch flag is registered.
Cheat protected	No

Values

Value	Meaning	Evidence
`1`	No blue	codemp/game/g_local.h:296
`32`	Desann only	codemp/game/g_local.h:301
`64`	Tavion only	codemp/game/g_local.h:302
`2`	No yellow	codemp/game/g_local.h:297

Flags

CVAR_ARCHIVE — saved to the user configuration

Provenance

Origin: jaPRO

Ultimate-origin introduction: d9d510063ce6 in jaPRO (content authored 2014-11-21, integrated 2018-01-01)
Upstream registration evidence: codemp/game/g_xcvar.h:202
Attribution method: squash-feature-group-explicit-credit
Attribution confidence: medium
Notes: The earliest authored/submitted introduction is shared by eternaljk, taystjk, japro, vulkan; fork-lineage order selects eternaljk. The identifier’s single-prefix squash feature group explicitly credits 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-11-21`	—	`2018-01-01`	`d9d510063ce6`	Shared integration commit
TaystJK	`2014-11-21`	—	`2018-01-01`	`d9d510063ce6`	Shared integration commit
jaPRO	`2014-11-21`	—	`2018-01-01`	`d9d510063ce6`	Ultimate origin
Vulkan	`2014-11-21`	—	`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-11`	jaPRO	`9b57ee1b8566` · PR #55 Japro update (#55)	Changed an exact bound cvar-variable reference. `codemp/game/g_active.c`	`high`
`2023-12-14`	jaPRO	`0bf81a8695ce` Since jaPRO added MV_OCPM and MV_TRIBES after MV_COOP_JKA, we have to shuffle some things around. MV_COOP was originally designed to support multiple additional physics than just jka, but this never panned out. Need to revert this change if that design ever makes a comeback.	Changed an exact bound cvar-variable reference. `codemp/game/g_active.c`	`high`
`2024-01-09`	jaPRO	`b5dff40126c7` · PR #82 Japro update (#82)	Changed an exact bound cvar-variable reference. `codemp/game/g_active.c`	`high`
`2024-01-17`	TaystJK	`c3293a76c178` · PR #100 conc sniper uses energy like phase rifle, mortar FX tweak, bounce strength (#100)	Changed an exact bound cvar-variable reference. `codemp/game/g_active.c`	`medium`
`2024-02-27`	jaPRO	`0683da475d2a` [jaPRO/Tribes] Fixup tribes check	Changed an exact bound cvar-variable reference. `codemp/game/g_active.c`	`high`

Evidence

registration: codemp/game/g_xcvar.h:201 (XCVAR_DEF)
behavior: codemp/game/g_active.c:3482
behavior: codemp/game/g_active.c:3505
behavior: codemp/game/g_active.c:3508
behavior: codemp/game/g_active.c:3512
behavior: codemp/game/g_active.c:3516
documentation: docs/japro_docs.md:21