`g_movementStyle`

jaPRO

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

Force movement style for players. 0=SIEGE 1=JKA 2=QW 3=CPM 4=Q3 5=PJK 6=WSW

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	`1`
Value type	`enum`
Restart	No latch flag is registered.
Cheat protected	No

Values

Value	Meaning	Evidence
`0`	SIEGE.	docs/japro_docs.md:53
`1`	JKA.	docs/japro_docs.md:53
`2`	QW.	docs/japro_docs.md:53
`3`	CPM.	docs/japro_docs.md:53
`4`	Q3.	docs/japro_docs.md:53
`5`	PJK.	docs/japro_docs.md:53
`6`	WSW.	docs/japro_docs.md:53

Flags

CVAR_ARCHIVE — saved to the user configuration

Provenance

Origin: jaPRO

Ultimate-origin introduction: d9d510063ce6 in jaPRO (content authored 2014-01-11, integrated 2018-01-01)
Upstream registration evidence: codemp/game/g_xcvar.h:234
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-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
`2018-02-05`	EternalJK	`675e97128f48` Merge remote-tracking branch ‘eternalcodes/master’	Changed an exact bound cvar-variable reference. `codemp/game/g_cmds.c`	`medium`
`2018-07-22`	EternalJK	`fae0fd307416` Merge branch ‘feature/update-game’ into develop	Changed an exact bound cvar-variable reference. `codemp/game/bg_pmove.c`, `codemp/game/g_active.c`, `codemp/game/g_cmds.c`	`medium`
`2019-02-01`	EternalJK	`08ee038fa4de` Allow onlybhop target_restrict change force jump level with count value,	Changed an exact bound cvar-variable reference. `codemp/game/g_active.c`	`medium`
`2020-06-15`	EternalJK	`c635b474e0de` cgame updates for coop defrag	Changed an exact bound cvar-variable reference. `codemp/game/bg_pmove.c`	`medium`
`2023-12-11`	jaPRO	`9b57ee1b8566` · PR #55 Japro update (#55)	Changed an exact bound cvar-variable reference. `codemp/game/bg_pmove.c`, `codemp/game/g_active.c`, `codemp/game/g_cmds.c`	`high`
`2024-03-05`	TaystJK	`9912f30e367f` · PR #166 Japro update (#166)	Changed an exact bound cvar-variable reference. `codemp/game/ai_main.c`	`medium`
`2024-03-20`	TaystJK	`fd60c90af33d` bot cap routes	Changed an exact bound cvar-variable reference. `codemp/game/ai_main.c`	`medium`
`2024-03-20`	TaystJK	`30454fc96fad` bot cap ai tweak, crashfix?	Changed an exact bound cvar-variable reference. `codemp/game/ai_main.c`	`medium`

Evidence

registration: codemp/game/g_xcvar.h:233 (XCVAR_DEF)
behavior: codemp/game/ai_main.c:8949
behavior: codemp/game/ai_main.c:9017
behavior: codemp/game/bg_pmove.c:447
behavior: codemp/game/bg_pmove.c:449
behavior: codemp/game/bg_pmove.c:451
documentation: docs/japro_docs.md:53