Manual
Every GuildOS feature, in the game, on the site and in Discord: what it does, who sees it, how it should behave and what looks like a bug but is not. If what you saw contradicts what is written here, it is a bug. Tell us.
In Discord
Raid commandsofficer/raid create, /raid lock and /raid cancel: open and close signups without leaving Discord.
- What it does
- /raid create opens a form with title, when, instance and size, and posts the raid in the channel where you typed it, with the signup buttons. /raid lock ends signups and /raid cancel cancels the raid; both redraw the post. Limits per role, deadline, approval and reminder are adjusted by editing the raid on the site. It works with or without the federated guild on.
- Who sees it
- Whoever has the permission to create raids on the server: a Discord role the guild released in the site's configuration, or whoever has Manage Server. The others hear that they do not have permission.
- Where to find it
- Typing in any channel of the server. /raid lock and /raid cancel ask for the raid's code (the id field), which is the end of the raid's address on the site.
How it should behave
- Only whoever has a role with the permission to create raids, or Manage Server, gets through. The permission is checked again when you submit the form.
- The date goes in the format 2026-08-14 22:00. A blank size becomes 25, and the maximum is 40.
- The time is read in your time zone if you have already opened the site signed in. Otherwise, in the server's time zone, and the reply says which time zone it read.
- The post goes out in the channel where you typed. If Discord refuses the channel, the raid exists anyway, and the reply says why and that you can publish from the site.
- /raid lock and /raid cancel redraw all of the raid's posts: Closed or Cancelled at the top, grey buttons.
- On a server with no guild linked yet, the raid is created the same way, and the reply shows where to link the guild to see signups and attendance on the site.
- All replies are only for you and come in your Discord's language: Portuguese if it is in Portuguese, English in the other languages.
This is not a bug
- /raid cancel does not message each signup. The notice is the post, which now says Cancelled, and that raid's reminder no longer goes out.
- A closed raid still happens: closing locks the list, not the night. The reminder and the officers' alert keep going out.
- The reply says it read the time in the server's time zone: Discord does not tell a bot what your time zone is. Open the site once, signed in, and /raid starts using yours.
CouncilofficerThe federated guild's panel and what only the Council decides: applications, blacklist, cases and stepping into a core.
- What it does
- /council config opens the federated guild's panel: switching on and off, channels, roles, deadlines, names and rules, and the Council's seats. The Council approves or turns down applications with the buttons in the recruitment channel and handles the blacklist. /case open records a problem with someone: level 1 is just recorded, levels 2 and 3 go to a Council vote. /council intervene is the only door through which the Council touches a core.
- Who sees it
- Whoever has a seat on the Council, and the GM, who has one too. Whoever has Manage Server configures and gives seats, but does not approve, vote or intervene. Choosing the roles also takes Manage Roles. A core's Raid Leader and officers open a case about someone in their core.
- Where to find it
- /council and /case, in any channel where you can write; the panel and the replies only you see. Each case has a private thread in the cases channel, and each change is announced in the log channel.
How it should behave
- The federated guild starts off, in each guild. Off, of its commands only /council shows up, which is how it is switched on, and /appeal.
- The seat is what rules, not the Discord role. Manage Server gets through in the configuration and the seats, and in nothing else.
- Choosing a role takes Manage Roles on the server, and the role coming in and the one going out have to be below your highest role. Never @everyone, an integration role, or a role with Administrator, Manage Server or Manage Roles.
- Switching on the federation does not take a role from anyone. Whoever already uses the configured member role is recognized as a member on first contact.
- Only a seat approves an application and touches the blacklist. An application from someone on the blacklist arrives flagged, and Approve is refused.
- The case is read in a private thread with the Council, the core's Raid Leader and whoever opened it, never with the person it is about. In the vote, the target, whoever opened it and whoever was marked as involved stay out; the most-voted option wins, and the GM only breaks ties.
- What the bot posts in the guild's channels goes out in the server's language. The panel and the replies only you see, including refusals, go out in your Discord's language.
This is not a bug
- A refused attempt does not show in the log channel. It is recorded, but a channel that repeats every wrong click is a channel nobody reads.
- The Approve button shows for everyone who sees the recruitment channel. Whoever has no seat clicks and hears that they cannot.
- The log channel says “case #12”, never about whom or what.
- Your server calls the Council, the core or the Raid Leader by another name: the guild can rename all three in the panel.
What the bot tells officersofficerThe alert before the raid when something is going wrong, and the DM reminders about what the guild needs.
- What it does
- Before each raid, at the lead time the guild chose, the bot checks the signups and only speaks if there is a problem: a tank or healer is missing, not enough people for the size, or someone confirmed whom the game will not let in. Apart from that, it DMs officers: when the site refuses the roster, when the roster stops arriving, to ask the companion from whoever does not run it yet, and a Monday summary with the next step.
- Who sees it
- The alert, whoever sees the chosen channel; whoever configures it is whoever has the permission to create raids. The reminders, only the guild's officers: whoever has an officer rank in the game and linked their character through /register or the site, and whoever created the guild on the site or has a valid companion code. Whoever switches the reminders on and off is whoever manages a guild server.
- Where to find it
- The alert goes out in the channel chosen in Officers' alert, in the guild's configuration on the site; with no channel, there is no alert. The reminders arrive by DM, and the site's reminders page switches each one on and off.
How it should behave
- The alert only goes out if there is a problem: tank or healer below half the spots, less than 80% of the size confirmed, or someone confirmed whom the game will not let in.
- It goes out once per raid, at the chosen lead time (from 3 to 48 hours; 24 if nobody changed it), and mentions no one.
- Regulars who did not reply come along in the message, but on their own never make the alert go out.
- A cancelled raid has no alert. A closed raid does.
- There are four reminders: roster refused by the site (right away, then at most one a day), roster stopped for 3 days (once per stoppage), officer without companion (once a week each, while the roster arrives and the target has not been met, until they say they do not use Windows) and the Monday summary, from 10am in the server's time zone.
- Whoever just received a problem reminder does not get the summary on top of it, in the same round. Mute for 1 week silences only the summary; the other reminders continue.
- The alert and the reminders come in the server's language. The reply to the button you press on a reminder comes in your Discord's language.
This is not a bug
- A good week, no alert. The silence is the message: an alert that arrives every week saying all is well is one nobody reads in the week it is not.
- Missing DPS never makes the alert go out. The DPS limit is a ceiling, not a need.
- The raid got worse after the alert time and the bot did not speak again: it decides once per raid, at the chosen lead time.
- The Monday summary did not arrive: there was nothing to do, or the guild was created this week and waits for the next Monday.
Saw something different from what is written here? Then it is a bug, and we want to know.