g_splashDamageScale
jaPRO
Needs review. The inventory/provenance evidence is recorded, but some behavior, options, or attribution still lacks a direct user-facing source.
Controls g_splashDamageScale in the game module. Consult the cited behavior reads before relying on values not listed here.
At a glance
| Field | Value |
|---|---|
| Default | 1 |
| Value type | float |
| Restart | No latch flag is registered. |
| Manually settable | Yes |
| Cheat protected | No |
| Network scope | server-authoritative: Owned or enforced by the server. |
| Category | Gameplay & combat |
| Module | game |
| Renderer | All / not renderer-specific |
| Derivation | code-trace |
| Confidence | high |
| Added | 2023-12-11 in 9b57ee1b8 (how to compare this against your build) |
| In-game xdocs | No |
| In-game menu | No |
Values
No discrete value list is enforced or documented in the inspected source.
Flags
CVAR_ARCHIVE: saved to the user configuration
Provenance
Origin: jaPRO
- Ultimate-origin introduction:
9b57ee1b8566in jaPRO (content authored2023-12-11, integrated2023-12-11) - Origin pull request: #55
- Upstream registration evidence: codemp/game/g_xcvar.h:222
- Attribution method:
squash-feature-group-explicit-credit - Attribution confidence:
high - Notes: 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 |
|---|---|---|---|---|---|
| TaystJK | 2023-12-11 |
2023-12-11 | 2023-12-11 |
9b57ee1b8566 |
Shared integration commit |
| jaPRO | 2023-12-11 |
— | 2023-12-11 |
9b57ee1b8566 |
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-01-06 |
jaPRO | 668338988def · PR #79Japro update (#79) |
Changed an exact bound cvar-variable reference. codemp/game/g_weapon.c |
high |
2024-01-15 |
jaPRO | 7629ca86250a · PR #95Japro update (#95) |
Changed an exact bound cvar-variable reference. codemp/game/g_items.c, codemp/game/g_weapon.c |
high |
2024-01-31 |
jaPRO | a5c04e80d08f · PR #127Japro updates (#127) |
Changed an exact bound cvar-variable reference. codemp/game/g_weapon.c |
high |
2024-02-03 |
jaPRO | 97cd4091c2ca · PR #129Japro update (#129) |
Changed an exact bound cvar-variable reference. codemp/game/g_weapon.c |
high |
Evidence
- registration: codemp/game/g_xcvar.h:221 (XCVAR_DEF)
- behavior: codemp/game/g_items.c:1511
- behavior: codemp/game/g_weapon.c:648
- behavior: codemp/game/g_weapon.c:1341
- behavior: codemp/game/g_weapon.c:1781
- behavior: codemp/game/g_weapon.c:2657
Generated from source commit c722804317d7 on 2026-09-28. Anything merged after that is not reflected here.