g_neutralFlag

jaPRO

Selects a neutral-flag game mode. Values 1 to 3 are rabbit variants for FFA and team FFA; values 4 to 6 are one-flag CTF variants for the CTF gametype, and a value outside a gametype’s range leaves that gametype’s normal flags in place. Changing the value swaps the flags immediately through CVU_Rabbit, without a map restart. Every mode needs a map with a team_CTF_neutralflag, and the one-flag modes also need trigger_multiple capture zones: spawnflag 16384 for values 4 and 5, spawnflag 32768 for value 6. The stock maps have neither. g_neutralFlagTimer sets how long a capture takes.

At a glance

Field Value
Default 0
Value type enum
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 2024-01-03 in c644ae832 (how to compare this against your build)
In-game xdocs No
In-game menu No

Values

Value Meaning Evidence
0 Off. The map’s neutral flag is removed at load, and CTF keeps its red and blue flags. codemp/game/g_items.c:3160
1 Rabbit, in FFA and team FFA: a neutral flag spawns and players fight to carry it. codemp/game/g_cvar.c:472
2 Sniper rabbit: as 1, but picking up the flag leaves the carrier with only a disruptor and 300 ammo. codemp/game/g_team.c:1181
3 Rabbit where the carrier scores a point for every five seconds they hold the flag. codemp/game/g_active.c:1783
4 One-flag CTF: score by holding the neutral flag inside your own team’s capture zone for g_neutralFlagTimer. codemp/game/g_trigger.c:212
5 One-flag CTF: score by holding the neutral flag inside the other team’s capture zone for g_neutralFlagTimer. codemp/game/g_trigger.c:214
6 One-flag CTF with capture points: bringing the neutral flag into a team’s capture point puts that team’s flag at its base, and the team scores when g_neutralFlagTimer runs out unless the other team takes that flag first. codemp/game/g_trigger.c:234

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
TaystJK 2024-01-03 2024-01-03 2024-01-03 c644ae832bad Shared integration commit
jaPRO 2024-01-03 — 2024-01-03 c644ae832bad 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-04 jaPRO cab839d15251 · PR #77
Japro update (#77)
Changed an exact bound cvar-variable reference. codemp/game/g_team.c high
2024-01-07 jaPRO 931f5d5c9044 · PR #80
Japro update (#80)
Changed an exact bound cvar-variable reference. codemp/game/g_combat.c high
2024-01-31 jaPRO a5c04e80d08f · PR #127
Japro updates (#127)
Changed an exact bound cvar-variable reference. codemp/game/g_team.c high
2024-03-13 jaPRO b4aeeea9c16c · PR #176
Japro update (#176)
Changed an exact bound cvar-variable reference. codemp/game/g_combat.c high
2024-05-15 jaPRO 93c2c1a5b4ef · PR #201
Japro update (#201)
Changed an exact bound cvar-variable reference. codemp/game/g_cvar.c, codemp/game/g_items.c, codemp/game/g_main.c and 2 more high

Evidence

Generated from source commit c722804317d7 on 2026-09-28. Anything merged after that is not reflected here.