ModSeeker

!ModSeeker — Your server, your policy. Paper plugin for mod and launcher checks.

Wiki · Commands · Source · Report an issue

ModSeeker is a Paper plugin for checking players' mods and launchers. It works with Hidder to block unwanted mods, check approved mod files, and apply optional launcher restrictions when players join your server.

  <h3>Mod detection</h3>
  <p>Block mods by ID, or allow only approved mod files. Checks include mods declared inside other mod JARs.</p>
</td>
<td align="center" width="50%" valign="top">
  
  <h3>Client &amp; launcher detection</h3>
  <p>Choose which detected launchers can join, and whether to accept unknown launchers.</p>
</td>

Features

In action

Block a mod in the web panel and enforce the rule when the player reconnects.

Compatibility

Install ModSeeker on the Paper server and Hidder on the players' clients. The Windows x64 requirement applies to Hidder, not to the server.

Getting started

1. Download the ModSeeker build for your server's Java version and put it in plugins/.
2. Have Java players install the matching Hidder, Fabric Loader and Fabric API versions.
3. Start the server, then choose your rules in plugins/ModSeeker/config.yml. Mod-ID checks are enabled by default; launcher verification is optional.
4. Run /modseeker reload after configuration changes. To open the web panel, run modseeker gui in the server console and follow the printed link.

Commands require operator permissions by default. You can grant modseeker.admin or individual command permissions to trusted staff. The GUI command is console-only, and its expiring access link should stay private.

Mod lists are logged to the console by default; set showModList: false to turn that off. Use /modseeker seek mod <player> to inspect an online player's cached report.

For commands, policy examples, remote panel access and troubleshooting, see the ModSeeker Wiki. Hidder's documentation explains what the client reports to the server.

Licence

AGPL-3.0-or-later · Third-party licences