Verification Modes

Verification Modes

ModSeeker has two alternative mod policies. Launcher verification is a separate switch that can accompany either policy.

Setting combinations

ModVerification	advancedModVerification	launcherVerification.enabled	Result
true	false	false	Mod-ID blacklist.
true	true	false	SHA-512 file-hash allowlist.
true	Either	true	The selected mod policy and launcher policy must both pass.
false	Ignored for mod checking	true	Launcher verification only; no mod-report policy check.
false	Either	false	Non-bypassed players are denied.

The player whitelist and enabled Floodgate bypasses are evaluated before these checks.

Normal mode: blocked mod IDs

ModVerification: true
advancedModVerification: false

Normal mode checks reported mod IDs against data/modblacklist.json. It also checks IDs declared inside bundled mod JARs. Unlisted, identifiable mods are allowed.

A blocked dependency can reject its enclosing mod. Read the reported ID before choosing a rule: blocking a shared library can affect several otherwise unrelated mods.

Advanced mode: approved file hashes

ModVerification: true
advancedModVerification: true

Every reported mod JAR hash must be approved in data/modallowlist.json. The enclosing JAR's hash covers its bundled contents. Updating or repacking a JAR changes its hash even if its mod name is unchanged.

This policy checks that the reported files are approved. It does not require the player to install every file in your allowlist, so it is not an exact required-modpack checker.

Prepare the allowlist before admitting regular players. ModSeeker tries to refresh essential Hidder and Fabric API entries from Modrinth when advanced mode starts or reloads. Verify that refresh succeeded and approve the other intended files. Policies and Lists covers local and player-report imports.

The mod-ID blacklist is dormant in advanced mode. Keeping an ID there does not add an extra blacklist check on top of hash verification.

Launcher checks

Enable launcherVerification.enabled only after choosing the allowed entries in client-list.yml. All generated launcher entries begin disabled. Launcher Verification explains unknown labels and client requirements.

Mod-count limit

enableModCountThreshold: true applies maxModCount in either mod mode. It counts reported top-level IDs, not every nested dependency or physical file. It has no mod-report effect in launcher-only mode.

While a player is being checked

ModSeeker holds unverified players by restricting movement and selected interactions until approval. This is an in-game verification hold, not a separate lobby or a replacement for proxy access controls. Successful verification releases the player and can send the configured welcome message.

Policy edits are used by subsequent checks. Reconnect a test player after changing modes or lists; reloading alone does not reverify everyone online.