FAQ and Support

FAQ and Support

Does every player need Hidder?

Java players who must pass verification need the matching Hidder/Fabric setup. Being an operator does not grant a verification bypass. A ModSeeker whitelist entry or an enabled, positively identified Floodgate bypass does. See Commands and Permissions and Floodgate and Bedrock.

Can vanilla, Forge or NeoForge clients pass these checks?

They cannot complete the required Hidder flow as supplied by this release. Hidder is a Fabric client mod for Windows x64. A bypass is an explicit server decision, not verification support for another platform.

Does Hidder work on macOS, Linux or mobile Java launchers?

No. Hidder's native library is built for Windows x64, so macOS, Linux and Android/iOS Java launchers are not supported.

Does one Hidder JAR work on every supported Minecraft version?

No. Choose the JAR for the client's Minecraft target. Within that target, the v3 JAR accepts the three supported Fabric Loader versions. Fabric API is a separate dependency that must match Minecraft. See Installation and Compatibility.

Can I require an exact modpack?

Advanced mode approves reported file hashes. It does not require every allowlisted file to be installed. If you need a mandatory exact pack, do not treat this allowlist alone as that check. Verification Modes explains the difference.

Why did a mod update cause a new rejection?

An updated or repacked JAR normally has different bytes and therefore a different hash. Review and approve the new file in advanced mode. Remove the old approval if you no longer want that version accepted. Keep the old JAR available privately if you may need to roll back.

Why is a dependency blocked when I never installed it separately?

A mod can bundle another mod or library inside its JAR. Normal mode checks those declared bundled IDs too. Check which installed mod contains the ID and decide whether the rule should apply. Do not remove libraries at random; see Policies and Lists.

Will adding a blacklist rule kick someone already online?

No automatic recheck is scheduled for an already verified player. The rule applies to subsequent checks. Disconnect/reconnect a test client to verify a change, or remove the player's current connection yourself if you need the new rule applied immediately.

Why is the mod list missing even though the player joined?

For missing console output, check showModList. It controls logging, not the report cache. If seek mod has no report, check whether mod verification is disabled, the player bypasses verification, or the client failed before submitting a valid report. Launcher-only verification has no mod report. seek mod requires the player to be online; it is not a live scan command.

Can I let an unknown launcher join without disabling mod checks?

Yes. Keep mod verification enabled and set launcherVerification.allowUnknownClients: true if that is your policy. This permits the unknown label; it does not allow recognized disabled launchers or clients without Hidder. See Launcher Verification.

Can players see each other's mod lists or open the GUI?

Commands are operator-only by default. A trusted player needs the relevant permission to inspect cached lists. The GUI starts only from the console, and its temporary link grants access to whoever holds it. See Commands and Permissions and Web GUI.

What does Hidder send, and who can see it?

The connected server receives the relevant mod IDs, advanced-mode hashes, requested launcher label and verification metadata. Server administrators can read the reports. Configured Discord events can forward player and report information. Security Overview and Discord Alerts list the data; encryption does not make a report private from the receiving administrator.

Do players need extra system software?

The release JAR includes the native library and does not need a separate OpenSSL or compiler installation. Players need the supported Windows x64/Fabric client setup described in Installation and Compatibility.

Can ModSeeker report resource packs or shaders?

Resource-pack and shader-pack reporting are not v3 features. The report covers mod JARs and the requested launcher information. It does not include hardware IDs. See Security Overview for the data fields.

Does ModSeeker replace an anti-cheat?

It checks reported mod files and launcher information against server policy. It does not detect every form of cheating or replace server-side gameplay checks. See Security Overview for the protections it does provide.

How do I report a problem?

Follow Troubleshooting first. If it still fails, search the relevant ModSeeker issues or Hidder issues, then include:

1. Server Minecraft/Paper and Java versions; ModSeeker filename.
2. Client Minecraft, Java, Fabric Loader and Fabric API versions; Hidder filename and launcher.
3. Active verification settings, any proxy/container setup, and whether the issue affects one or every player.
4. The exact message, the steps that produce it, what you expected, and the relevant server/client log excerpt from that connection.
5. For a policy problem, the affected mod ID and JAR version. State whether a dependency is bundled; do not upload an entire modpack as the first report.

Remove private keys, webhook URLs, active GUI links/tokens, player IP addresses, account tokens and identifying local paths. Share only relevant config settings rather than your whole server backup. For a suspected vulnerability, ask the maintainer for a private reporting route without posting reproduction details in the public issue.