1.1.0
Compatibility
Required content
Changes
TS Widget 1.0.0 π’ New | π‘ Changed | π΄ Fixed
π’ New
- π’ KnownUsers local cache/persistence (config/tswidget-users.json, UID β nickname/lastSeen) to remember seen TeamSpeak users across sessions
- π’ /tswidget and /ts-widget client commands (settings, toggle, widget show/hide, connect/disconnect, help)
- π’ Open Keybinds / Hotkeys button in Settings β Control (opens the Minecraft keybinds screen)
- π’ channelclientlist now requests -uid for more stable user identification
π‘ Changed
- π‘ StatusEmoji rendering switched to texture drawing with proper scaling
- π‘ Settings toggles redesigned for clarity: high-contrast ON/OFF state (green/red track + label + knob position), with live toggle feedback
- π‘ Widget interaction/input handling updated for better LabyMod/Fabric screen compatibility
π΄ Fixed
π΄ Fixed periodic status flicker (~every 2s) where users briefly reverted to idle/white: user fields are now preserved/only updated when present in responses; channel refresh no longer wipes known state π΄ Improved sync when Minecraft starts before TeamSpeak: more robust connect/init flow (use, whoami, channel/client list requests) and better handling of late TS3 availability (reconnect behavior) π΄ Fixed βUnknown channelβ cases by handling channelvariable responses without cid, caching/resolving channel names, and requesting channel list updates on channel changes π΄ Improved stability of channel/user refresh by carrying over existing user state (mute/deaf/away/talk flags, talking snapshot) during list updates βοΈ Requirements Minecraft 1.21.11, Fabric Loader >=0.18.1, Fabric API >=0.141.0, Java >=21 Client-side only, MIT licensed
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:DPCbYwww:joim8lIP"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DPCbYwww:joim8lIP"
}
