Tags
Creators
Details
Licensed CC-BY-4.0
Published 2 years ago
Updated 6 months ago
All versions
1.0.7-DEV
Release
AwesomeChat v1.0.7-DEV8 months ago 35
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
Platforms
Paper
Spigot
Changes
🚀 AwesomeChat v1.0.7-DEV Changelog
New Features
- Chat Channels — Staff, admin, VIP + custom channels with per-channel formats, sounds, and permissions (
/ch join,/ch send,/ch leave) - Ignore System — Block players from chat and PMs with persistent JSON storage (
/ignore,/ignore list) - Mute Chat — Server-wide chat mute toggle with bypass permission (
/mutechat) - Clear Chat — Self or global chat clear with bypass and announcements (
/clearchat) - Emoji Shortcuts — 20 built-in
:shortcode:→ unicode replacements, permission-gated - Censor Mode — Alternative to blocking: replaces matched words with
****instead of cancelling the message - Join/Leave Messages — Per-group join, leave, first-join, MOTD, and sounds with EssentialsX vanish support
- Mention System —
@player,@(role),@everyone,@herewith per-type highlight colors, sounds, and action bar notifications - Item Display —
[item],[inventory],[enderchest],[/command]triggers in chat with hover tooltips and snapshot GUIs - Chat Radius — Distance-based local chat with per-group radii, shout prefix for global messages, cross-world toggle
- Chat Logging — SQLite/MySQL storage with
/chatlogssearch, time filters, and clickable pagination - Per-Group Sounds — Different chat sounds per LuckPerms group
- Per-Group Hovers — Component-specific hover text (username + message) with per-group overrides and click actions
- Public API —
AwesomeChatAPIinterface for other plugins to access violations, permissions, and managers - Config Migration — Incremental v3 → v6 migrator that preserves user settings and adds new sections automatically
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 auto-broadcaster indexing errors
- Fixed config version mismatch causing config to regenerate on every startup
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:QJE4vowW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:xlhtxoKF:QJE4vowW"
}

