Quick Start

Quick Start

This walkthrough sets up normal mod-ID verification, confirms a clean join, and tests one blacklist rule.

1. Install the server plugin

Choose the ModSeeker build for your server:

Paper family	ModSeeker file	Java
1.21.x	modseeker-3.0.0+java21.jar	21
26.x	modseeker-3.0.0+java25.jar	25

Stop the server, place one ModSeeker JAR in plugins/, and start it again. Look for ModSeeker's startup summary and Ready message. It creates plugins/ModSeeker/ with its configuration and data files.

2. Prepare one test client

Use a supported Windows x64 client with a Hidder JAR for that exact Minecraft version. Install one of the supported Fabric Loader versions and the matching Fabric API. Put Hidder and Fabric API in the instance's mods/ folder.

Installation and Compatibility lists the versions and explains which component goes where.

3. Check the settings

For this walkthrough, use:

ModVerification: true
advancedModVerification: false
showModList: true
launcherVerification:
  enabled: false

These are the relevant defaults. If you edit an existing file, keep its other sections and indentation. Apply edits with:

/modseeker reload

The test player must not be on ModSeeker's verification-bypass whitelist. An operator still needs Hidder unless that identity has an explicit bypass.

4. Confirm a successful join

Join with the test client. The console should show Hidder presence, a mod list and Verification passed for .... The player should be able to move after verification finishes.

To inspect the connected player's cached list:

/modseeker seek mod <player>

If this first join fails, use Troubleshooting before adding policy rules.

5. Test a blacklist rule

Choose the ID of a harmless test mod that is actually present in the client report. examplemod below is a placeholder; replace it with that ID.

/modseeker modblacklist add examplemod

Ask the test player to disconnect and reconnect. The server should reject that connection and name the blocked mod. Adding a rule does not automatically kick players who are already verified online.

Remove the test rule and reconnect again:

/modseeker modblacklist remove examplemod

The clean join should pass again. Command changes are saved immediately; these add/remove commands do not need a reload.

Next steps

Use Policies and Lists to build your real rules, or Web GUI to manage them in a browser. Every command above is available to operators by default. The GUI command itself must run in the server console.