BetterModVerifier

A simple mod verification that uses a whitelist of allowed mods. It is designed to be used on a host to prevent players from using unauthorized mods.

Features

• Check if players joining your room have the same mods installed.
• Show a notification when a mod mismatch is detected.
• Kick clients that have different mods than the host whitelist.
• Customizable mod whitelist file.
• Detailed logging of verification results to verifier_result.log in the whitelist file directory.

Configuration

Mod whitelist file default path: C:/Users/<YourUsername>/AppData/LocalLow/LandCrab/PEAK/BetterModVerifier/verified_mods.json

Host-only ignored mod file default path: C:/Users/<YourUsername>/AppData/LocalLow/LandCrab/PEAK/BetterModVerifier/ignored_mods.json

ignored_mods.json entries only need name and guid. Matching is by guid. Ignored mods are filtered before whitelist creation and verification, so host-only mods do not become required client mods.

Config is host-only, clients changes will not affect and always use the host's config.

Verification modes:

• ExactMatch (default): the player's mod set must exactly match the host whitelist.
• AllowExtra: every whitelist mod must exist in the player's mod set, but additional player mods are allowed.

When the whitelist contains at least one mod, an empty player mod set always fails verification.

Tips

• KickUnverifiedPlayers may be kick incorrectly if the client's network connection is bad and the mod info packet is not received in time. Ensure you have zero tolerance for players who fail verification; otherwise, it's recommended to manually check verifier_result.log instead of enabling this setting.