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 the game

Raids › CoresofficerThe guild's raid teams: who is in each, in what role, and each one's rules.

In your game: Raids › Cores

What it does: Each core is a raid team with its own roster, its own format (10, 20 or 40 players), its own attendance penalties and its own points. Players ask to join with the Core Application button, in the window footer, and the officer accepts or declines in Applications. Cores put together in Discord by the bot reach the game through the companion.
Who sees it: The sub-tab is officer-only. Any member applies to a core with the Core Application button, in the window footer.
Where to find it: In the window (J or /gos), Raids tab, Cores sub-tab. Inside a core there are Roster, Applications and Configuration.

How it should behave

A new core starts at 20 players, and the format cycles between 10, 20 and 40.
The reference composition is 2 tanks, 5 healers, 6 melee and 7 ranged for 20; 2, 2, 3 and 3 for 10; 4, 10, 13 and 13 for 40.
On application, each person only picks a role their class can do: warrior tank or melee; paladin tank, healer or melee; priest healer or ranged; shaman healer, melee or ranged; druid any of them; rogue melee; hunter, mage and warlock ranged.
A person can be in more than one core. Putting someone in a core does not take them out of another.
A core's penalties apply only to it, from 0 to 100. If the core does not set one, the guild's applies (Settings › Raid); with none, 10.
Changing a core's roster sends the whole roster to the other officers.
Discord cores arrive when you log in or reload the interface, with the web companion on. Whoever came from Discord joins and leaves with Discord; whoever the officer added by hand is never touched.

This is not a bug

Creating, renaming, deleting, and changing the format and penalties stay only in your game. The other officers do not receive those changes.
In the roster, the officer can give anyone any role. The class restriction only applies on application.

Link to this feature Report on Discord

LootofficerThe master looter's tools: announce, roll and hand out, with history, equity and soft reserves.

In your game: Loot

What it does: When you are the master looter and open a boss's loot, the addon opens a window with the items: you announce, the raid rolls MS, OS or passes, and you hand it out with one click. The Loot tab keeps the History of what was handed out, the Equity (who received how much, against attendance) and the Soft Res imported from softres.it.
Who sees it: The tab is officer-only. The master loot window opens for whoever is the group's master looter. The popup with MS, OS and Pass appears for whoever has the addon and is in the raid.
Where to find it: In the window (J or /gos), Loot tab. The loot system (/roll, Wishlist, DKP or External / Off) and the distribution rules are in Settings › Loot, officer-only. Loot Master is switched on and off in Settings › General › Modules.

How it should behave

The winner is decided in this order: MS beats OS; then the priority set by the officer; then whoever has a soft reserve; then wishlist position; then whoever received fewer items; then the highest attendance in 20+ raids; finally the highest roll. The two criteria before the last come on and can be turned off in Settings › Loot.
Only /roll 1-100 (MS) and /roll 1-99 (OS), from someone in the raid, count. Any other roll is ignored.
The master loot window opens for rare or better items, and for any item that binds when equipped. The rarity threshold is changed in Settings › Loot.
With Min. Attendance for MS Roll above 0, the MS of someone below it becomes OS.
Received fewer items counts what the master looter handed out since the start of the raid session, or in the last 8 hours when there is no session.
If the loot window has already closed, the item stays in the trade queue: when you open a trade with the winner, the addon puts the item in it.
History keeps only what was handed out by the addon's master loot, up to 500 items; the tab shows the 100 most recent.

This is not a bug

Pass sends nothing: the master looter does not see who passed.
In Forever, the countdown does not go to the raid warning, and the winner is only announced to the raid when you click End Roll. The game does not let an addon speak in chat on its own.
With External / Off, the addon does not open a loot window or ask for a roll, and the history stops growing.
The loot system applies to your game: each officer picks their own, and the choice does not pass to the others.

Link to this feature Report on Discord

WishlistofficerThe guild's wish lists: who wants each item, and the priority the officer sets.

In your game: Wishlist

What it does: Shows the guild's characters with how many items they have on their wishlist and each one's attendance. In My Wishlist you build your list, in the order you want the items, marking MS or OS. In Manage Prios the officer sets, item by item, who has priority. The item tooltip says who wants it.
Who sees it: Officers only, and only when the loot system chosen in your game is Wishlist or TMB. In this version the wishlist is available to officers only.
Where to find it: In the window (J or /gos), Wishlist tab. The loot system is in Settings › Loot; the tooltip, in Settings › General › General Options.

How it should behave

Each character has their own list, with up to 50 items.
The list order is the priority: the first item is the one you want most. It changes with the arrows.
At loot time, wishlist position decides. MS or OS shows in the tooltip, but does not change who wins.
When two or more people in the raid tie at the top of an item's wishlist, only they can roll for it, in any loot system.
Your list goes to the guild when you add, remove or reorder an item, or press Sync.
An item the master looter has already given you stays at the end of the list and cannot be removed or reordered.
Save & Sync, in Manage Prios, sends the whole priority table to the guild.

This is not a bug

