Docs

What Umbyrx is

Umbyrx is a Discord bot with a web dashboard. The parts you use in the middle of a conversation are commands you type in Discord. The parts you set up once and forget are configured in the browser. That split is deliberate: nobody wants to build a ticket panel by typing twenty config commands, and nobody wants to open a website to ban someone.

It is black and white on purpose, it has no paywalled commands, and it runs on prefix commands rather than slash commands.

Adding the bot

Use the invite page, pick your server, and keep the permissions it asks for. You need Manage Server in that server to add a bot at all.

Once it has joined, open the dashboard and sign in with Discord. Your server appears in the list, and every module starts turned off. Nothing changes in your server until you switch something on.

The prefix

The default prefix is -, so commands look like -ban and -help. Change it in General Settings on the dashboard or with -settings prefix <new>. A dashboard change reaches the bot within about thirty seconds.

If you forget it, mention the bot and it will tell you what the prefix is here.

Permissions and hierarchy

Two things decide whether a command works: whether you are allowed to run it, and whether the bot is able to carry it out.

Every command lists the permission you need on the commands page. The bot, separately, needs the matching permission itself, and its highest role has to sit above whoever it is acting on. This is Discord's rule, not ours: a bot cannot ban, kick, mute, or change the roles of anyone whose top role is equal to or above its own.

If a command does nothing and the bot says it cannot act on that member, drag the Umbyrx role higher in Server Settings, Roles. That fixes most of these.

The dashboard applies a ceiling too: role pickers will not let a manager hand out a role at or above their own highest role. The server owner and the bot owner are exempt.

Moderation and cases

The usual actions are -ban, -softban, -tempban, -kick, -mute, -unmute and -warn. Mutes use Discord's own timeout, so they survive a restart and show in the member list. Durations are written the way you would say them: 10m, 2h, 1h30m, 7d.

Every action opens a numbered case. -case <number> shows one, -reason sets or corrects the reason after the fact, and -modlogs @user lists everything that has happened to a member. Warnings have their own list through -warnings, -delwarn and -clearwarnings.

Set a mod-log channel in General Settings and every case is posted there as it happens.

Channels and cleanup

-purge bulk deletes messages, optionally only from one member. Discord will not let any bot delete messages older than fourteen days, so purge stops there.

-lock and -unlock close a channel to the everyone role, -hide and -unhide take it out of the channel list, and -slowmode sets the per-member cooldown.

Automod

The Automod page edits Discord's native AutoMod rules rather than a copy of them. Rules you make there appear in Server Settings, and rules you make in Discord appear on the dashboard. Nothing is duplicated and nothing drifts.

That also means the filtering runs on Discord's side, so it keeps working even if the bot is restarting.

Antinuke

Antinuke watches the audit log and steps in when one account takes more destructive actions than you allow inside a short window: mass bans, mass kicks, channel deletions, role deletions. The punishment is yours to pick: ban, kick, or strip every role.

The server owner, the bot, and anyone on the whitelist are never punished. A scam-image filter can also fingerprint posted images and delete ones matching a known blocklist.

Antinuke settings are owner-only. Managers can see the page but cannot change it, because someone who can edit antinuke can disable it first and then do the damage.

Logging

Logging routes server events to channels, per event, so deletes can go somewhere private while joins go somewhere public. A destination can be a channel or a thread.

Ignore lists let you exclude a channel, a member or a role from an event, which is how you stop a busy bot channel flooding the delete log. Where Discord exposes it in the audit log, the panel also names who did it.

Greet and farewell

Welcome and goodbye messages, plus an autorole given on join. Messages are built in the dashboard's message editor, so they can carry a panel, buttons and variables like the member's name and the server's member count.

Leveling

Members earn xp for talking, with a cooldown so spam does not pay. Ranks are a text panel rather than a generated image, which keeps them readable on a phone and instant to post.

-rank shows a member's level, -levels shows the leaderboard. Role rewards are set on the dashboard and granted automatically.

Activity tracking

The bot counts messages and voice time per member and keeps thirty days of history. -messages and -voice show one member, -topmessages and -topvoice show the leaderboard, and both accept a window and a channel, for example -topmessages 7d #general.

Leaderboards are interactive: page through them with the buttons, and change the window without retyping the command. Only the person who ran it can drive the buttons.

