`cl_discordRichPresence`

EternalJK

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

Allow/disallow sharing current game information on Discord profile status

At a glance

Field	Value
Category	Engine & diagnostics
Module	`engine-client`
Also registered in	`engine-client`
Renderer	All / not renderer-specific
Network scope	`client-only` — Local to the client/UI/renderer.
Derivation	`documented`
Confidence	`medium`
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/client/cl_discordrpc.cpp:152
`1`	Enabled.	codemp/client/cl_discordrpc.cpp:152

Flags

CVAR_ARCHIVE — saved to the user configuration

Provenance

Origin: EternalJK

Ultimate-origin introduction: 1bcb29af6443 in EternalJK (content authored 2019-03-19, integrated 2019-03-19)
Upstream registration evidence: codemp/client/cl_main.cpp:3360
Attribution method: shared-earliest-commit-lineage-order
Attribution confidence: medium
Notes: The earliest authored/submitted introduction is shared by eternaljk, taystjk, japro, vulkan; fork-lineage order selects eternaljk.

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	`2019-03-19`	—	`2019-03-19`	`1bcb29af6443`	Ultimate origin
TaystJK	`2019-03-19`	—	`2019-03-19`	`1bcb29af6443`	Shared integration commit
jaPRO	`2019-03-19`	—	`2019-03-19`	`1bcb29af6443`	Shared integration commit
Vulkan	`2019-03-19`	—	`2019-03-19`	`1bcb29af6443`	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
`2019-03-19`	EternalJK	`ad1655124ccf` Discord lib handling cleanup	Changed an exact bound cvar-variable reference. `codemp/client/cl_main.cpp`	`medium`
`2019-03-19`	EternalJK	`46ae589c3b8f` Show idle status (orange bubble) only when idle for 5+ minutes or if [AFK] tag has been set	Changed an exact bound cvar-variable reference. `codemp/client/cl_discordrpc.cpp`	`medium`
`2019-03-21`	EternalJK	`580de0259290` Discord status will show “Playing demo”/”Playing offline”/”Spectating on”/”Playing on”	Changed an exact bound cvar-variable reference. `codemp/client/cl_discordrpc.cpp`	`medium`
`2019-03-21`	EternalJK	`f6c6472650cc` Discord RPC integration	Changed an exact bound cvar-variable reference. `codemp/client/cl_discordrpc.cpp`	`medium`
`2019-03-21`	EternalJK	`6c98db92ff8c` Remove pointless gametype argument from Discord status functions	Changed an exact bound cvar-variable reference. `codemp/client/cl_discordrpc.cpp`	`medium`

Evidence

registration: codemp/client/cl_main.cpp:3459 (Cvar_Get); condition defined(DISCORD) && !defined(_DEBUG)
behavior: codemp/client/cl_discordrpc.cpp:152
behavior: codemp/client/cl_discordrpc.cpp:225
behavior: codemp/client/cl_discordrpc.cpp:246
behavior: codemp/client/cl_discordrpc.cpp:474
behavior: codemp/client/cl_discordrpc.cpp:485