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

The raid postmemberThe raid message in the channel, with the buttons for you to say whether you are going.

What it does: When a raid is scheduled, the bot posts in the channel when it is, where it is, how many are going and who is going, in columns by class. Below are the buttons Sign up, Late, Tentative, Absent and Leave. On each click the post redraws itself, in every channel where the raid was posted. The time shows on the reader's clock.
Who sees it: Everyone who sees the channel reads and clicks, with no role and no addon. In a raid with approval, whoever clicks Sign up or Late stays in Waiting on an officer until an officer approves on the site.
Where to find it: In the channel where the raid was scheduled, through /raid create or the site. The same raid can be in several channels and servers, and can get a thread for the night's chatter.

How it should behave

Sign up and Late ask which character you are going with, or the class and spec if you do not have a character yet. Tentative, Absent and Leave ask nothing.
Late holds your spot the same way as Sign up. In the post, your name gets a ⏱.
The limits are per role: tank, healer and DPS. Whoever goes over their own role's limit goes to the Waitlist, and the click's reply says so. When a spot opens, the first on the Waitlist gets in, in signup order.
Absent leaves your name on the post, under Absent. Leave removes your name and frees the spot for the next on the Waitlist.
The post shows the name, the spec icon and ⭐ for officers. Item level and attendance never appear in it: they stay on the raid page on the site.
A closed or cancelled raid says Closed or Cancelled at the top, and all buttons turn grey, including Absent and Leave. When the signup deadline passes, the raid closes by itself.
The post comes in the server's language. The reply only you see, after the click, comes in your Discord's language.

This is not a bug

After the raid, the post does not change to show who came. The night's result (people, bosses, items) goes out in a separate message, only in the channel where the guild pinned the upcoming raids list, and each person's attendance stays on the site.
The roster says 18/25 and you still landed on the Waitlist: the remaining spot is for another role. Tank, healer and DPS are counted separately.
Whoever marked Tentative without ever choosing a character shows up with their Discord name and “(no character)”. A character is only asked of whoever takes a spot.
The post says how many signups have no addon, never who. In a raid with two or fewer confirmed, not even the number appears.

See it working Link to this feature Report on 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.

Link to this feature Report on Discord

Commands for everyonememberRegister your character, see what the guild knows about you and, in the federated guild, apply and find a core.

What it does: /register links your Discord account to your character and hands out the roles the guild configured. /profile shows your attendance, whether you came when you said you would, the next raid and your characters. In the federated guild there are also /apply (application), /pool (who has no core), /availability (the nights you can raid), /core info and /core apply. /appeal asks the Council, once, to review an expulsion.
Who sees it: Anyone on the server. /register and /profile exist on every server with the bot. /apply, /pool, /availability and /core only appear where the guild switched on the federated guild: /apply is for someone not yet in the guild, /availability for recruits and members, /core apply for members. /appeal is only for someone who was expelled.
Where to find it: Typing the command in any channel where you can write. In a locked channel, use the pinned message's buttons: Register, Apply and My data in the entry channel; See the pool and My availability in the pool channel. /appeal works in the bot's DM.

How it should behave

/register suggests roster names as you type. If the name is in the roster and nobody has taken it, you are confirmed right away. If it already belongs to another account, the bot refuses. If it is not in the roster, the bot asks for class and spec, registers anyway and links it by itself when the roster arrives.
In Forever the name has a surname. If you type only the first name and it matches someone in the roster, the bot shows the full names instead of registering.
The first character you register becomes the main. From the second on, the bot asks which is the main: the roles come from it.
The class and role roles are swapped for the main's. The member role only comes when the character is in the roster, and /register never removes it.
/profile replies only to you: nobody else sees your numbers.
/apply only works if the guild configured an applications channel, and each person has one pending application at a time. Once approved, you get the code of conduct by DM, and the recruit role only comes when you accept it.
The replies to these commands are only for you and come in your Discord's language.

This is not a bug

The bot does not touch a role the guild did not configure for /register: color, channel, or what you got for another reason stay where they are.
Where the federated guild is on and uses the same role, it is the one that hands out that role, and /register leaves it alone.
/apply, /pool, /availability and /core do not show in your command list: the guild did not switch on the federated guild.

Link to this feature Report on Discord

CoresmemberA core is a micro guild inside the guild, with its own Raid Leader, schedule and loot.

What it does: A member calls for a core with /core create: name, size and style, schedule, loot and the channels it will have. The call becomes a post in the cores forum with I'm in and I'm out, and the core's role and channels are created right away. Once the minimum is reached, the core forms: whoever called becomes Raid Leader and the others, raiders. After that the button becomes Ask to join, and the core's leadership invites, accepts, promotes and removes.
Who sees it: Calling a core and asking to join: guild members (a Council seat counts). Inviting and accepting: that core's Raid Leader and officers. Editing, removing, promoting, handing over leadership, closing and merging: only that core's Raid Leader. /core info: anyone. All of this only exists where the guild switched on the federated guild.
Where to find it: /core and what you want to do, in any channel where you can write. The call goes to the cores forum, or to the channel where you used the command if there is no forum. Requests and invites arrive by DM. Each core has its own category, with announcements, chat, rules-and-loot, roster and voice, which only the core sees.

How it should behave

Only a guild member calls a core. Each person has one open call at a time, and the guild at most 10.
The core forms at the configured minimum; with no configuration, at half the size, rounded up. Whoever called becomes Raid Leader.
Only whoever called, or the Council, cancels a call, and only while it is calling. Once cancelled, it leaves nothing behind: role, category and channels are deleted.
Inviting and accepting a request: Raid Leader and that core's officers. Removing, changing someone's role and editing schedule, loot and rules: only the Raid Leader.
Leaving the core is not leaving the guild. Whoever is left without a core returns to the pool, and whoever lost their core because it closed shows up first, with ⭐.
The Raid Leader only leaves the core by handing over leadership first.
Each click is checked again. A button that shows up is not permission: whoever cannot hears the reason, in their own Discord's language.

This is not a bug

The Council does not edit or close a core directly. It only touches a core through /council intervene, with a case open about that core.
The post of a formed core does not list who is in it. The list is in /core info and in the core's roster channel.
Whoever is removed from a core is notified, but does not hear the reason. The reason stays with the Raid Leader and the Council.
A core with no raid for 14 days (or the period the guild configured) only produces a notice in the log channel. Nobody is removed.

Link to this feature Report on Discord

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.

Link to this feature Report on Discord

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.

Link to this feature Report on Discord

Saw something different from what is written here? Then it is a bug, and we want to know.

Report on Discord

Found a mistake in the translation? Let us know on Discord.