1.0.14
Compatibility
Changes
What's new in v1.0.14
Spark-style Diagnostic Reports
/mcsl share now generates a structured diagnostic report inspired by the Spark profiler, giving you a far more useful snapshot of your server at a glance.
New: Health Check section Three at-a-glance health indicators at the top of every report, each with a visual progress bar and status symbol (★ OK / ⚠ WARN / ✗ CRIT):
- TPS — flags degraded performance (warn <18, crit <15)
- Memory — heap pressure percentage (warn >75%, crit >90%)
- CPU — system load via JVM MXBean (warn >70%, crit >85%)
New: Platform Information section
- Java version and vendor (e.g. 21.0.10, Eclipse Adoptium)
- JVM implementation name (e.g. OpenJDK 64-Bit Server VM)
- Operating system and architecture
- CPU core count
- Relevant JVM flags (-Xmx, -Xms, -XX: options)
New: Garbage Collection section Per-GC-collector collection count and cumulative pause time, so you can spot GC pressure without needing a profiler.
New: Exception grouping
Errors are now deduplicated and grouped by exception type (e.g. 3x NullPointerException) instead of printing every raw line individually, making high-volume error logs much easier to read.
New: Thread Summary section Total thread count (with daemon split) and a breakdown of thread states (RUNNABLE / WAITING / TIMED_WAITING / BLOCKED) at the moment the report was generated.
Report section order Health Check → Platform → Server Info → GC → Plugins → Mods → Errors (grouped) → Warnings → Player Events → Thread Summary → Full Log
All other commands (/mcsl upload, /mcsl crash, /mcsl errors, etc.) are unchanged.
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:PvG9MjJ3:VU9agwLb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PvG9MjJ3:VU9agwLb"
}

