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.
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.
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.
Saw something different from what is written here? Then it is a bug, and we want to know.