Links
Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated 6 months ago
All versions
0.1.0
Release
CompatGuard 0.1.06 months ago 70
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platform
Paper
Changes
🚀 0.1.0 — Initial Release
✅ Added
- 🧠 Plugin compatibility scanner with five‑tier risk classification:
SAFE|LIKELY SAFE|REVIEW NEEDED|HIGH RISK|FAILED / DISABLED - ⚙️ Configurable scoring rules via
rules.yml
(e.g., penalties for missing/oldapi-version, legacy patterns, etc.) - 🔍 Auto‑detection of update sources:
- GitHub
- Modrinth
- Spiget
- 🌐 Smart discovery:
- Parses
websitefield for GitHub URLs - Searches Modrinth & Spiget by plugin name with fuzzy matching
- Probes common GitHub release filename patterns as fallback
- Parses
- 🔗 One‑click in‑game updates via clickable Adventure chat components
(🎣/cg update <name>— works from console too) - 📦 Updates staged safely in
plugins/update/— no hot‑swapping
⚠️ Old JARs saved toplugins/backup/before update - ⏰
auto-update: true— auto‑update on startup (optional) - ⏱️ Scheduled auto‑scan every
Nhours (auto-scan-interval-hours) - 🆕 Operator join notifications with interactive update prompts
(🔔 “Click to update” style messages) - 🔄 Callback‑based completion — notifications fire only when checks finish
- 💬 Discord webhook notifications with rich embeds
(🚨 High‑risk plugins, new updates, etc.) - 🚫
plugin-ignore-listinconfig.ymlfor plugins you never want to auto‑check - 🧪
/cg debug <name>— full diagnostic output (including detected download URL) - 📄 JSON report export to
plugins/CompatGuard/reports/
(📊 timestamp, server version, Java, plugin list, scores, status, update info) - 📖 Paginated GUI with inventory‑based plugin browser
- Left‑click: details
- Right‑click: refresh checks
- Shift‑click: export one‑line summary
- 🧩 Dual‑layer caching:
- Results cache (compatibility scores, status)
- Auto‑detected provider mappings (GitHub/Modrinth/Spiget → plugin name)
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:rOHDPWtr:qZe3fLDQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rOHDPWtr:qZe3fLDQ"
}

