Hytale EventNotifications Plugin

A Hytale server plugin that sends real-time notifications to external services when server events occur. Get notified via ntfy (phone, desktop, or web), Discord, Slack, or custom webhooks when players join, the server starts/stops, and more.

Supported Notification Services

ntfy - Free, open-source push notifications (recommended)
Discord - Webhook notifications with rich embeds
Slack - Webhook notifications with attachments
Webhooks - Generic HTTP webhooks for custom integrations

Installation

Download the latest EventNotifications.jar from releases
Place the JAR in your Hytale server's mods folder
Start the server once to generate the default config
Edit config.json to configure your notification targets
Restart the server

Quick Start (ntfy)

The fastest way to get notifications:

Get ntfy: install the mobile app, desktop app, or use the web app
In the app, subscribe to a topic (e.g., my-hytale-server)
In config.json, set "enabled": true at the top level
Set the ntfy target to "enabled": true and update the URL to https://ntfy.sh/my-hytale-server
Restart the server - you'll now receive notifications!

Configuration

The config file is located at mods/Valhal_EventNotifications/config.json.

Important: The top-level "enabled" must be set to true for the plugin to send any notifications. By default, this is false.

For a complete example with all options, see example-config.json.

Basic Structure

{
  "enabled": true,
  "targets": {
    "ntfy": { ... },
    "discord": { ... },
    "slack": { ... },
    "webhook": { ... }
  }
}

ntfy Setup

ntfy is a free push notification service. You can use the public server or self-host.

"ntfy": {
  "type": "ntfy",
  "enabled": true,
  "url": "" rel="noopener nofollow" target="_blank">https://ntfy.sh/your-topic-name&quot;,
  "events": {
    "serverStart": {
      "enabled": true,
      "title": "{server} - Online",
      "message": "The server is now online!",
      "priority": "high",
      "tags": "green_circle"
    }
  }
}

Discord Setup

Create a webhook in your Discord channel (Channel Settings > Integrations > Webhooks)
Copy the webhook URL

"discord": {
  "type": "discord",
  "enabled": true,
  "url": "" rel="noopener nofollow" target="_blank">https://discord.com/api/webhooks/YOUR_ID/YOUR_TOKEN&quot;,
  "discordUsername": "Hytale Server",
  "discordUseEmbeds": true,
  "events": {
    "playerJoin": {
      "enabled": true,
      "title": "Player Joined",
      "message": "**{player}** joined the server",
      "color": "#5865F2"
    }
  }
}

Slack Setup

Create a Slack app at api.slack.com/apps
Enable "Incoming Webhooks" and create a webhook for your channel
Copy the webhook URL

"slack": {
  "type": "slack",
  "enabled": true,
  "url": "" rel="noopener nofollow" target="_blank">https://hooks.slack.com/services/YOUR/WEBHOOK/URL&quot;,
  "slackUseAttachments": true,
  "events": {
    "playerJoin": {
      "enabled": true,
      "title": "Player Joined",
      "message": "*{player}* joined the server",
      "color": "#5865F2"
    }
  }
}

Webhook Setup

For custom integrations with any HTTP endpoint:

"webhook": {
  "type": "webhook",
  "enabled": true,
  "url": "" rel="noopener nofollow" target="_blank">https://your-server.com/webhook&quot;,
  "contentType": "application/json",
  "events": {
    "serverStart": {
      "enabled": true,
      "title": "Server Online",
      "message": "The server started"
    }
  }
}

Authentication

All targets support optional authentication. Add these fields to any target configuration.

Bearer Token

For services that use token-based auth (like ntfy with access tokens (optional)):

"bearerToken": "tk_your_token_here"

This sends an Authorization: Bearer tk_your_token_here header with each request.

Basic Auth

For services that use username/password authentication:

"username": "your_username",
"password": "your_password"

This sends an Authorization: Basic <base64> header with each request.

Custom Headers

For webhooks that need custom authentication headers:

