Links
Tags
Creators
Details
0.5.3
Compatibility
Changes
FullXaosRPG v0.5.3 — Changelog Release: v0.5.3 (merged from v0.5.0 + v0.5.2) Target: Paper 1.21.x
BUG FIX — TitleService missing colorize() method v0.5.2 TitleService was missing the colorize() and getDisplayPrefix() methods. HudService called titleService.colorize() at runtime — this would crash on title display. Fixed by restoring the complete v0.5.0 TitleService which includes:
colorize(titleId) — color-codes titles by type (gold for Season Champion, yellow for Top3, green for Top10, aqua for Rank titles, purple for Prestige titles) getDisplayPrefix(UUID) — returns formatted title prefix for HUD formatTitle() aliased to colorize() for compatibility
BUG FIX — FullXaosCommand broken routing v0.5.2 command handler used a broken if-else chain where upgrade skill and upgrade level branches were unreachable, and season had no standalone handler. Replaced with clean switch-based routing from v0.5.0. All subcommands now work correctly:
/fullxaos prestige <skill> — routes correctly /fullxaos season — now has standalone handler (shows timer + your points) /fullxaos season top — leaderboard top 10 /fullxaos title list / equip / off — all working /fullxaos upgrade skill and upgrade level — now reachable
ENHANCEMENT — Portal list shows full info /fullxaos portal list now displays per portal:
Time remaining (e.g. ⏱12m or ⏱45s) Active rift modifiers (e.g. ◆ ⚡ Frenzied 🌀 Gravitational) Boss affixes if boss has spawned (e.g. ✦ Boss: ✦ Blink 🔥 Enraged)
Version string fix All three version references updated to 0.5.3:
plugin.yml version field onEnable log message onDisable log message
No DB changes No new migrations. Schema unchanged from v0.5.2. No architecture changes No packages deleted, renamed, or refactored. ServiceRegistry pattern intact. All 17 services preserved.
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:v1yHN2vV:rmNA45le"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v1yHN2vV:rmNA45le"
}

