Server-side tool that inspects what mods and resource packs a connecting client has loaded. Uses a network channel handshake: clients that don't have the mod installed are disconnected after a 10-second timeout. Clients with blacklisted files are kicked immediately.
Verification Flow
- Player connects — server validates the client has the mod
- Server requests the client's loaded mod list and active resource packs
- If the client doesn't respond within 10 seconds → disconnected
- Server checks each filename (substring match) and SHA-256 hash against the blacklist
- Any match → immediate kick with a specific reason message
Configuration
Blacklist managed via config/sarosmodchecker-blacklist.json:
{
"blacklistedNames": [
"xray",
"cheat-client"
],
"blacklistedHashes": [
"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855"
]
}
blacklistedNames— substring match against filename (case-insensitive). Any mod or resource pack filename containing these strings is flagged.blacklistedHashes— exact SHA-256 hash match. Useful for blocking specific file versions regardless of filename.
Mod List Export
On every server startup, the mod generates a full report of loaded server-side mods at [ServerRoot]/modlist.md — a markdown table with Mod Name, ID, Version, and SHA-256 hash.
Commands
/checkclientmods <player> (OP Level 2)
Retrieves and displays the full mod and resource pack list for an online player, including SHA-256 hashes. Useful for manually auditing a suspicious player or debugging hash mismatches.
Note: This wiki serves as documentation. For active discussion, please join the Discord Server.
