clankick

EternalJK

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

Runs Svcmd_ClanKick_f in the game module.

At a glance

Arguments and gating

No verified argument schema is available beyond the syntax shown above.

Provenance

Origin: EternalJK

• Ultimate-origin introduction: fa2b5ba6883b in EternalJK (content authored 2018-08-09, integrated 2018-08-20)
• Upstream registration evidence: codemp/game/g_svcmds.c:1637
• 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.

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.

Evidence

• registration: codemp/game/g_svcmds.c:1666 (game-console command table)
• handler: codemp/game/g_account.c:3226