Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated 2 months ago
All versions
1.3-Beta-06
Beta
Bugs/Errors fixes4 months ago 18
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-06 - Changelog
🐛 Bugs/Error Fixes
- Fixed
IllegalPluginAccessExceptionon plugin disable —RedisMessagingService.publish()no longer uses the Bukkit scheduler (runTaskAsynchronously), which threw an error when the plugin was shutting down. Now usesCompletableFuture.runAsync()for all Redis publishes, making it safe during the entire plugin lifecycle including disable. - Fixed cross-server mention formatting lost — Mention highlights (color, bold, etc.) were stripped when messages traveled between servers. The cross-server payload now sends MiniMessage source strings instead of JSON-serialized Components, preserving all rich text formatting end-to-end.
- Fixed cross-server auto-links not clickable — URLs with
<click:open_url>and<hover>events were lost in transit. The new MiniMessage-based transfer preserves click and hover actions on links for Paper servers. - Fixed cross-server interactive player names not working — Hover and click events on player names in chat format were discarded cross-server. Now fully preserved via MiniMessage serialization.
- Fixed cross-server tags (
[inv],[pos],[ping]) losing hover/click — Item tooltips, position data, and ping display with their hover components now transfer correctly to other servers. - Fixed cross-server PM sender name not interactive — Private messages from other servers now show the sender's name with hover info (including their origin server) and click-to-reply action, matching the local PM behavior.
- Fixed cross-server mention sound detection — The mention sound now uses pre-mention plain text for reliable player name matching, avoiding false negatives from MiniMessage tags wrapping player names.
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:91PBwNrJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5ElF3ZHX:91PBwNrJ"
}

