naive implementation opens door to amplification attacks

[Intege-rs]

Lacks error correction, nor do you have any kind of handshake to validate the return Ip address is actually someone who wants this information. opening yourself to amplification attacks. a less naive approach would be to build on top of the already existing QUIC implementation and register your own alpn. you also blindly send the entire player list and plugin list without checking if its too large for a UDP packet.

[Sceri]

Thanks for the feedback! These were valid concerns with v1. We've addressed all of them in v2.0.0:

Amplification attacks - V2 now requires a challenge-response handshake before any data is returned
Large player lists - V2 implements pagination with MTU-aware packet sizing
Protocol design - While building on QUIC is an option, we intentionally kept this as a simple stateless UDP protocol.

The v1 protocol is still supported for backwards compatibility but can be disabled via LegacyProtocolEnabled: false.