Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 3 months ago
Updated 2 weeks ago
All versions
2.4.0
Release
ChatSphere 2.4.0last month 26
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Required content
Any compatible version
Changes
2.4.0
Added
/chatsphere doctordata status: rows against the caps, file sizes, backups, Discord state/chatsphere backup,backups,restore <timestamp>,purge <channel>,reload- Typing indicator, plus a notification level per conversation (all / mentions / muted), both configurable
- Channel history for players who join mid-session, and unread counts that survive a restart
inviteHistoryEnabledserver option: joining a channel delivers its stored history- Create channel screen: three step wizard (template, basics, sub-channels) with templates that prefill the name and suggest sub-channels
- Client settings for the outside-chat HUD and the character cap per bubble
- HUD bubbles show custom emoji as
[emoji]/[animated emoji]instead of the raw shortcode - Optional Discord bridge: mirror one channel to Discord with a webhook, or both ways with a bot token (off by default)
Changed
- Chat, console and channel writes are batched instead of one disk write per message
- Chat scrollback is never capped below the server's
maxChatHistory - Emoji uploads allow 512 KB, animated GIFs 320x320 / 60 frames, sprite sheets up to 8192 px
- Client settings page: notifications and HUD options have their own groups
Fixed
/chatsphere infoshowed the raw translation key instead of the label- HUD unread badge could render underneath the chat icon while the count refreshed
- Channel info: the invite code no longer overlaps its label in longer languages
- The left rail and the sidebar scroll, so a long channel list no longer pushes the create button off screen
- Channel info: the owner gets a delete button instead of a leave button that did nothing
- Deleting a channel from its config screen no longer leaves the info panel open
- Custom skin API: avatars are fetched properly, and the refresh button updates every known player
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:rbuDt8Bs:MYQqbszF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rbuDt8Bs:MYQqbszF"
}