Windows longer than thirty days are clamped, because that is how long the history is kept.

Tickets

Build a panel on the dashboard, give it types (each with its own name, description, button or menu entry, category, staff roles and opening message), then post it to a channel. Members open a ticket from the panel.

Tickets can be channels or threads. Inside one, -claim takes it, -add and -remove change who can see it, and -close ends it, optionally saving a transcript you can read back on the dashboard.

Giveaways

-gstart <time> [winners] <prize> starts one, for example -gstart 2h 3 Nitro. Entries are a button, so the giveaway keeps working across restarts. -gend, -greroll and -glist handle the rest.

Economy

A server currency with a wallet, a bank and several ways to earn. Members run -balance, -deposit, -withdraw, -pay and -eclb for the rich list, which pages and sorts by wallet, bank or net worth.

Earning. -work always pays and carries no risk. -crime pays more but can backfire and fine them a share of their wallet. -beg is small change on a short cooldown. -rob takes from another member's wallet, and when it fails the robber hands a cut of their own wallet to the person they tried it on. Each one has its own switch, payout range, cooldown and odds on the dashboard, so you can turn the risky ones off entirely. -cooldowns shows what is ready.

On a clock. -daily, -weekly and -monthly. Claim the daily on consecutive days and the streak pays a growing bonus, up to a cap you set; miss two days in a row and it starts again.

The bank. Money in the bank cannot be robbed, but a bank only holds so much. Fill it and the capacity grows, so the ceiling rises with what a member actually earns.

The dashboard owns all of the tuning, and its Members tab lists every balance so a manager can correct one without typing commands.

Money only ever moves inside a locked database row, so two commands racing each other cannot spend the same money twice or push a wallet negative.

Social notifier

Announce new YouTube uploads and Twitch streams in a channel of your choosing, with your own message and an optional role ping. YouTube works with no API key. Twitch needs credentials on the backend.

Paste a channel link, a handle or an ID and the Verify button confirms you have the right account before you save it.

Voicemaster

Three pieces, each on its own page under the Voicemaster module.

The generator is a hub voice channel. Joining it gives the member their own room, built from your defaults: category, position, user limit, bitrate, region, which permissions it inherits, whether it starts open, locked or hidden, and a name template such as {nickname}'s VC. The room is deleted when the last person leaves.

The controller is one panel of buttons and a menu, posted once to a text channel. Whoever uses it acts on the room they are currently sitting in, and only its owner can change it. The same actions exist as -vm commands.

The AFK page moves quiet people to an AFK channel. Someone counts as present while their mic is unmuted, their camera or screenshare is on, or they are talking in the server. It can watch only voicemaster rooms or every voice channel in the server.

Discord allows two channel renames every ten minutes, so a busy room may keep its old name for a while after a rename.

Autoresponders and scheduled messages

The Messages module covers four things: autoresponders that reply to a trigger, scheduled messages that post on an interval, sticky messages that stay at the bottom of a channel, and one-off announcements you send from the dashboard.

Mentioning everyone in a dashboard announcement needs to be the server owner, an administrator, or to hold Mention Everyone.

Templates and custom replies

Templates are saved messages you can post to any channel from the dashboard, built in the same editor as greetings and ticket messages.

Default messages let you rewrite what the bot says. Every customisable reply has a key and a set of variables, so you can change the wording of a ban confirmation or an error without touching anything else.

When something does not work

The bot ignores my commands

Check the prefix by mentioning the bot. Check that it can read and send messages in that channel. If a command channel is set in General Settings, commands only work there.

It says it cannot act on that member

The Umbyrx role is not above theirs. Move it up in Server Settings, Roles.

My server is missing from the dashboard

You need Manage Server in it, and the bot has to be in it. Use Refresh channels and roles after adding the bot, since Discord caches the list for a short while.

A channel or role picker is empty

Press Refresh channels and roles. If it is still empty, the bot cannot see that part of the server.

Something broke and I want the detail

The Error Logs page on the dashboard lists recent errors for your server, with what was being done at the time.

Getting help

The support server is the fastest way to reach us. Bring the server name, the command or module involved, what you expected, and what actually happened.

The full command list, with arguments and permissions, is on the commands page.