Floodgate and Bedrock

Floodgate and Bedrock

Bedrock clients cannot install the Hidder Fabric mod. ModSeeker can bypass its checks for connections identified as Bedrock by the Floodgate API.

allowFloodgate: true

This is the default. It is a bypass of launcher and mod verification, not a Bedrock mod-report implementation.

Paper with Geyser and Floodgate

Install and configure the relevant Geyser/Floodgate components, then restart the server. Follow the official Floodgate setup for your platform and authentication settings.

Floodgate must be enabled and expose a working API to the Paper server running ModSeeker. Installing Geyser alone does not provide this identity check. A name prefix is not used as proof that someone is a Bedrock player.

Behind a proxy

Because ModSeeker calls the API on the Paper backend, a proxy-only Floodgate installation is not enough for this bypass. Configure Floodgate's backend API support and player forwarding using its backend setup instructions.

Keep backend access restricted to the intended authenticated forwarding path. Follow Floodgate's instructions for its key files; they must stay private. Restart the affected components after installing or changing their integration.

Verify the result

1. Start the server and check whether ModSeeker reports that the Floodgate bypass is available.
2. Join with a real Bedrock connection through the configured Geyser route. It should bypass Hidder checks.
3. Join with a non-bypassed Java client. It should still need Hidder.

If Floodgate is unavailable or the API lookup fails, ModSeeker logs a warning and treats the connection as Java. It does not guess from a username or silently bypass verification.

With allowFloodgate: false, those players need the normal verification flow, which a Bedrock client cannot complete. Do not turn this setting off expecting Bedrock mod scanning.