1.2.0
Compatibility
Changes
omg so i was not expecting to do a 1.2 so quickly after a 1.1, especially since i was working on some patches but I did some reasonably big changes in the code, so yeah.
Changelog
✨ What’s New & Improved:
-
Better Test Coverage:
We’ve added lots of unit tests for important parts likeColorUtil,FormatConfig,Messages,ChatManager, andNeboChatRenderer.
We also set up integration testing with MockBukkit to mimic real server environments. -
Debug Fixes:
The debug toggle now works as expected, even when config files are a bit messy.
No more losing your settings due to bad YAML! -
Safer Config Handling:
Extra checks were added to catch problems withconfig.yml, so things run more smoothly and with fewer hiccups. -
Code Touch-ups:
Old, unused code was cleaned out, and the experimental stuff is now stable.
JUnit5 tests are a bit neater too—they're tucked away safely as package-private. -
More Reliable Performance:
Fixed some tricky message-rendering bugs that could make chat messages vanish.
The plugin now handles edge cases and async events more gracefully. -
Version Awareness:
We’ve added checks to make sure things play nicely with Paper and supported Minecraft versions—less guesswork, more peace of mind.
👩💻 For Devs:
-
PlaceholderAPI Testing:
We ran safe integration tests to confirm it works without forcing a hard dependency. -
Config Example Refresh:
The example configuration file has been updated to better reflect real-world use.
🧹 Small Touches:
- Code formatting and cleanup for easier reading and consistency.
This update should feel smoother all around—more stable, easier to work with, and nicer for both devs and server owners. 💖
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:5huSIvoG:Jk8YaF3u"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5huSIvoG:Jk8YaF3u"
}

