1.0.0
Compatibility
Changes
🛡️ CheckYourMods - v1.0.0 (Initial Release)
Welcome to the first stable release of CheckYourMods for Minecraft 1.21.1 (NeoForge)! This tool is essential for server administrators looking to maintain game integrity and transparency.
🚀 Key Features
🔍 Smart Anticheat Logic
- Metadata-Based Xray Detection: The mod automatically inspects player Resource Packs. If the
pack.mcmetafile contains suspicious keywords (e.g., xray, transparent, vision), administrators are immediately alerted. - Modlist Verification: Compares client-side mods with server-side mods. Any extra mod not found on the server or the whitelist will be reported.
- SHA-256 Fingerprinting: Generates and tracks unique hashes for every Resource Pack, allowing identification of cheat packs even if the player renames the file.
⚙️ Advanced Configuration
The mod generates a config file at serverconfig/checkyourmods-server.toml with the following options:
ALLOWED_MOD_IDS: A whitelist for utility mods (Optifine, Iris, Sodium, etc.) to prevent false positives.MANUAL_XRAY_HASHES: A manual database to flag or block specific pack hashes.
💻 Admin Commands
| Command | Description | Permissions |
|---|---|---|
/modcheck list |
Displays the current allowed mods on the server. | Everyone |
/modcheck packs |
Lists the resource pack hashes currently being watched. | Everyone |
🛠️ Technical Changes
- Persistent Logging: Implemented a detailed logging system found in
logs/checkyourmods-log.txt. - Visual Identity: Added the official logo to the Minecraft/NeoForge mod menu.
- Network Optimization: Information packets are sent asynchronously to prevent connection lag or TPS drops when players join.
📦 Installation
- Download the
.jarfile from the Releases section. - Place it in the
modsfolder of both your Client and Server. - Restart your game and enjoy a more secure environment!
Developed by Alber11 for the NeoForge community.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:mBtn08Gy:Ev5SDtVF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mBtn08Gy:Ev5SDtVF"
}

