Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated 2 months ago
All versions
1.3-Beta-09
Beta
Bug Fixes3 months ago 19
Uploaded by
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.5
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
🚀 X-Chat v1.3-Beta-09 - Changelog
⚙️ Bug Fixes
- Fixed local links not clickable — Links are now built directly via Adventure Component API (
ClickEvent/HoverEvent) instead of embedding MiniMessage string tags. Bypasses any MiniMessage parsing issues with complex nested click/hover tags. - Fixed cross-server link formatting — Same Component API fix ensures the JSON-serialized payload carries proper click/hover events to other servers.
- Fixed mentions not formatting — Mention names are now built as Adventure Components and injected via
Placeholder.component(), guaranteeing correct color/style rendering both locally and cross-server. - Fixed item tag hover/click not working — Item tags now build hover tooltips directly as Adventure Components with
HoverEvent.showText(). Previously the hover text was inserted as visible plain text instead of an actual Minecraft hover event. Item tags also support configurable click actions (suggest command, run command, copy to clipboard). - Fixed interactive player name — Player name hover/click in chat format now uses Adventure Component API instead of embedded MiniMessage string tags, for more reliable rendering.
- Fixed race condition with interactive name resolver —
AsyncPlayerChatEventfires concurrently across threads; the previous instance-field resolver could be overwritten by a second chat before being read. Now passed as a local parameter via anInteractiveNameResultholder. - Hardened cross-server payload delimiter — Switched from
\nto\u0001(SOH) between legacy/JSON/pre-mention parts. The old\ndelimiter could be silently corrupted if a player with MiniMessage permission typed<newline>. Receiver auto-detects the delimiter for backward compatibility with older senders. - Improved cross-server reliability — JSON Component serialization now carries proper interactive events since all local Components are built correctly. Added defensive
NoClassDefFoundErrorfallback on the receiver for very old Spigot, and a one-shot warning ifGsonComponentSerializeris missing from the classpath.
Optional dependencies
Any compatible version
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:5ElF3ZHX:uxPdPryJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5ElF3ZHX:uxPdPryJ"
}

