ModernUO/Projects/Server/Network/NetState
Kamron Batman b6c0a0bde8
docs: tighten comments to the non-obvious why
Cuts explanation that restated the code or repeated itself, and keeps the parts
a future change would otherwise undo.

The same fact was asserted in three places: BanChannel.IsExempt, BanExemptions
and LoginAllowlist each explained that an exemption withholds escalation only.
It now lives on the seam that defines it, and the other two point at it.

The seed short-read comment was eight lines arguing a decision; the load-bearing
part is that waiting costs a connection slot per one- or two-byte client, so
that is what it says now. The new test-collection markers are one line each
rather than a summary of how STArrayPool works internally.

Also drops a fully-qualified System.Func in BanExemptions in favour of a using.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-07-30 18:40:02 -07:00
..
DumpNetStates.cs fix: Bumps deps. Updates copyrights (#2353) 2026-03-05 19:36:54 -08:00
NetState.ClientVersion.cs fix: Bumps deps. Updates copyrights (#2353) 2026-03-05 19:36:54 -08:00
NetState.cs docs: tighten comments to the non-obvious why 2026-07-30 18:40:02 -07:00
NetState.Movement.cs feat: Adds robust speed hack detection and movement throttling (#2266) 2026-03-07 11:44:37 -08:00
NetState.Network.cs feat(network): allowlist false-positive IPs, escalate on behaviour 2026-07-30 18:31:34 -07:00
ProtocolChanges.cs fix: Bumps deps. Updates copyrights (#2353) 2026-03-05 19:36:54 -08:00