Tags
Creators
Details
1.0.8
Compatibility
Changes
π AwesomeChat v1.0.8-BETA Changelog (official)
π¨NOTE: This is a BREAKING change, the config migrator is still expirimental and is likely to break. You may need to delete and regenerate the plugin folder if things are not working as expected. As always, make sure to back it up first.
NEW
- New chat filter system, easier to use and configure.
- Chatlog Support
Bug Fixes
- Fixed hex color codes (
&#RRGGBB) not parsing in chat formats, hover messages, or console - Fixed hex colors rendering as wrong colors due to
Component.text()not interpreting BungeeCord hex format β now uses AdventureLegacyComponentSerializer - Fixed hex colors in per-group formats rendering as the wrong color β
extractTrailingColornow correctly identifiesΒ§xhex sequences instead of treating the lastΒ§pair as a standalone color - Fixed per-group hovers not working β
HoverManagermethods now accept the player's group for per-group hover lookups - Fixed
/ignoretoggle not working reliably β replacedHashMap/HashSetwithConcurrentHashMapfor thread safety between async chat and main thread commands - Fixed /unignore and /unblock commands not registering
- Fixed color code permission bypass via uppercase
&codes β color pattern matching is now case-insensitive - Fixed persistent chat colors and manual
&codes being stripped from messages βbuildComponentFromFormatnow wraps messages using Adventure's component tree instead of serializing to plain text - Fixed auto-broadcaster indexing errors
- Fixed config version mismatch causing config to regenerate on every startup
- Fixed [item] and [inventory] formats not working
- Fixed chatcolor gui and default permissions
- Fixed
per-group-hoversnot working properly - Fixed ignored messages still taking up a blank space
- Fixed Anti-Advertising chat filter module breaking
- Fixed colors not properly registering in the
per-group-formatsection
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:xlhtxoKF:l5Dt0BSp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xlhtxoKF:l5Dt0BSp"
}

