WebhookIntegrations — Beauty in Blocks Fork
WebhookIntegrations connects a Paper Minecraft server to Discord through configurable webhooks. It can report server activity, player events, chat messages, deaths, advancements, and other information without requiring a Discord bot.
This version is a custom fork of WebhookIntegrations, originally created by rudynakodach.
Original project:
https://github.com/rudynakodach/WebhookIntegrations
The original project provides the main Discord webhook system used by this fork. Our version updates the plugin for current Paper releases and adds a webhook bridge for exporting Lightweight Clans information to websites and other JSON endpoints.
Standard Webhook Features
-
Support for multiple webhook URLs
-
Separate webhook destinations for different event types
-
Configurable Discord messages and embeds
-
PlaceholderAPI support
-
Configurable permissions
-
Player chat logging
-
Configurable chat censoring
-
Server startup and shutdown messages
-
Player join, quit, and kick messages
-
Player death messages
-
Advancement messages
-
Player-count updates
-
Custom HTTP request headers
-
Reload command for applying configuration changes
Each event can be enabled or disabled separately. Events can also be assigned to different webhook destinations, allowing server owners to keep general activity, chat, administrative information, and other messages in separate Discord channels.
Message contents are stored as configurable JSON in messages.yml. Server owners can replace the included messages with their own Discord embeds and formatting.
Lightweight Clans Integration
This fork includes an optional bridge for the Lightweight Clans plugin.
When enabled, the bridge sends clan information to a regular HTTP or HTTPS endpoint as JSON. This can be used to maintain a clan directory on a website, update external databases, or connect clan activity to another service.
The bridge can report:
Full clan information can be sent when the server starts, manually through a command, or periodically at a configurable interval.
Clan records may include:
Member and banner information can be included or excluded through the configuration.
Signed Webhook Requests
Requests from the Lightweight Clans bridge are signed using an HMAC-SHA256 shared secret. Each request includes headers identifying the event, its source, its timestamp, and its signature.
This allows the receiving website or service to verify that the request came from the Minecraft server and was not altered during delivery.
The bridge also includes configurable connection timeouts, read timeouts, retry attempts, and retry delays.
Lightweight Clans Is Optional
Lightweight Clans is only required when using the clan webhook bridge. The standard Discord webhook features continue to work without it.
When Lightweight Clans is not installed, its API is unavailable, or no clan endpoint has been configured, only the clan bridge is disabled. The rest of WebhookIntegrations remains active.
Basic Discord Setup
-
Create a webhook in the desired Discord channel.
-
Copy the Discord webhook URL.
-
Start the Minecraft server.
-
Use /seturl <webhook URL> to configure the default webhook.
-
Use /seturl <webhook URL> <ID> to add additional webhook destinations.
Events can then be assigned to the appropriate webhook ID in messages.yml.
Requirements
PlaceholderAPI is optional and is only required when PlaceholderAPI placeholders are used.
Lightweight Clans is optional and is only required for the clan data bridge.
Credit and License
WebhookIntegrations was originally created by rudynakodach. This project is a modified fork developed for the Beauty in Blocks server and released for others who may find the added features useful.
Please visit the original project for the original source, documentation, and development history:
https://github.com/rudynakodach/WebhookIntegrations
