Links
Tags
Creators
Details
paper-1.0
Compatibility
Changes
Provides server‑side enforcement, logging, and admin tools to ensure fair play and transparency.
Key Features:
✅ Instant enforcement — kicks players using banned mods or resource packs
🛡️ Client verification — requires the ModSync client to connect successfully
📁 Audit logging — generates per‑player .log files showing current and deleted mods/packs with timestamps
⏱️ Configurable delays — control grace period for client verification and log generation
🎨 Admin commands — /modsync modlist <player> and /modsync packlist <player> with filters and color‑coded output
🗂️ Persistent storage — logs saved in plugins/ModSync/players/ for long‑term accountability
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:WdL3t7jw:IFxuRRbP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WdL3t7jw:IFxuRRbP"
}