"headers": {
  "X-API-Key": "your-api-key",
  "X-Custom-Header": "value"
}

Supported Events

Event	Placeholders	Description
`serverStart`	`{server}`	Server finished starting
`serverStop`	`{server}`	Server is shutting down
`playerJoin`	`{server}`, `{player}`	Player connected
`playerLeave`	`{server}`, `{player}`	Player disconnected
`playerChat`	`{server}`, `{player}`, `{message}`	Player sent a chat message (disabled by default)
`gameModeChange`	`{server}`, `{gamemode}`	Game mode changed
`groupPermissionChange`	`{server}`, `{group}`, `{action}`, `{permissions}`	Group permissions modified
`playerPermissionChange`	`{server}`, `{player}`, `{action}`, `{group}`, `{permissions}`	Player permissions modified

Note: Chat notifications are disabled by default to avoid notification spam on busy servers. Enable playerChat in your config if you want to receive chat messages.

Event Configuration Options

Each event supports these options:

Option	Description
`enabled`	Whether to send notifications for this event
`title`	Notification title (supports placeholders)
`message`	Notification body (supports placeholders)
`priority`	ntfy priority: `min`, `low`, `default`, `high`, `urgent`
`tags`	ntfy emoji tags (e.g., `green_circle`, `skull`)
`color`	Discord/Slack color as hex (e.g., `#5865F2`)

Target Configuration Options

ntfy Options

Option	Default	Description
`ntfyMarkdown`	`true`	Enable markdown formatting in messages
`ntfyDefaultPriority`	`default`	Default priority for all events (`min`, `low`, `default`, `high`, `urgent`)
`ntfyIcon`	-	URL to icon image shown in notifications

Discord Options

Option	Default	Description
`discordUsername`	`{server}`	Bot username shown in Discord (defaults to server name)
`discordAvatarUrl`	-	URL to bot avatar image
`discordUseEmbeds`	`true`	Use rich embeds instead of plain messages

Slack Options

Option	Default	Description
`slackUsername`	`{server}`	Bot username shown in Slack (defaults to server name)
`slackIconUrl`	-	URL to bot icon image
`slackIconEmoji`	-	Emoji to use as bot icon (e.g., `:video_game:`)
`slackUseAttachments`	`true`	Use rich attachments instead of plain messages

Webhook Options

Option	Default	Description
`contentType`	`application/json`	HTTP Content-Type header
`bodyTemplate`	-	Custom body template (see below)
`headers`	-	Custom HTTP headers as key-value pairs

Custom Body Template

Use bodyTemplate to send a custom JSON payload instead of the default format:

"webhook": {
  "type": "webhook",
  "enabled": true,
  "url": "" rel="noopener nofollow" target="_blank">https://your-server.com/webhook&quot;,
  "bodyTemplate": "{\"event\": \"{eventType}\", \"text\": \"{message:json}\"}",
  "events": { ... }
}

Available template placeholders: {eventType}, {title}, {message}, {priority}, {tags}, plus all event-specific placeholders. Use :json suffix for JSON-escaped values (e.g., {message:json}).

Multiple Targets

You can enable multiple targets simultaneously. Each target has independent event settings, so you can send different events to different services:

{
  "targets": {
    "ntfy": {
      "enabled": true,
      "events": {
        "serverStart": { "enabled": true },
        "playerChat": { "enabled": false }
      }
    },
    "discord": {
      "enabled": true,
      "events": {
        "serverStart": { "enabled": true },
        "playerChat": { "enabled": true }
      }
    }
  }
}

Troubleshooting

Notifications not sending?

Check that the target is enabled: true
Verify the event is enabled: true within that target
Ensure the URL is correct and accessible from your server
Check server logs for error messages

Discord embeds not showing?

Make sure discordUseEmbeds is true
Verify webhook URL is complete and valid

Acknowledgments

This project was built using Hytale-Example-Project as a template.

Notes

Note: This plugin is not affiliated with ntfy.sh

License

MIT License