The hye bot lives where your community already does.
Run release alerts, license delivery, server whitelists, and event RSVPs from your Discord server. Same Hye account. Zero copy-paste.
Open source. Hosted by Hye. Self-host coming.
Built for the people who run things.
Release pings
Auto-post to a release channel when a creator you follow ships a new version. Filter by version type, MC version, or loader.
License delivery
Buyers receive their license key via DM right after checkout. They never see your inbox.
Server commands
/hye search, /hye install, /hye versions — search the catalog without leaving your channel.
Event RSVPs
RSVP to a hye event from Discord. Hosts decide whether RSVPs auto-grant a Discord role.
Whitelist sync
Wire RSVPs to your Minecraft server's whitelist. Going → added; clear → removed. Optional auto-removal post-event.
Moderation alerts
Staff get pinged when a project they're assigned to gets a report or DMCA notice. Acknowledge inline; the audit log records who saw it.
For server owners on call at 3am.
Restart from chat
Restart and stop targets via slash command, gated by Discord role. Logs the actor and reason in the audit trail.
Per-version compatibility
Bot reads each plugin's loader / MC version range and blocks installs that don't match the running server.
Update polling
Daily check for new versions of installed plugins. Posts a digest to a channel of your choice.
For people shipping plugins.
New version digest
Auto-compose a release post (changelog, downloads link, MC versions, loader) when you publish.
Per-license DM
Each buyer gets their key in DM. No more pinging staff for keys.
Showcase channel
Pin your latest published projects to a channel. Updated automatically when you ship.
Tie hye events to Discord.
RSVP from a thread
Hosts post the event in a Discord channel; members react to RSVP. The RSVP lands on hye and inherits the event's visibility rules.
RSVP → whitelist
For private servers: a 'Going' RSVP auto-adds the player to the Minecraft whitelist via the bot. RSVP cleared → removed at event end. Cleanup is auditable.
What the bot needs.
Granular Discord scopes; no message history, no DM read access.
applications.commandsSlash commands.
bot (Send Messages, Embed Links)Post release pings and event posts.
guild.members.readMap Discord IDs to hye accounts for license delivery.
webhook.incomingPost to a release channel without spamming a bot account.
dm.messages.sendDeliver license keys via DM.
roles.assign (specific role only)Grant the event role on RSVP.
- Read your DM history
- See message content outside slash commands
- Post in channels you didn't grant access to
Add the bot.
Three steps. (1) OAuth into your Discord server. (2) Pick a release channel and an event channel. (3) Link your hye creator profile under Connected accounts in your dashboard.
Common questions.
- Is the bot open source?
- Source on GitHub at github.com/mrayden/hye-discord-bot. Run a fork against your own hye instance if you self-host.
- What does it cost?
- Free for any hye account. Hye doesn't charge per-message or per-guild.
- Do buyers need Discord?
- No. License delivery falls back to email when the buyer hasn't linked Discord.
- Will RSVP → whitelist work without Bukkit?
- For Bukkit-family servers, the bot pushes via RCON. Other servers can poll the hye API for the current whitelist via a creator-provided webhook.