A simple proxy service that filters Discord webhook messages from DinkPlugin based on player allowlists and denylists.
Prefer to run your own? Click the button above to deploy your own copy to Cloudflare!
Once deployed, on the Domains tab in the Cloudflare Worker dashboard, enable the production Worker URL so you can access the Visit button at the top right
This service sits between DinkPlugin and Discord, letting you control which players' messages get posted to your Discord channel. You can:
- Allowlist mode: Only players with specific dink account hashes or player names are forwarded (recommended; more secure)
- Denylist mode: All players except those with specific names or account hashes are forwarded (simpler; easier to bypass)
- Visit your deployed worker URL
- Click "Create New Webhook Filter"
- Copy the webhook URL shown (it includes a secret code)
- Enter your Discord channel's webhook URL
- Choose your filter mode (allowlist or denylist)
- Add player identifiers (one per line)
- Save the configuration
| Field | Description |
|---|---|
| Discord Webhook URL | The webhook URL from your Discord channel settings |
| Filter Mode | allow — only listed players are forwarded.deny — all players except listed ones are forwarded |
| Identifiers | One identifier per line. You can include both dink account hashes (from ::DinkHash) and player names in the same list. Matching is case-insensitive. Maximum: 1024 players. |
In your DinkPlugin configuration, set the webhook URL to:
https://dink.pajlada.se/webhook/GENERATED_SECRET_HASH
That's it; DinkPlugin will now send messages through your filter automatically.
When DinkPlugin sends a message, the service checks it against your list:
- Allow mode: The message is forwarded if the player's dink account hash or player name appears in your list
- Deny mode: The message is forwarded only if neither the player's dink account hash nor the player name appears in your list
Messages that don't pass the filter are silently dropped.
Note: Your identifier list can contain a mix of dink account hashes and player names simultaneously. The most secure option is to solely use an allowlist of account hashes.
Webhook not working
- Verify your Discord webhook URL is correct
- Make sure DinkPlugin is using the full webhook URL (including the secret hash; but not the secret key)
Filtering doesn't seem to work
- For allow mode: confirm the player's dink account hash or name is listed
- For deny mode: confirm the player's dink account hash and name is not listed
Lost your secret?
Navigate to /new to create a fresh configuration (if you can't find the old secret in your browser history) and update your DinkPlugin settings.
Instead of relying upon our instance, you can create your own Cloudflare Worker using this repo.
The admin can disable the creation of new webhook configurations by setting the
DISABLE_NEW_CONFIGS environment variable in wrangler.toml to true:
[vars]
DISABLE_NEW_CONFIGS = trueWhen enabled, requests to /new are rejected with 403 Forbidden. Existing
configurations and their webhooks continue to function normally. This is useful
for "freezing" a deployment once the desired filters have been created.