KickEvents KickStreaming MultiStreamer | Channel Reedemptions, Subs gifted, Kicks gifted

Bring your Kick stream directly into Minecraft.

KickEvents is a Paper and Folia plugin that listens to official Kick webhooks and turns channel activity into Minecraft console commands. Channel reward redemptions, gifted subscriptions, and gifted KICKs can trigger announcements, rewards, effects, minigames, server events, or practically any action that can be executed through a command.

The plugin includes its own lightweight web server, OAuth callback page, and webhook receiver. You do not need to develop or host a separate website or external bot. Simply configure the IP and port, connect your public domain or tunnel, create your Kick application, and authorize your channel with /ke login.

Versions supported: 1.20 - 26.2

Main features

• Official Kick OAuth2 authentication.
  
  
• Automatic webhook subscriptions after a successful login.
  
  
• Built-in web server for OAuth callbacks and incoming webhooks.
  
  
• Support for Paper and Folia.
  
  
• Channel reward redemption events.
  
  
• Gifted subscription events.
  
  
• Gifted KICK events.
  
  
• Multistreamer support for multiple Kick channels at the same time.
  
  
• Different rules and commands for each streamer.
  
  
• Filters by streamer, reward name, status, gift name, and minimum amount.
  
  
• Multiple console commands per event.
  
  
• Built-in event placeholders.
  
  
• Custom variables configured in config.yml.
  
  
• Optional PlaceholderAPI support.
  
  
• Configurable MiniMessage messages through messages.yml.
  
  
• Signed webhook verification, replay protection, payload limits, and duplicate-event protection.

How it works

KickEvents creates a connection between Kick and your Minecraft server:

1. A streamer authorizes the plugin using /ke login.
   
   
2. Kick redirects the streamer to the callback page hosted by the plugin.
   
   
3. KickEvents securely stores the authorization token.
   
   
4. The plugin automatically subscribes the channel to the supported Kick events.
   
   
5. Kick sends signed webhook requests whenever a configured event occurs.
   
   
6. KickEvents validates the webhook and finds matching rules in rewards.yml.
   
   
7. Every command in the matching rule is executed from the Minecraft console.

For example, a channel reward can give an item to a player, start a server event, change the weather, summon a mob, broadcast a message, or call commands from another plugin.

Supported events

Channel reward redemptions

Event name:

This event is received whenever a viewer redeems a channel reward or its status changes. Rules can be filtered by the exact reward title, streamer, and redemption status.

Kick reward redemptions may arrive as pending and later be updated to accepted or rejected. In most cases, using statuses: [accepted] is recommended so the action only runs after the redemption has been accepted.

{input} contains the optional text entered by the viewer. If the reward does not request text or Kick sends null, the placeholder becomes an empty value.

Gifted subscriptions

Event name:

This event allows commands to run when someone gifts subscriptions. You can require a minimum amount and create different rewards for different milestones.

Gifted KICKs

Event name:

This event reacts to gifted KICKs. Rules can filter by gift name, streamer, and minimum amount.

Leaving an optional filter empty makes the rule match any value.

Multistreamer support

KickEvents can connect multiple Kick channels to the same Minecraft server. This is useful for creator servers, events, SMP communities, and networks where several streamers play together.

Enable multistreamer mode and authorize every additional streamer:

Rules can then target one specific streamer:

Another streamer can use a different reward name and completely different commands. If streamer is empty, the rule can match events from any connected channel.

Remove a connected streamer with:

KickEvents removes the locally stored connection and its webhook subscriptions.

Available placeholders

KickEvents replaces these values inside every configured command:

Placeholders that do not apply to the current event are replaced with an empty value or the event's default amount.

Custom variables

Reusable variables can be created in config.yml:

They can then be used in any event command:

Any key added under variables becomes available using {variable-name}. These values are intended for public reusable text and should never contain passwords, tokens, or secrets.

PlaceholderAPI support

PlaceholderAPI is supported as an optional dependency.

The expansion that provides each placeholder must also be installed. Because Kick webhooks are processed as console events, placeholders that require a specific online Minecraft player may not have player context. Server-wide, global, and console-compatible placeholders are the best fit.

KickEvents placeholders use braces, such as {user}. PlaceholderAPI placeholders normally use percent signs, such as %server_online%. Both formats can be used in the same command.

Creating the Kick application

1. Open Kick Developer Settings.
   
   
2. Select Create application.
   
   
3. Enter an application name and description.
   
   
4. Add the redirect URL used by KickEvents.
   
   
5. Enable webhooks and add the public webhook URL.
   
   
6. Select the scopes required for user/channel information, channel rewards, and event subscriptions.
   
   
7. Create the application.
   
   
8. Copy the Client ID and Client Secret into config.yml.

Example production URLs:

The redirect URL registered on Kick must exactly match oauth.redirect-url, including the protocol, domain, port, and path.

Web server configuration

KickEvents hosts the callback page and webhook endpoint itself:

• bind-address controls the network interface used by the embedded server.
  
  
• port controls the local listening port.
  
  
• public-base-url is the public address reachable by Kick.
  
  
• callback-path is used after OAuth authorization.
  
  
• webhook-path receives signed Kick events.

For localhost testing, a public HTTPS tunnel such as Cloudflare Tunnel or ngrok can forward traffic to the plugin's local port. For production, place a reverse proxy or secure tunnel in front of KickEvents and configure TLS, firewall rules, rate limiting, and DDoS protection there.

KickEvents provides the application endpoints; domain registration, DNS, certificates, tunnel configuration, and infrastructure protection remain under the server owner's control.

Basic configuration

After saving the configuration, use:

Open the generated authorization link and approve the application. The player who requested the login receives visual and sound feedback when authorization and webhook subscription finish successfully.

Commands and permissions

Main command: /kickevents

Alias: /ke

Permission: kickevents.admin

All feedback messages can be customized in messages.yml using MiniMessage formatting.

Security notes

Webhook requests are treated as untrusted input. KickEvents validates Kick's signature, limits request body size, checks timestamp age, and deduplicates event message IDs before executing rules.

Keep these files private:

• config.yml when it contains your Client Secret.
  
  
• tokens.yml, which contains authorization data.

Only trusted administrators should receive kickevents.admin or filesystem access to rewards.yml, because configured actions run as console commands. HTTPS is strongly recommended for any public installation.

Requirements

• Paper or Folia.
  
  
• Java 17 -21.
  
  
• A Kick developer application.
  
  
• A public URL, reverse proxy, or HTTPS tunnel for incoming webhooks.
  
  
• PlaceholderAPI is optional.

KickEvents turns stream engagement into real gameplay: viewers interact through Kick, streamers can share the same server, and server owners remain in control of every rule and command.


Support:
Discord - 0x20x