All versions
1.0.0
Release
Extra Chat 1.0.02 weeks ago 35
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Changes
Extra Chat 1.0.0 — Tabbed Control Update
Single Tabbed Panel
- Added the new Single Tabbed Panel layout. (Kept the classic separate-window layout as the default layout.)
- Added circular next and previous tab switching.
- Empty, hidden, and unavailable tabs are skipped automatically.
- Added a shared HUD position and size for the tabbed panel.
- Only one panel is shown in the HUD position screen while this mode is active.
Keyboard Shortcuts
- Added configurable next and previous tab shortcuts.
- Added direct shortcuts for individual tabs.
- Added Alt, Shift, and Ctrl modifier support.
- Added shortcut conflict warnings.
- Shortcuts are disabled while chat or another screen is open.
Tab Settings
- Added a dedicated Tab Settings screen.
- Moved Appearance, Tab Shortcut, and Server Restrictions into this screen.
Server-Specific Tabs
- Tabs can be limited to selected servers.
- Multiple server addresses can be added to each tab.
- Server entries can be reordered or removed.
- Tabs are automatically hidden outside their assigned servers.
- Default port matching is supported.
Appearance and HUD
- Added advanced global appearance options.
- Added header settings, line height, padding, tab color, and text shadow options.
- Improved settings screen alignment.
Settings Management
- Added Undo, Defaults, Apply, Save & Close, and Cancel options.
- Added recent-change undo support.
Compatibility and Metadata
- Added optional Mod Menu compatibility.
- Extra Chat has officially been released with version 1.0.0.
- Changed the license to All Rights Reserved.
Optional dependencies
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:AFkQc3V3:SdTAM826"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AFkQc3V3:SdTAM826"
}


