Baldio is the Discord bot that connects your WowUtils group to your Discord server. It posts your setups and raid nights, keeps an officer activity feed, reminds raiders who have not answered, and lets raiders set their status without opening the site.
Link it from your group hub's Integrations tab, then set your officer and raider roles there.
Setup
On WowUtils
Link the bot
Open Integrations in your group hub and use the invite link in the Discord Bot section to add Baldio to your server.
Set your calendar timezone
Open Settings and set your calendar server timezone. Baldio reads it from your group, so event times post in the right zone with no command needed.
On Discord
Check the bot's permissions
Baldio needs View Channel, Send Messages and Embed Links in every channel you want to use it in, and Mention Roles if you want it to ping roles. Everything it posts is an embed, so without Embed Links nothing arrives.
Set your officer and raider roles
Officer roles get everything, raider roles get the raider commands. Until you set them, everyone on the server can run every command.
Set these on the website. Your group's Integrations section has them on the Discord bot status card, both for the whole server and for your team on its own.
Point people at /help
Anyone on the server can run /help. Baldio answers privately with a link to the Integrations page for whichever team that channel answers for, and a short list of what it still does from Discord. It is the fastest way to stop a raider guessing.
Missing Permissions
If a command answers with "Missing Permissions", Baldio is missing a permission in that specific channel. Channel permissions override server ones, so check the channel first.
Integrations checks these for you. Under Channels, every channel card says whether Baldio can still post there and which permission it is missing, a banner at the top counts the channels that are failing, and the channel picker greys out the ones it cannot use. Permissions are re-checked every few minutes, so a change in Discord shows up here shortly after you make it.
Who can run what
Setting Baldio up happens on the website, so what is left in Discord is short.
| Command | Who can run it |
|---|---|
/help | Anyone on the server |
/raider | An officer or raider role |
/post | An officer role |
/channel unbind-group | An officer role, plus Discord's Manage Channels |
Your Baldio roles are the gate on the middle three. In a channel bound to a team, the roles checked are that team's; everywhere else they are the server's. If no roles were ever set, everyone can run everything. Being the server owner is not a way around it: set the roles under Integrations.
Setting up a channel
Your group's Integrations section, under Channels, has a card per channel. Everything a channel does is turned on and off there, and every row on the card has an edit and a stop.
- Post events keeps the next few of your group's upcoming raids posted in that channel, updates each post within seconds of a change on the site, and removes it once the raid is over or the night is deleted.
- Post a schedule does the same for one named calendar schedule, under its current name even after you rename it on the Calendar page.
- Post keys mirrors your group's Keys board into that channel: one post per planned Mythic+ run, plus one list of everyone still looking for a group. See below.
- The activity feed turns a channel into a log of what your group is doing. Pick a channel to start it, or stop it from that channel's card.
Both posting kinds ask how many raids to keep up, whether the setup image goes on every post or only the first, and which weekdays to post on. The weekday filter is how Tuesday raids and Thursday raids end up in different channels.
Quiet hours are on by default, between midnight and 08:00 on your server's time. New raid posts wait until the window ends instead of arriving overnight; change the window or turn it off per posting row in the same dialog. A raid that actually starts during quiet hours is posted anyway, and reminders and updates to posts already in the channel are never held.
Stopping a schedule's posts leaves the ones already in Discord where they are, and they are no longer removed automatically once their raid is over.
Checking a channel works. Every channel card has a Send test post button. Baldio posts a short message in that channel, usually within a few seconds, and the card says whether it went out or names the permission Baldio still needs. The post comes from the bot rather than the website, so one that lands tells you the bot is running as well as that the channel is set up correctly.
What shows up in the activity feed
Raid nights created, cancelled, uncancelled, edited and deleted. Signup changes, including who set them when an officer answers for someone. Members linking and unlinking their Discord. Applications submitted and decided, and changes to your recruitment listing.
Roster moves too: someone joining the team, an officer adding them, someone leaving or being removed, and a raider claiming a roster spot. A join says who added them when an officer did, so it is clear whether the raider arrived on their own invite link.
Boosted groups also get the planning side: a plan published or put back into draft, a plan edited, and cooldowns updated for a boss. Plan and cooldown edits are grouped into one line per editing session rather than one per change.
Baldio posts these within seconds of them happening, and the feed's row on the channel card says when it last looked and when it last posted something. Turning the feed on starts it watching from that moment, so it reports everything from then on and nothing from before.
The feed reports what happened, it does not ping anyone.
Mythic+ keys in a channel
Post keys puts your group's Keys board in a Discord channel. Every planned run gets its own post with its date and time, the dungeons it plans to run, the organizer's note, and the five seats with who is in each. The post is edited as seats fill and free up, and it comes down when the run starts. A run cancelled on the site takes its post with it.
Underneath, one message lists everyone who has marked themselves looking for a key, with the characters they would bring and when they are free. It is edited in place rather than reposted, so the channel does not fill up with old copies, and it says so when nobody is looking.
Joining a run still happens on the site. Each post carries an Open in Viserio button that opens the board on that run's own date.
Pings are separate from posting. Pick which roles to mention, then choose which of the three moments actually ping them: when someone posts a run (on by default), when a run drops to its last open seat, and when someone new starts looking. Pick no roles and the channel gets the posts without pinging anyone. Editing a post never pings, so a run filling up one seat at a time stays quiet.
Stopping key posts leaves the ones already in Discord where they are.
Reminders before raid
Two reminders chase people for you, posted in the channel you set them up in.
- Signup reminders ping the members who have not set a status yet.
- Pre-raid warnings ping the members whose sim has gone stale, so gear checks happen before pull.
- Lead time and roles. Pick how far ahead the reminder fires, up to 24 hours before the event, and the roles to mention on the post.
If everyone has already answered, nothing is posted. A group that does not track signups or sims never gets the matching reminder.
Set these up on the website. Your group's Integrations section, under Channels, lists every reminder on every channel with an Add reminder button on each card and a remove on each row. The card explains what each kind pings about, so there is nothing to look up here. Each row also has an edit, for changing the kind, the lead time or the roles it pings. Editing keeps track of the raids the reminder has already pinged about; removing one and adding it back starts fresh, so it can ping again about a raid it had already covered.
Posting on demand
These are the /post commands, and they need an officer role.
/post next-setupposts one or all setups from your most recently updated reset. If the reset has several setups you are asked which./post setupdoes the same, but you pick the reset yourself./post eventposts a chosen event from your group calendar, with members and their status. If the event has a setup linked, the post carries it as an image.
Setup and event posts both mention up to 3 roles if you want, and both carry an Update button that refreshes the message in place rather than posting a new one below it.
Commands for raiders
These are the /raider commands. An officer or raider role can run them.
/raider set-event-statuslets a raider pick an upcoming night and set their own status. Only the statuses that night allows are offered./raider submit-wishlist-simtakes a Raidbots or QE Live link and imports it, with any warnings from the import shown back to them.
Running more than one raid team
Binding a channel points it at one team instead of the server's default. Bind each team's channels to its own team, and every post, calendar and feed in that channel follows that team.
Set this up on the website. Your group's Integrations section, under Channels, has a channel picker at the bottom of the page and an unbind on each card. A channel with no binding of its own answers for the first team linked to your server, which the page names rather than leaving you to guess.
Each team can also have its own officer and raider roles, on the Discord bot status card. They apply in that team's bound channels, and the server-wide roles cover everything else. On a server with two teams, setting one team's roles leaves the other's alone.
/channel unbind-group is the one piece of this that also works from Discord, and it needs Manage Channels. It releases whatever binding is on the channel it is run in. It exists for the case the website cannot cover: the website only lets a team release its own channels, so a channel bound to a team that is no longer around would otherwise stay bound forever.
The weekly setup post
Once a week, Baldio posts the raid setups for your next reset in a channel you pick, mentioning the roles you choose.
Set this up on the website. Your group's Integrations section, under Channels, has a Post your setups button on each channel card and at the bottom of the page. Pick a day of the week and a time, and the roles to mention. Times are in your Discord server's timezone, which the dialog names; if your server has none set, they are in UTC and it says so.
Each schedule sits on its channel's card with the day and time it posts, and when the next one goes out. After you add or change one, Baldio works out that time itself within a few minutes, so the row says it is working on it until then.
- Change it without setting it up again: another day, another time, different roles.
- Stop it and start it again. A stopped schedule keeps its settings. Starting it again picks up at the next occurrence rather than posting immediately to catch up, and clears any earlier failure so it gets a full run of chances again.
- Remove it once it is stopped.
A schedule that keeps failing is stopped for you, and the row says why, usually a permission Baldio no longer has in that channel. Fix it in Discord, then start the schedule again.
See also
- Calendar & Signups - the raid nights Baldio posts
- Loot & Wishlists - where a submitted sim ends up
- Raider Flow - what a raider does across the week