Creators
Details
1.0.5
Compatibility
Changes
Added
- Folia support: the plugin now runs on Folia servers alongside Bukkit, Spigot, and Paper.
All scheduled tasks use a new scheduler abstraction that automatically picks the correct
Bukkit or Folia scheduler at runtime.
plugin.ymlnow declaresfolia-supported: true. - Correct chat formatting on Spigot: chat-format events are now handled through the right
API on each platform —
AsyncChatEventon Paper andAsyncPlayerChatEventon Spigot.
Fixed
-
Plugin did not start when TeamsAPI or EzCountdown were absent: Servers without TeamsAPI or EzCountdown installed logged
NoClassDefFoundErrorat startup and the plugin failed to load entirely. Both integrations are now fully isolated — the plugin always starts cleanly and activates each integration only when its plugin is present. -
Plugin did not start on Spigot (
NoClassDefFoundErrorat startup): Several internal classes referenced Adventure API types that are absent or incompatible on Spigot 1.21.4 and 1.21.11, causing the JVM to crash during class initialisation before any commands or events could be registered. All Adventure-typed state has been moved into lazily-loaded inner classes that Spigot never touches at startup. -
Messages showed no colour or formatting on Spigot: Plugin messages appeared as raw plain text because Spigot does not bundle Adventure at runtime. The plugin now ships its own copy of Adventure (MiniMessage + legacy serialiser) so colours, bold, italic, and other formatting always render correctly on Spigot.
-
All commands crashed on Spigot (
/f info,/f create, and every other command): Every command thrown on Spigot producedUnsupportedOperationException: No JsonComponentSerializer implementation found, making the plugin completely unusable. The GSON serialiser is now bundled in the plugin JAR, and the initialisation sequence explicitly uses the plugin classloader so that Java'sServiceLoaderlocates the implementation at runtime rather than falling back to a stub that throws. -
Hover tooltips did nothing on Spigot (
/f infomember list,/f mapterritory tiles): After the command crash was resolved, hover and click events were still silently dropped because the Spigot message path was sending plain §-coded strings. Messages to players are now serialised to JSON via the bundled GSON serialiser and delivered through the BungeeCord chat API, so hover and click events work correctly on Spigot. -
Intermittent shutdown error from bStats metrics (rare): On servers that shut down shortly after startup, bStats background tasks occasionally ran after the database connection was already closed, logging
HikariDataSource has been closed. A shutdown flag now prevents metrics tasks from querying the database once the plugin has stopped.
Optional dependencies
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:trDfzeaq:2aurmzJG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:trDfzeaq:2aurmzJG"
}







