Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 4 months ago
Updated 3 days ago
All versions
1.0.0-1.21.11
Release
1.0.0-1.21.114 months ago 13
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Fabric
Supported environments
Dedicated servers only
Required content
Changes
StreamerUtils 1.0.0-1.21.11
Features
- Custom nameplate icons – choose from Twitch, YouTube, Kick, heart, crown, or none (pixel art icons included).
- Full RGB & 16 official Minecraft colors for your name in chat.
- Twitch integration:
- Connect your Twitch account to show live status on your nameplate.
- Responds to
!highlight(gives the streamer Glowing effect) and!firework(launches a firework). - Follow alerts with custom sounds – configurable per player (none / personal / global / both).
- Server‑side only – works on dedicated servers. No client installation required.
- Per‑player settings saved persistently (icon, color, streamer live status, follow alert mode, welcome message, prefix style).
- Global bracket customization for operators (e.g.,
[Player]→{Player}). - Welcome message with clickable documentation / download links and an option to disable it.
- Full command suite –
/su helplists everything.
Notes
- Requires Fabric Loader 0.19.2+ and Fabric API 0.141.3+.
- Built for Minecraft 1.21.11; other versions may work with updated mappings.
- Server‑side only – the client does not need the mod, but the optional companion resource pack makes custom icons look better.
Upcoming / Planned Features
- More platform icons (Punkord (cough-cough), Discord, etc.) --- suggest some anywhere on my discord
- Web dashboard for live configuration.
- Maaybbee compatibility with earlier Minecraft versions?
- Definitely 26.1/2 compatibility (oh dear).
- Configurable cooldowns for Twitch commands (eh, still not sure).
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:gbHqKlUz:1PdVApMt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gbHqKlUz:1PdVApMt"
}

