Protectcord

Added

• Floodgate/GeyserMC support — Bedrock players connecting through Geyser are no longer incorrectly blocked by proxy, datacenter, or VPN detection. ProtectCord now detects Floodgate at runtime via reflection (zero compile-time dependency) and applies configurable bypasses for identified Bedrock players
• New compatibility.floodgate config section with granular control:
  • bypass-proxy-check (default: true) — Geyser acts as a proxy, so Bedrock connections are flagged as proxies
  • bypass-datacenter-check (default: true) — Cloud-hosted Geyser flags connections as datacenter IPs
  • bypass-vpn-check (default: false) — Disabled by default for security
  • exempt-account-per-ip (default: true) — Critical for standalone Geyser where all Bedrock players share one IP
  • log-detection (default: true) — Shows active bypass settings on startup
• Config migration v1 to v2 — Existing configs automatically gain the new Floodgate options with sensible defaults on upgrade
• Added floodgate to soft-dependencies on all platforms

Notes

• Tor, Bogon, and geo-blocking checks are never bypassed for Bedrock players
• Floodgate must be installed alongside Geyser for player detection to work
• Forge platform is unaffected (no chat/compat changes)