A member cannot open the wishlist: in this version it is officer-only.
Unknown item when adding: the game has not loaded that item yet. Try again in a few seconds.
Whoever was offline when you changed the list only receives it on your next change, or when you press Sync.

Link to this feature Report on Discord

TrialsofficerMembers on probation: how much time is left, how they are progressing and what the officers think.

In your game: Trials

What it does: Lists who is on trial, with iLvl and how much it has changed since the start, the sponsor, the days left and the status. Clicking a row opens the officers' comments, where you add yours. OK approves and X denies.
Who sees it: Officers only.
Where to find it: In the window (J or /gos), Trials tab. To put someone on trial, right-click their name in the Roster and choose Mark as Trial. Switch it on and off in Settings › General › Modules.

How it should behave

Every trial lasts 30 days, counted from the moment it was marked.
The sponsor is the officer who marked the trial.
The days left are green above 14, gold above 7 and red at 7 or fewer.
OK and X only appear while the status is TRIAL.
The most recent trial is on top.
A comment has up to 200 characters and keeps who wrote it and when.
Each new trial, status change or comment goes to the other officers right away, and everything is resent every 5 minutes.

This is not a bug

A trial only becomes EXPIRED when an officer logs in or reloads the interface. Until then it shows 0d in red.

Link to this feature Report on Discord

LeadershipofficerThe officers' tools: ranks, inactivity, suggestions, message of the day, log, ban list, engagement and presets.

In your game: Leadership

What it does: Eight sub-tabs: Ranks, Inactivity, Suggestions, MOTD / Info, Audit Log, Ban List, Engagement and Presets. From here you see who has gone missing, who deserves a promotion, who was banned and who helped with recruitment. Officer notes are in the Roster: right-click the name, Add Officer Note.
Who sees it: Officers only.
Where to find it: In the window (J or /gos), Leadership tab. Who counts as an officer is chosen in Settings › Officer › Officer Ranks. Switch it on and off in Settings › General › Modules.

How it should behave

The sub-tabs appear in this order: Ranks, Inactivity, Suggestions, MOTD / Info, Audit Log, Ban List, Engagement and Presets.
Promote, demote and remove are actions the game protects: the buttons open Blizzard's guild window so you finish there.
Inactivity lists, untouched, whoever has been away for 30 days or more, the longest gone first.
Suggestions flags for promotion whoever is neither an officer nor a trial and has 80% attendance or more, from highest to lowest.
When a banned player joins the guild or whispers you, officers get a warning in chat and on screen.
An expired temporary ban stays on the list for 7 days, marked as expired.
An officer note has up to 200 characters, each member keeps up to 50, and a new note goes right away to the other officers.

This is not a bug

Whoever just became an officer needs to reload the interface for notes, trials and the welcome to start in their game.
BANNED in the tooltip shows for everyone who has the addon, not only officers.
A note written while another officer was offline only reaches them when someone presses Sync.

Link to this feature Report on Discord

On the site

Start hereofficerThe wizard that links your guild to GuildOS, from Discord to the first roster.

What it does: The door says what you need before sitting down and the four places the path goes through: in the browser (server, bot, guild and the first raid), on Windows (the companion), in the game (the addon sends the first roster) and with the guild (invite, the /register roles and page). You can do it all at once, or only part today: only the raid on Discord, or only the roster from the game. Each step says what to do and follows live what happens outside the page.
Who sees it: The door is public: anyone reads it before authorizing anything. The steps ask you to sign in with Discord and only work on a server where you have Manage Server. Whoever manages no server goes straight to picking their character.
Where to find it: In Start here, in the header, or at guildos.me/start. While something is missing, the Set up badge in the header and the “guild N of M” ring on the guild bar also lead here.

How it should behave

Nothing is stored to know whether a step is done: the wizard looks at what already exists. Closed the tab midway? When you come back, it continues from the right step.
The chosen server only counts if you have Manage Server on it. Someone else's server is ignored.
The companion step is only done when the companion has talked to the site, or when a roster has arrived. Creating the code is not enough.
“Call the guild” is done when at least half the roster has the addon.
In the full suite, the first raid, the invite, the roles and the page are optional and can be skipped. A step that depends on another not yet done does not open.
While it waits for something from outside, the page refreshes itself: every 5 seconds waiting for the bot, 15 waiting for the first raid, 30 waiting for the companion and the roster.
“Send to my PC” sends you at most one message per minute.

This is not a bug

Clicked Start here and landed on Your character? You do not manage any Discord server, and for someone who only plays, saying who their character is is everything.
“The companion has not shown up yet” after 3 days with the code created: no companion has talked to the site with that code. It is almost always the Windows warning or the code not pasted.
Played and the roster did not arrive? The game only saves the roster when you do /reload or leave the game, and only after /gos web on.
“The guild name did not match”: the name on the site has to be the game's. Capitals and the < > signs do not count; accents and spaces do. “Use the game's name” fixes it with one click.

Link to this feature Report on Discord

Schedule a raidofficerThe form that schedules a raid and announces it in the Discord channels.

