Links
Tags
Creators
Details
0.4.1
Compatibility
Changes
Kick realtime connection fix
- Replaces the retired hardcoded Pusher connection with Kick-negotiated anonymous Centrifugo chat. Fixes the Pusher 4001 connection error.
- Adds heartbeat handling, anonymous token renewal, reconnect with backoff, and cleanup on plugin disable/reload.
- Filters duplicate messages and formatting controls; never logs raw chat or tokens.
Configuration migration
Add kick-channel-id to your existing config: the top-level id from https://kick.com/api/v2/channels/YOUR_CHANNEL_NAME. Keep kick-channel set to chatroom.id from the same response. These IDs must refer to the same streamer. Legacy app-key, cluster, ws-url, and auth-token settings are ignored. No account or OAuth token is needed.
Requires Paper/Purpur 26.2 and Java 25. Five automated tests pass. Live Kick message decoding and the chat subscription on a running Paper 26.2 server were verified.
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:8Y0afIlv:Trdt5Gpq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:8Y0afIlv:Trdt5Gpq"
}

