`sv_newfloodProtect`

jaPRO

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

Use new method of delaying commands with flood protection

At a glance

Field	Value
Category	Server & networking
Module	`engine-server`
Also registered in	`engine-server`
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	`bool`
Restart	No latch flag is registered.
Cheat protected	No

Values

Value	Meaning	Evidence
`0`	Disabled.	codemp/server/sv_client.cpp:1564
`1`	Enabled.	codemp/server/sv_client.cpp:1564

Flags

CVAR_ARCHIVE — saved to the user configuration

Provenance

Origin: jaPRO

Ultimate-origin introduction: d9d510063ce6 in jaPRO (content authored 2017-12-22, integrated 2018-01-01)
Upstream registration evidence: codemp/server/sv_init.cpp:997
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	`2017-12-22`	—	`2018-01-01`	`d9d510063ce6`	Shared integration commit
TaystJK	`2017-12-22`	—	`2018-01-01`	`d9d510063ce6`	Shared integration commit
jaPRO	`2017-12-22`	—	`2018-01-01`	`d9d510063ce6`	Ultimate origin
Vulkan	`2017-12-22`	—	`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-25`	EternalJK	`3e6223fcaa69` optimize new floodprotect, fix cvar description	Changed registration, default, flags, module, renderer scope, handler, or gating. `codemp/server/sv_init.cpp`	`medium`
`2018-10-19`	EternalJK	`bc4c013bbe7d` these dont need to be serverinfo?	Changed registration, default, flags, module, renderer scope, handler, or gating. `codemp/server/sv_init.cpp`	`medium`

Evidence

registration: codemp/server/sv_init.cpp:997 (Cvar_Get)
behavior: codemp/server/sv_client.cpp:1564
behavior: codemp/server/sv_client.cpp:1602