What it does: You give a title, the day and time, pick the raid from the list (or write another), the size, the composition and the channels to announce in. You can repeat it every week, warn ahead, close signups some hours before, close when it fills up and require an officer to approve each signup. On creating, the bot posts the raid with button signup in each chosen channel.
Who sees it: Whoever can schedule a raid on the site, through a Discord role with that permission in the configuration, or whoever has Manage Server on a guild server. The others go back to the raids list.
Where to find it: In Schedule a raid, at the top of the raids page. The wizard's first raid step also brings you here.

How it should behave

The day and time you type are read in your time zone, the one that appears next to “When”.
The raid list is the one for the guild's game. A night that is not on the list goes through the free field.
If no channel accepts the post, the raid is not created, and the page shows the reason Discord gave.
Past a role's limit, the signup goes to the waitlist, in the order people replied. Nobody is turned down.
“Repeat every week” turns the chosen day and time into the fixed time and keeps 1 to 8 weeks up (3, if you do not change it).
With no size chosen, the size of the raid from the list applies, and the spots by role come from it.
The channels where the last raid was announced come already ticked.

This is not a bug

The soft reserve option does not show: the soft reserve site does not have WoW: Forever raids.
“No channel available”: the bot only offers channels it can see and where it can post. Check its permissions in the channel.
The “who usually can” line only appears when someone marked the nights that work in Your guilds.
A raid scheduled only with the free field never links itself to the night the addon records: only a raid chosen from the list links. Link it by hand on the night's page.

See it working Link to this feature Report on Discord

Reminders on DiscordofficerWhat the bot sends officers in a direct message, and when.

What it does: Shows who the officers are and whether each one has the companion running, the guild's target (at least 2, or all) and the four alerts to switch on and off: Monday summary, companion stopped, officer without companion and upload refused. Beside them, the messages as Discord will show them, in the server's language.
Who sees it: Only whoever has Manage Server on a guild Discord server. For the others, the page answers that it is not here.
Where to find it: On the dashboard, in the “reminders on Discord” card, under “See the messages”; or in the configuration, under Reminders on Discord.

How it should behave

An officer is whoever has an officer rank in the game (the leader, the rank right below, or a rank with one of these words in its name: officer, leader, master, vice, GM, oficial, líder or mestre) and linked the character to Discord through /register. Whoever created the guild on the site or a companion code also counts, unless the roster shows the person playing without an officer rank.
An officer has a companion when a code they created was used in the last 7 days.
The summary goes out on Monday, from 10am in the time zone of the guild's Discord server, which today is Brasília's for every guild. With nothing to do, it does not go out.
“Companion stopped” goes out once per stoppage, after 3 days without a roster, and only if a roster has arrived before.
“Officer without companion” asks each officer at most once a week, and stops asking when they answer that they do not use Windows.
“Mute for 1 week” silences only the Monday summary. The problem alerts continue.
The messages go out in the language of the guild's main server.

This is not a bug

No officer on the list: they appear when the roster arrives and each one links their character through /register.
A guild created this week does not get a summary until the next Monday.
An officer gets only one message at a time: whoever just got the companion stopped alert does not get the summary on top of it.

Link to this feature Report on Discord

ConfigurationofficerWhere the guild is adjusted: name, public page, servers, permissions, roles and companion codes.

What it does: Changes the name and where the guild lives (ruleset and region) and writes the public page. Switches Discord servers on and off, picks the main one and each one's language. Says which Discord roles can schedule raids, set up the guild and change permissions, and which roles /register hands out. Creates and revokes companion codes, picks the channel for the pinned raid list and for the officers' alert, and switches the public character pages on or off.
Who sees it: Whoever has Manage Server on a guild server, or a role with the permission to manage the guild or to manage permissions. Anyone else who opens the page sees the notice that they need to manage a server tied to the guild.
Where to find it: In settings, on the guild bar (only shows for whoever can). The warnings at the top and the wizard also bring you here.

How it should behave

Renaming the guild changes the key the addon uses: the next roster has to come from a guild with that name in the game.
Whoever has Manage Server can do everything. With no role configured, only those people can act.
Whoever only has the permission to manage the guild opens this page, but does not change permissions: that is for whoever has Manage Server or the permission to manage permissions.
The guild's last server cannot be switched off.
A server's language applies to what the bot posts in its channels. The reply only you see follows your Discord's language.
A companion code appears only once, when it is created. Lost it? Create another and revoke the old one.
Switching off the public pages takes down each character's page and the randomly picked characters on the guild page.

This is not a bug

The server's language only has Português and English: what the bot posts in channels still comes out only in those two.
/register did not hand out a role? The bot needs Manage Roles and its own role above the ones it hands out. And the member role only goes to whoever the roster confirms.
The officer alert does not arrive before every raid: it only speaks when there is a problem, such as a gap in tank or healer. With no problem, the bot stays quiet.
Switching off the public pages does not take down the guild page: it only takes down each character's pages and the random pick.

Link to this feature Report on Discord

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.

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.