Tags
Creators
Details
1.0.0
Compatibility
Changes
Initial release of MCMS — Make Console Make Sense.
70+ console message patterns transformed into plain English (with a dash of sarcasm). Network errors, lag warnings, plugin failures, Java exceptions, chunk issues, player events, Mojang auth — all of it, actually readable.
- Smart exception summaries: root cause + file/line shown first, full trace still follows
- Colorful ASCII art startup banner (on supported terminals)
- Update checker with a hard-to-miss console notice
- /mcms stats — see how many messages have been transformed this session
- Zero configuration required — drop in and go
Supports Paper, Purpur, Spigot, Bukkit, Folia, and all Paper forks (1.18 – 26.1.2)
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:BTLT17At:wx6VhubM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BTLT17At:wx6VhubM"
}

