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

NowmemberThe first tab: the next raid, what is waiting for you and what just happened in the guild.

In your game: Now

What it does: One column with three cards: Next Raid, with the countdown; Needs Me, with whatever is waiting for an action from you; and Activity, with the guild's last 48 hours. With a wide window, the next event with its reply buttons, your readiness, the guild pulse, recruitment, your loot and the guild chat appear beside it. Clicking a line opens the screen that handles it.
Who sees it: Everyone, and it cannot be turned off. Officers get more alerts in Needs Me.
Where to find it: Open the window with J or /gos: it is the first tab. It is also in the minimap button menu (right-click).

How it should behave

Next Raid shows the next Raid-type event in the calendar that has not started yet, with a countdown: 4:12:38 under a day, 2d 4h over a day.
Needs Me shows You haven't replied when the next calendar raid, within the next 7 days, still has no answer from you.
For officers, it also shows trials about to expire (in red, first), members inactive for more than 30 days, promotions to review and applicants waiting. At most 5 lines.
Activity covers the last 48 hours, newest on top, with up to 12 lines: who joined, left or changed rank, loot handed out, who leveled up and the raids logged.
The cards on the right only appear with a wide tab. In a narrow window, only the column remains.
While the tab is open, the countdown ticks every second and the lists refresh every 10 seconds.

This is not a bug

Opened the window and did not land on Now? The window reopens on the last tab you used.
For a member, Needs Me almost always says All caught up: the other alerts are officer-only.
A raid scheduled on the site never shows up as unanswered: the reply is made through Discord or the site.
A guild join or leave can be missing from Activity. It comes from system messages, read by whoever has the addon and was online at the time.

Link to this feature Report on Discord

RostermemberThe guild list, with level, class, iLvl, professions and everyone's sheet.

In your game: Roster

What it does: Shows every member, with level, class, iLvl, race, when the data arrived, professions and zone. At the top, cards count members, players, online, average iLvl, average attendance and how many use Guild OS. On the left you filter by online, rank or class. Clicking a name opens the person's sheet, with gear, professions, attendance and loot; right-click opens the action menu.
Who sees it: Everyone, and it cannot be turned off. Mark as Trial and officer notes are officer-only. Promote, demote and remove follow your rank's permissions in the game, and the public note shows for whoever the rank lets edit it.
Where to find it: In the window (J or /gos), Roster tab. The Analytics button, on the tab's bar, opens the guild charts.

How it should behave

Whoever is online always comes first. Untouched, the order is by level, highest to lowest, with ties broken by name.
Search looks in the name, class, zone and rank. Only numbers search by level: 60, 50-59, >=55, or several separated by commas.
Zone only shows for whoever is online. Last seen shows Now for whoever is online; for the others, how long ago their addon's data arrived.
In a narrow window, columns disappear in this order: Zone, Professions, Last seen, Race and iLvl. Member, Lvl and Class never disappear.
The public note, under Add Note in the right-click menu, fits 31 characters without accents (fewer with accents). An empty box deletes the note.
About 10 seconds after you log in, the addon may ask whether your other characters in the guild are alts of your highest-level one. Not now stops it from asking about the same group again.
Your data goes to the guild a few seconds after you enter the game and then every 5 minutes. The Sync button, in the footer, forces it right away.

This is not a bug

iLvl, race, professions with levels, gear and stats only show for whoever has the addon and has already sent their data.
Last seen is not the last login to the game: it is the age of the person's addon data.
Race shows in the language of the person's game: Orco for someone playing in Portuguese, Orc for someone playing in English.

Link to this feature Report on Discord

RaidsmemberThe tab that gathers everything raid-related: attendance, raiders, cores, audit and tools.

In your game: Raids

What it does: One tab with five sub-tabs: Sessions, Raiders, Cores, Audit and Raid Tools. Each has its own page in this manual.
Who sees it: Everyone. The Cores sub-tab is officer-only: for a member, its button does not even appear.
Where to find it: Open the window with J or /gos and click Raids. It is also in the minimap button menu (right-click). Switch it on and off in Settings › General › Modules.

How it should behave

The sub-tabs appear in this order: Sessions, Raiders, Cores, Audit and Raid Tools.
The first time, the tab opens on Sessions. After that, it returns to the last sub-tab you used, until you reload the interface.
For anyone who is not an officer, not even a direct shortcut opens the Cores sub-tab.
Turned off in Settings, the tab disappears from the window right away, without reloading the interface.

This is not a bug

Cannot see the Cores sub-tab? It is officer-only, and an officer is whoever has one of the ranks ticked in Settings › Officer › Officer Ranks. Untouched, that is the Guild Master and the rank right below.
Became an officer with the game open and Cores did not appear? The tab decides this when it is first built: reload the interface.
Turning off the Raids tab only hides the tab. Raids keep being logged.

Link to this feature Report on Discord

Raids › SessionsmemberRaid attendance, measured by the addon without anyone writing it down.

In your game: Raids › Sessions

What it does: The addon notices on its own when you enter a raid and notes who is in the group. Each night becomes a session, with the bosses killed and the wipes, and the nights of the same raid in the same week merge into one lockout. At the bottom, Member Attendance gives each person's percentage, split by core.
Who sees it: Everyone sees the sub-tab. Each game records the nights the player was present at, and sessions are only exchanged between officers: the whole guild's attendance stays with them. Only officers see the X that deletes a session and change the penalties.
Where to find it: In the window (J or /gos), Raids tab, Sessions sub-tab. The guild's penalties are in Settings › Raid › Raid Tracker, and each core's in Raids › Cores › Configuration.

How it should behave

In Forever every raid is logged. The session starts when you enter the instance, and also when you log in or reload the interface already inside it.
Whoever is in the group is noted on entering, every 5 minutes, at every change in the group and at the start and end of each boss.
After you leave the instance, the session waits 20 minutes. If you return to the same raid in that time, it continues; if you enter a different raid, the previous one closes right away.
Each lockout (the same raid, of the same core, in the same week) is worth 100 per person. Whoever was not in the group at the first note loses the late-arrival penalty; whoever was not in the last, the early-departure penalty. Untouched, each takes off 10.
The lockout week turns over on Tuesday at 00:00 UTC, which is Monday at 21:00 in Brasília.
Only raids of 20 players or more count toward the percentage. A 10-player raid is logged, but does not count.
A night only counts if at least half of the people who passed through the group are from the guild. If not, the addon warns in chat and attendance does not change.

This is not a bug

The No Consumables penalty shows in the settings, but in Forever nobody gets it: the addon does not read flasks or food here.
Cannot find a 10-player raid in the list? The list opens filtered to 20+ players; press All.
Two players can see different numbers: a member only sees the nights they logged themselves, and the penalties live in each officer's own game, without passing from one to another.

See it working Link to this feature Report on Discord

Raids › RaidersmemberWho is at the level cap, which roles they are willing to play and whether their gear is ready.

In your game: Raids › Raiders

What it does: Lists the guild members at level 60, online or not, with their roles (T, H, D), gear state (Ready, Gearing, Missing), iLvl, spec and a note. At the top, cards count raiders, online, tanks, healers, dps and ready.
Who sees it: Everyone sees it. Only officers change roles, gear and note; for the others the list is read-only. Everyone reads the note an officer writes here.
Where to find it: In the window (J or /gos), Raids tab, Raiders sub-tab. You set your own roles in Settings › General › My Profile.

How it should behave

Every member at level 60 is included, offline ones and alts too, in alphabetical order. There is no way to add or remove someone by hand.
Each person's roles are the ones they ticked in My Profile, until an officer touches the row. From then on the officer's roles apply, starting from the ones the person had ticked.
Gear cycles with each click: —, Ready, Gearing, Missing.
The note has up to 120 characters.
Whoever has more than one role counts in each of them in the cards at the top. Ready counts whoever has Ready gear.
An officer's change reaches the guild in seconds, and whoever logs in later receives the list from an online officer.

This is not a bug

iLvl and Spec showing —: the person does not have the addon, or their addon has not sent that data yet.
Changed your roles in My Profile and nothing changed here? An officer has already touched your row, and their choice applies.
The roles here (T, H, D) are not the cores' roles (Tank, Healer, Melee, Ranged). They are separate lists.

Link to this feature Report on Discord

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

Raids › AuditmemberWho in the guild is wearing unenchanted gear.

In your game: Raids › Audit

What it does: It has three parts. Readiness lists each member with status, iLvl and enchants. Enchants lists who has an unenchanted piece and in which slot. Sync shows how many in the guild have the addon and who is on a different version from yours.
Who sees it: Everyone.
Where to find it: In the window (J or /gos), Raids tab, Audit sub-tab. It opens on Readiness.

How it should behave

Nine slots are checked: head, shoulders, chest, legs, feet, wrists, hands, back and main hand. Rings, neck, trinkets, waist, off hand and ranged weapon are left out.
An empty slot does not count as missing: only an equipped piece without an enchant.
In Enchants, whoever has the most enchants missing comes first; ties, by name. With nobody missing, it shows Everyone is fully enchanted!
In Readiness, whoever has one enchant missing is marked to check, whoever has not sent data gets —, and the rest are ready.
iLvl is the average of the equipped pieces; an empty slot does not pull the average down.

This is not a bug

Only people with the addon appear: each person's gear is sent by their own addon.
In Readiness, besides iLvl, only the enchants column has content in Forever: the other two always stay at —, and the target button never leaves All raids.

Link to this feature Report on Discord

Raids › Raid ToolsmemberThe group's composition, the buffs it covers and the cooldowns it has, before the pull.

In your game: Raids › Raid Tools

What it does: Composition shows how many of each class there are and which raid buffs are covered. Cooldowns shows which important cooldowns the group has and which are missing.
Who sees it: Everyone.
Where to find it: In the window (J or /gos), Raids tab, Raid Tools sub-tab.

How it should behave

In a raid, the list is the current raid; in a group, the current group with you; alone, the online guild members.
The buffs checked are Fortitude and Spirit (priest), Intellect (mage), Stats (druid), Attack Power (warrior or paladin), Blessings (paladin) and Totems (shaman).
The cooldowns checked are Battle Rez and Innervate (druid), Power Infusion (priest), Soulstone (warlock) and Salvation (paladin). One that nobody covers shows as missing.
A buff or cooldown counts as covered when the class that provides it is in the group. The spec and whether the buff is active are not checked.
The screen does not change by itself when the group changes: press Refresh or open the sub-tab again.

This is not a bug

Without a group, the screen shows the online guild instead of staying empty.

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

DKPmemberThe guild's points: how many each person has, earned and spent.

In your game: DKP

What it does: Shows the points standings: current, earned and spent. The officer gives or takes points with a reason, and under More... opens the Guild Points window, with points for the whole raid, decay and history. The points belong to the active core, or to the guild when no core is active.
Who sees it: The tab only appears when the loot system chosen in your game is DKP / Points. Only an officer changes the loot system, and the choice does not pass from one player to another: in practice, whoever sees the tab is the officer who chose DKP. Anyone opens the points window with /gos points and sees the standings, without being able to change anything.
Where to find it: In the window (J or /gos), DKP tab. The loot system, the mode and the values (points per boss, decay, starting points, cost per item) are in Settings › Loot, officer-only.

How it should behave

Untouched, each boss is worth 10 points, everyone starts with 0, decay is 0% and the cost per item is 0, which means off.
With Auto-award on boss kill on, the boss's points go to everyone in the raid when it dies. The one who awards is the group leader, and only if they are an officer and the raid session is running.
Decay does not run by itself: the officer presses Apply Decay, and each person loses the configured percentage of what they have, rounded.
With a cost per item above 0, whoever wins an item from the master looter pays that cost, and the raid sees the notice. It applies when the loot system is DKP and the master looter is an officer.
The standings go from whoever has the most points to the fewest; ties, by name.
Each change goes out right away to everyone in the guild with the addon and is counted only once. Only a change made by an officer is accepted.
The history keeps the last 500 changes of each core.

This is not a bug

In the EPGP and Loot Council modes, points work as in DKP: the mode changes the name shown, not the math.
Whoever was offline when someone gained points only catches up when an officer presses Sync in the points window.
The typed name is used as is: a typo creates a new row in the standings.
Changed the active core and the points changed? Each core has its own points.

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

ProfessionsmemberWho in the guild makes what, and what nobody makes yet.

In your game: Professions

What it does: Lists the guild's professions with each one's recipes and who can make them. In Recipes you search for a recipe and filter by All, In guild or Nobody makes it; in Crafters you see who has the profession and at what level. Clicking a recipe opens a card with reagents, source and crafters, with Whisper for whoever is online.
Who sees it: Everyone. If the tab is turned off, the names of whoever makes the item still show in the tooltip.
Where to find it: In the window (J or /gos), Professions tab. The Find Crafter button is at the top of the tab. Switch it on and off in Settings › General › Modules; the tooltip, in Settings › General › General Options.

How it should behave

Your recipes are read without you opening the profession window. Opening the window only adds any recipe the addon does not know yet.
Each person's addon tells the guild what they know a few seconds after they enter the game, and then every 10 minutes.
Learned a recipe? It goes out to the guild about 10 seconds later.
In the list on the left, primary professions come first and secondary ones after, each group in alphabetical order.
The crafters column shows up to 3 names, online ones first, and +N for the rest. With nobody, it shows nobody in red.
In Crafters, whoever has the addon comes first, from highest level to lowest; whoever does not is at the end.
In an item's tooltip, Created by: lists who in the guild makes the item. With Only when holding Shift ticked, the line only appears while Shift is held.

This is not a bug

Whoever does not have the addon shows up only with the profession name, with no level and no recipes, and never counts as someone who makes a recipe.
With the tab open, what arrives from the guild does not show up by itself: close and reopen the tab, or click a profession.

Link to this feature Report on Discord

GuildmemberThe tab for guild life: calendar, activity, bulletin, calls to arms, polls and chat.

In your game: Guild

What it does: One tab with six sub-tabs: Calendar, Activity, Bulletin, Call to Arms, Polls and Chat. Each has its own page in this manual.
Who sees it: Everyone. No sub-tab is officer-only; what changes for officers are the buttons inside them.
Where to find it: Open the window with J or /gos and click Guild. It is also in the minimap button menu (right-click). Switch it on and off in Settings › General › Modules.

How it should behave

The sub-tabs appear in this order: Calendar, Activity, Bulletin, Call to Arms, Polls and Chat.
The first time, the tab opens on Calendar. After that, it returns to the last sub-tab you used, until you reload the interface.
In a narrow window, the sub-tabs wrap onto two lines instead of disappearing.

This is not a bug

Turning off the Guild tab only hides the tab. Calls to arms keep arriving and the calendar keeps receiving events.

Link to this feature Report on Discord

Guild › CalendarmemberThe guild's events on a month calendar, with who is going.

In your game: Guild › Calendar

What it does: A month calendar. Click a day to see the events and reply Going, Maybe or Not going, with your role. Officers create, edit and delete events. Raids scheduled on guildos.me also appear here, with whoever signed up on the site.
Who sees it: Everyone sees it and replies. Only officers see New Event, Edit and Delete.
Where to find it: In the window (J or /gos), Guild tab, Calendar sub-tab. In Now, the Open calendar button goes straight to the day of the next raid.

How it should behave

The month starts on Sunday and shows six weeks.
An event has a type: Raid, Dungeon, PvP, Farm, Social or Other. If you do not choose, it is Raid.
A new event starts at 20:00, for 20 players. The size cycles between 10, 20 and 40.
The title has up to 60 characters and the description up to 500.
Each person has one reply per event. Replying again replaces the previous one.
The count of tanks, healers and dps adds up only those who replied Going.
A raid scheduled on the site has no reply button. It shows Signup is through Discord or the site, the list time and who is going, who is waiting for approval, maybe, on standby and who is not going.

This is not a bug

A site raid only reaches the calendar when an officer who uses the companion logs in or reloads the interface. Whoever signed up on the site after that shows up the next time.
An event created or replied to while you were offline may not reach you, and the list of who is going can differ between two players.
Times are from your computer's clock.

Link to this feature Report on Discord

Guild › ActivitymemberWhat happened in the guild in the last 7 days, in a few lines.

In your game: Guild › Activity

What it does: A summary of the last week: new members, who left or was removed, raids logged, items handed out, the change in your points, who reached the level cap, the next event, new bulletin notices and new polls. These are the same lines as the summary that appears when you log in.
Who sees it: Everyone. Officers also see trials ready for a decision and how many members are inactive.
Where to find it: In the window (J or /gos), Guild tab, Activity sub-tab.

How it should behave

Shows only the last 7 days. With nothing in that period, it shows Nothing new in the last 7 days.
New members appear with up to 3 names and +N for the rest.
Who left and who was removed appear as a count, not name by name.
From the bulletin, up to 3 new notices are included.
An event in the next 24 hours appears as soon, with the day and time.

This is not a bug

Promotions and demotions do not appear here. The full log is in Leadership, which is officer-only.
A new member is someone your addon saw for the first time, not the date the person joined the guild.

Link to this feature Report on Discord

Guild › BulletinmemberShort notices from the officers to everyone in the guild who has the addon.

In your game: Guild › Bulletin

What it does: Officers post short notices and everyone reads them. The newest notice is on top, with who wrote it, the day and the time. New notices also appear in the summary the addon shows when you log in.
Who sees it: Everyone who has the addon reads it. Only officers see the writing box, the Post button and the × that deletes a notice.
Where to find it: In the window (J or /gos), Guild tab, Bulletin sub-tab.

How it should behave

The bulletin keeps the 20 newest notices. The 21st pushes the oldest out.
A notice has up to 200 characters.
Only officers post and delete. A notice stays until it is deleted or pushed out.
Posting or deleting sends the whole bulletin to the guild, and everyone ends up with the newest version.
Whoever was offline receives the bulletin from an online officer when they log in.

This is not a bug

Logged in and the bulletin is empty or old? It comes from an officer with the addon open. With no officer online, it waits.

Link to this feature Report on Discord

Guild › Call to ArmsmemberAn officer calls the guild to a world boss, a PvP fight or an event, and everyone is notified right away.

In your game: Guild › Call to Arms

What it does: The officer picks a type (World Boss, World PvP, Defend, Event / Farm or Rally) or a custom template, and sends it. Whoever has the addon gets a popup at the top of the screen, with sound, the place and how many are already on the way, and can reply On my way. A line goes out in guild chat for whoever does not have the addon.
Who sees it: Everyone who has the addon receives it and sees the recent calls. Only officers see Send a call, the templates and Also post to guild chat. Each person chooses in My alerts how they want to be notified.
Where to find it: In the window (J or /gos), Guild tab, Call to Arms sub-tab. Your alerts are right there, in My alerts.

How it should behave

An officer sends at most one call per minute. The wait still applies after reloading the interface.
The popup stays on screen for 30 seconds, one at a time; the newest call takes its place.
A call that arrives less than 10 seconds after the last popup becomes a chat line, with no popup.
With Mute in instances and combat on, inside an instance or in combat the call arrives as a chat line.
A call more than 10 minutes old does not show up.
A long message is cut: 140 characters fit, fewer if it has accents. {zone} becomes the zone the officer is in.
The recent calls list shows the last 10.

This is not a bug

After reloading the interface, the recent calls list starts empty. A call is a live alert, it is not stored, and whoever logs in later does not see it.
The guild chat line does not go out if the game is holding chat at that moment, such as during an encounter. The popup goes out anyway.
Two calls from the same officer less than 30 seconds apart: the second is ignored by whoever receives it.

Link to this feature Report on Discord

Guild › PollsmemberOfficers ask, the guild votes.

In your game: Guild › Polls

What it does: An officer creates a poll with a question and 2 to 6 options. Everyone votes by clicking an option and sees how many votes and what percentage each option has. The officer closes the poll whenever they want.
Who sees it: Everyone who has the addon sees and votes. Only officers see the create box and the Close button.
Where to find it: In the window (J or /gos), Guild tab, Polls sub-tab.

How it should behave

The question has up to 150 characters, and the options go one per line, from 2 to 6. A 7th line is ignored.
Each person has one vote. Clicking another option changes your vote while the poll is open, and your choice is highlighted.
A closed poll takes no votes and shows [closed] before the question.
Open ones stay on top; within each group, the newest first.
Only officers create and close polls. A poll does not close by itself.

This is not a bug

A poll created while you were offline does not reach you later. It and the votes only reach whoever has the addon open at the time, so the count can vary between two players.

Link to this feature Report on Discord

Guild › ChatmemberGuild chat inside the window, with what was said while you were away.

In your game: Guild › Chat

What it does: Shows guild chat and lets you reply from there. In Forever the server keeps the history, so what was said while you were offline also shows up. Each guild channel you can read gets a tab: Guild, Officers and the ones the guild created.
Who sees it: Everyone. The Officers tab only appears for whoever the game lets read the officer channel.
Where to find it: In the window (J or /gos), Guild tab, Chat sub-tab. In Now, with a wide window, the same chat appears in the Guild chat card.

How it should behave

Each channel shows up to the last 200 lines.
Channel tabs only appear when there is more than one channel to choose from.
Your line appears when the game sends it back, not the instant you press Enter.
If you scrolled up, a new line does not pull the chat down. It only follows new lines when you are at the bottom.
Item and player links stay clickable, and a line break becomes a space.

This is not a bug

During an encounter the game locks chat for addons: the message does not go out, the addon warns you and the text stays in the box so you can send it later.
While chat is locked, you cannot switch channels.

Link to this feature Report on Discord

AlliancememberLinks your guild to allied guilds, with chat, bulletin and crafters in common.

In your game: Alliance

What it does: An alliance joins several guilds: an alliance chat channel, a bulletin where each guild posts notices, the allied guilds' crafters in the search for who makes an item, and the events each guild shares. It has four sub-tabs: Bulletin, Chat, Overview and Management.
Who sees it: Officers always see the tab; members, only when their game is already in an alliance. Bulletin and Chat only appear with the guild in an alliance. Management is officer-only, and posting on the bulletin or inviting guilds belongs to the ambassadors.
Where to find it: In the window (J or /gos), Alliance tab. Founding, joining and inviting are in Management. Switch it on and off in Settings › General › Modules.

How it should behave

An alliance has up to 16 guilds, and each guild up to 8 ambassadors.
The tag has up to 12 letters and numbers, no accents or spaces, and becomes uppercase.
The alliance chat is a game channel named GOS plus the tag.
The join code has 8 characters, without O, 0, I and 1 so they are not confused. A guild that has the code joins without waiting for anyone to approve.
An invite reaches the officer as an Accept or Decline popup, which disappears after 60 seconds.
On the bulletin, each notice has up to 200 characters, each guild keeps its 20 newest and only deletes its own.
A calendar event only goes to the alliance if Share with the alliance is ticked on it. It comes unticked.

This is not a bug

The alliance channel is public: anyone who guesses the name can join. Do not put anything sensitive there.
Blocking a guild applies only to your game, and nobody is notified.
In Overview, the seen count only counts whoever has the addon and is visible: it is a minimum, not the total online.
A member who receives an alliance invite only sees a notice in chat: accepting is up to an officer.

Link to this feature Report on Discord

RecruitmentmemberThe recruitment message in the channels, the welcome for new members and the keyword invite.

In your game: Recruitment

What it does: For officers: a recruitment message that comes back on the interval you choose and goes out to the channels with one click, a welcome message for whoever joins the guild, the automatic keyword invite by whisper and the Scanner, which looks for players without a guild. For members: it shows whether the guild is recruiting and lets you help spread the word.
Who sees it: Everyone sees the tab, but each person sees a different screen: the officer configures; the member sees the message and chooses whether to help spread it.
Where to find it: In the window (J or /gos), Recruitment tab. Switch it on and off in Settings › General › Modules.

How it should behave

It comes off. The default interval is 120 seconds, and the minimum is 60.
Each send to a channel takes a click: a popup appears with the channel and the exact text, and it only goes out if you press Post.
Between two sends from the same game, at least 30 seconds pass; a click before that does nothing.
A member only helps spread it if they choose to. The officer sets up to which rank members may spread it in Helping Members; if not set, any rank.
A member receives at most 40 spread requests per session; after that the addon pauses on its own and warns.
The welcome comes on and goes out in guild chat through an officer's game; with several officers online, only one sends. In Forever, it waits for the officer to click before going out.
The automatic invite comes off. When on, whoever whispers the keyword (untouched, ginv) is invited, with a 5-minute wait per name; banned players never. In Forever, each invite waits for the officer to click Invite.

This is not a bug

You have to click for the message to go out: the game does not let an addon post to a channel on its own.
The popup without the Post button? You are not in any of the chosen channels: join one of them.
Changed the message and members are still spreading the old one? It reaches them with Broadcast to Members, when turning it on or off, or on the resend every 5 minutes while recruitment is on.
Send Now does nothing for a member when the guild is not recruiting.

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

WebmemberThe bridge to guildos.me: publish the guild to the site and bring the raid planned there into the game.

In your game: Web

What it does: In Publishing you switch on sending the guild's data to the site. In Planned Raid the raid scheduled on guildos.me appears: how many are coming, the composition, who is on standby and who needs a look. Bring roster loads the list, Invite calls everyone and Groups puts each person in the group the site planned. What carries the data between the game and the site is the companion, a small program on your PC.
Who sees it: Everyone sees the tab, and publishing is each person's choice. Invite needs a loaded roster and publishing on; Groups needs you to be in a raid as leader or assistant.
Where to find it: In the window (J or /gos), Web tab. First time? The three steps are on the tab itself. Switch it on and off in Settings › General › Modules.

How it should behave

Publishing comes off. While it stays that way, nothing leaves the game.
The addon saves what goes to the site when you leave the game or reload the interface. Publish now does exactly that, and does not work in combat.
Whoever publishes sends the whole guild as their addon knows it: every roster member, with the data that arrived from them.
The roster planned on the site arrives when you log in or reload the interface, and only with publishing on.
Standby and Needs a look show up to 5 names; the rest appears as +N on the site.
Invite calls everyone in the roster who is not in the group yet, and also whoever signed up with a character the site did not know but who is in the guild. Whoever is already in the group is not invited again.
Groups only works in a raid, for the leader or an assistant, and only moves whoever is in the wrong group.

This is not a bug

The site's roster does not show up with the game open: reload the interface. The game only reads what the companion left when it loads.
Invite or Groups greyed out? The reason is written under the button, for example Turn publishing on first.
The companion updates every hour. The warning that it is sending nothing only appears after 3 days without a reply.

See it working Link to this feature Report on Discord

SettingsmemberWhere you switch each part of the addon on and off and adjust how it behaves.

In your game: Settings

What it does: Five categories. General has My Profile (the roles you are willing to play), window scale, the Modules that switch each tab on and off, quick access, general options, chat and mentions. Loot has the loot system and the master looter's rules. Raid has the attendance penalties. Officer has the officer ranks and maintenance. About has diagnostics, backup and the links.
Who sees it: Everyone, and it cannot be turned off. Loot and Officer are officer-only; in Raid, a member sees the penalties but cannot change them.
Where to find it: In the window (J or /gos), the last tab. It is also in the minimap button menu (right-click).

How it should behave

The categories are General, Loot, Raid, Officer and About. Loot and Officer only show for officers.
In Modules, everything comes on. Now, Roster and Settings have no checkbox: they cannot be turned off.
Unticking a tab removes it from the window right away. Unticking a background piece, such as the Raid Tracker, only takes effect after reloading the interface, and the addon warns you.
UI Scale goes from 80% to 120%, in steps of 5.
Guild info in item tooltips has three modes: always (the default), only when holding Shift, or off.
Guild button opens Guild OS comes on: J and the guild button open Guild OS when you are in a guild. Turned off, they open Blizzard's window, and Guild OS stays on the minimap button.
In Officer › Officer Ranks, ticking a rank ticks all above it, and the Guild Master is always an officer. Only an officer changes it, and the change applies to the whole guild.

This is not a bug

The loot system chosen in Settings › Loot applies only to your game: each officer picks their own, and a member stays on /roll.
Turning off a tab does not turn off what it does behind the scenes: without the Raids tab, raids keep being logged.
Changed the UI Style and nothing changed? It only applies after reloading the interface.
Guild OS's own shortcut in Key Bindings comes with no key: what opens the window by default is J, through the guild button.

Link to this feature Report on Discord

On the site

What it does: Every sign-in button on the site leads to this page. You sign in with Discord, with no new account and no password, and go back to where you were. It is through Discord that the site knows which guilds you can see.
Who sees it: Anyone. Whoever is already signed in does not even see the page: they go straight to where they were going.
Where to find it: In Sign in, in the corner of the header, or at guildos.me/entrar. It is also where someone goes who tries to reply to a raid through the link without having signed in.

How it should behave

If you have already signed in, the page asks nothing and sends you straight to where you were going.
After signing in, you go back to the page you came from. An address that leads outside the site is never followed: in that case, you land on Your guilds.
If you cancelled on Discord and tried again, you still go back to where you were going, for example to the raid from the link you opened.
Coming from a raid's link, the page says which raid you are going back to, with the day and time in your time zone.
The site asks Discord for your name, your avatar, the servers you are in and your roles in them. Never your email or your messages.

This is not a bug

“Discord did not confirm” appears when the Discord window is closed before authorizing, or when authorization is denied. Nothing was saved: just try again.

Link to this feature Report on Discord

Your guildsmemberThe list of guilds you reach through your Discord servers.

What it does: Shows each guild tied to a Discord server you are in, with how many members and items it has and in which servers it answers. Here you also mark the nights that usually work for you to raid. Whoever manages a server links one more server to a guild of theirs. With no guild at all, the page leads to the wizard or to saying who you play.
Who sees it: Whoever signed in with Discord. Each person sees only the guilds of the servers they are in.
Where to find it: In Your guilds, in the header, or in My guilds, in your account menu. Address: guildos.me/dashboard.

How it should behave

All guilds tied to any Discord server you are in appear, and only them.
The guild carries the “admin” tag when you have Manage Server in one of its servers. On the others, “member”.
“When I can raid” has one row per guild, not per server. It is not a signup: nobody is marked on any raid because of it.
The days you mark show to officers when they schedule a raid, and on the raid page while you have not replied.
Linking a server to a guild takes two things: Manage Server on that server, with the bot in it, and managing the guild.
With no guild at all, whoever manages a server sees the wizard's buttons. Whoever does not manage one sees the path to say who they play.

This is not a bug

Just joined the guild's Discord and it does not show up? The site keeps your server list for about a minute. Reload in a little while.
When Discord does not answer, the list is empty and the page warns that it could not reach it. Signing out and in again usually fixes it.

Link to this feature Report on Discord

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

Your charactermemberWhere you say which character is yours, so signups show the real you.

What it does: You pick your character from the guild roster, accept one the site found for you, or register one by hand. Once linked to the roster, it shows item level and attendance on signups. If you registered before the guild sent the roster, the page says what is missing and lets you tell the officers.
Who sees it: Whoever signed in with Discord. Each person sees and edits only their own characters.
Where to find it: In My characters, in your account menu and in Your guilds; in “Pick my character”, in Start here; and in the registration link from a raid. Address: guildos.me/start/character.

How it should behave

The list to pick from brings whoever in the roster of your guilds has no owner yet and has already been measured by the addon, from highest item level to lowest, up to 12 at a time.
You can only take a character from the roster of a guild tied to a Discord server you are in.
A roster character who already belongs to someone else is not offered to you.
If you came from a link, such as a raid's, the page sends you back there as soon as you have a character.
“Tell the officers” sends the message at most once a week. Deleting and registering the character again does not reset that count.
In WoW: Forever, if you registered only the first name and the roster has the full name, the page asks “The roster has … Is that you?”. Nothing is linked without you saying “That's me”.
Once confirmed in the roster, the character shows the item level, or “no addon” with the button to install.

This is not a bug

Your name is not on the list? It only brings whoever the addon has already measured. Open “None of these are mine, let me type it” and write the name.
The roster list disappears once you have a character. To register an alt, use the form.
“declared” next to the character means no roster has confirmed it yet. When the roster brings the same name, it links by itself if you have already signed up for a raid of the guild; otherwise, the page offers “That's me”.
The “waiting for the guild” box and the “Tell the officers” button only appear for whoever registered through /register on Discord. The site's form does not know which Discord you came from.

Link to this feature Report on Discord

Guild dashboardmemberThe guild's first page: what needs you now, the next night and the latest ones.

What it does: For whoever manages a guild's Discord server, it is the dashboard: the next step at the top, with the why, what comes after, the guild's health and what happened in the last 14 days. For everyone else, it is the guild's page: the join requests waiting, the next night with what is missing by role and the latest recorded nights. When nothing needs you, it says so and does not invent a task.
Who sees it: Whoever shares at least one Discord server with the guild. For anyone else, the page answers that it is not here. The dashboard with the next step is only for whoever has Manage Server on one of the guild's servers.
Where to find it: In dashboard, on the guild bar; by clicking the guild in Your guilds; or at guildos.me/guild/… The Monday summary the bot sends to officers also leads here.

How it should behave

It only opens for whoever is on some Discord server tied to the guild. For anyone else, the page answers that it is not here, whether the guild exists or not.
The next step is always the most urgent: first what blocks the roster (upload refused, companion stopped), then whoever is waiting for an answer, then the wizard, and last what improves the guild.
“The companion stopped” appears after 3 days without an accepted roster, and only if a roster has arrived before.
“Remind me in a week” hides an item for 7 days, only in this browser. Upload refused, companion stopped, join requests and required steps cannot be postponed.
In the next night, the count by role uses only whoever said yes or is arriving late and is in: the waitlist and declined do not count.
Dates and times appear in your time zone, your browser's.
Upload refused, companion stopped and companion out of date appear in a strip at the top of the guild pages, for whoever sets up the guild. On the dashboard, the same warning comes as the next step, and the strip does not repeat.

This is not a bug

A night with bosses and “nobody was measured”: the addon of whoever recorded it noted the bosses, but not the group snapshots. It does not mean nobody was there.
Without having signed in, the page asks you to sign in first, whether the guild exists or not. The site does not say whether a guild is here to someone who has not said who they are.
“Could not confirm with Discord”: who can open the page comes from Discord, and it did not answer. Trying again usually fixes it.
You set up the guild and do not see the dashboard? It is for whoever has Manage Server on a Discord server of the guild. A role with permission on the site is not enough.

Link to this feature Report on Discord

RostermemberEveryone in the guild, and how much of it the addon measures.

What it does: The list of every character the game sent, with level, rank, item level and professions. The top says how many the addon measures and how to reach the rest: the bot calls by DM whoever has Discord linked, and the invite in the channel reaches whoever does not. Each name opens the person's sheet: gear, attendance night by night, what they got in loot, their other characters and how many times they said yes and did not show up.
Who sees it: Whoever shares a Discord server with the guild. Each member's Discord name, the call buttons and the list of unmatched registrations are only for whoever has Manage Server on a guild server.
Where to find it: In roster, on the guild bar. A person's sheet opens by clicking their name here, on a recorded night or on loot.

How it should behave

The roster changes when an officer's companion sends what the game saved. The game only saves when the officer leaves the game or does /reload.
An older upload never overwrites a newer one: with two officers sending, the most recent data for each person wins.
An officer with an out-of-date addon does not erase what a newer addon already sent, such as gear.
Measured means having an item level, and only the addon measures it. “no addon” is whoever no addon has measured yet.
The default order is “needs attention first”: whoever has a warning, then the measured from highest item level to lowest, and last whoever has no addon, in alphabetical order.
“Call by DM” calls each person at most once a week. The row shows “queued” or “called” with the day, in place of the button.
On the sheet, “20+ lockouts” counts only raids of 20 people or more. Two nights in the same raid in the same week are a single chance.

This is not a bug

Empty roster: it appears when the first roster arrives from the game. Whoever manages the server sees the button to turn it on.
“no addon” is not the member's fault. The game tells everyone the name, class, level and rank; item level, gear and professions only exist for whoever has the addon.
“said yes and did not show up” only counts raids that someone recorded with the addon. With no absences, the block does not even appear.
The “officers” filter counts only the guild's two highest ranks in the game. A lower rank does not count, even with “officer” in its name.

Link to this feature Report on Discord

RaidsmemberThe guild's schedule: the scheduled raids and the nights the addon recorded.

What it does: Lists the raids of the guild's Discord servers, with what is missing by role and who is on standby. You can see the upcoming ones, the past ones, the cancelled ones, all of them, or the month on a calendar, and subscribe to the schedule in your phone's calendar. Below are the nights the addon recorded, marked as a raid here or not. Officers approve requests, edit, lock, cancel, open the signup link and manage the fixed weekly raids.
Who sees it: Whoever shares a Discord server with the guild. The buttons and the reading of each signup (item level, attendance, warnings, time without loot) are only for whoever can schedule a raid; the others see who is going and in which role.
Where to find it: In raids, on the guild bar.

How it should behave

The list brings the raids of all Discord servers tied to the guild.
A raid stays in Upcoming until 6 hours after it starts: during the night, it does not vanish from the screen.
Each tab says how many raids it has, so none looks erased.
Each raid's day and time appear in your time zone.
A fixed weekly raid shows the time in the time zone it was created in, with the city name, without converting to yours.
Each signup's item level, attendance, warnings and weeks without loot only appear for whoever can schedule a raid.
In a raid with approval, whoever asked to join stays in “Waiting for an officer” and does not take a spot until accepted.

This is not a bug

On the first visit, the times may change right after the page opens: it starts on the guild's time and redoes itself in your time zone as soon as the browser says which it is.
A recorded night with “no raid scheduled”: the addon recorded it, but nobody marked that night as a raid here. It counts toward attendance all the same.
“outside the guild” on a night: the addon did not count it as a guild raid, because fewer than half the group was from the guild. It does not count toward anyone's attendance.

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

Raid pagememberA whole raid on one screen: who is coming, what is missing, the groups and, afterwards, who showed up.

What it does: Shows the day and time, what is missing by role, the signups (confirmed, waitlisted, waiting for an officer and those not coming) and the buttons to reply with your character. It says how many signups the site does not know can go, because they have no addon, and, after the raid, compares who said they were coming with who the addon saw there. Officers also approve requests, build the groups, tag in the raid's thread whoever has no addon and copy the text that carries the list into the game. With the link open, the raid also has a public address, for people who are not in the guild's Discord.
Who sees it: The guild page: whoever shares a Discord server with the guild. The public address: anyone with the link, while an officer keeps the link open, and to reply you must sign in with Discord. It only shows how many of each role are going, never names. With the link closed, the address answers that the page is not here.
Where to find it: By clicking the raid's title in raids, in the dashboard's next night, or in “See the raid” in Your character. The public address (guildos.me/r/…) is the one the officer copies when opening signup by link.

How it should behave

Spots go in order of reply. “Running late” takes a spot like “I'm in”; “Maybe” and “Can't make it” do not.
After the signup deadline the raid closes: nobody joins or changes their answer, on the site or in Discord. Only Leave, on the site, still works.
When someone leaves, the first on the waitlist for that role moves up.
“Take into the game” takes only the confirmed with a character the roster confirmed. Waitlist, absent and those not in the roster are left out.
Opening signup by link also turns on approval: every request that arrives through the link waits for an officer.
“Tag in the raid's thread” goes out only once per raid, and only before it starts.
Whoever can schedule a raid sees who said, in Your guilds, that day of the week works and has not replied yet.

This is not a bug

The “The night” block does not appear: it only exists when someone's addon recorded the raid. Without a recording, there is no way to say who came.
“no addon · unknown” accuses nobody: item level comes from each person's addon, and without it the site only has the name.
There are no boss assignments or buff coverage: the site does not yet know the bosses and buffs of WoW: Forever raids.

See it working Link to this feature Report on Discord

Recorded nightmemberA night the addon recorded: who was there, what dropped and who said they were coming.

What it does: Shows the duration, the bosses (killed and wipes), who was there and the loot that dropped at that time. If the night is linked to a scheduled raid, it puts side by side how many said yes and how many the addon measured, and names who said yes and did not come and who came without replying. Whoever can schedule a raid links the night to a raid, or unlinks it.
Who sees it: Whoever shares a Discord server with the guild. Linking and unlinking is for whoever can schedule a raid.
Where to find it: In raids, in the list of recorded nights; in the dashboard, in the latest nights; in the attendance squares on a person's sheet; and in the post the bot makes on Discord after the night.

How it should behave

“Agreed vs measured” only appears when the night is linked to a scheduled raid. The number of who said yes stays on screen and is never replaced by the measured one.
The night links itself to a raid of the same instance when it starts between 2 hours before and 8 hours after the scheduled time. Outside that, it stays without a raid.
To link by hand, the list brings the guild's raids from 7 days before to 7 days after the night, except cancelled ones.
Whoever came without replying counts the same as whoever replied.
“Dropped here” gathers loot by instance and by the night's time: the loot does not know which night it came from.
The bot only posts the night on Discord if it is up to 48 hours old, and only in the channels where the pinned raid list is.
The day and times appear in your time zone.

This is not a bug

“nobody was measured” with bosses on the list: the addon recorded the bosses, but not the group snapshots. It does not mean nobody was there.
Whoever said yes without a character confirmed in the roster does not appear in “said yes, did not come”: without a character, there is nobody to compare.
“Nobody marked this night as a raid here” even with a scheduled raid: it did not have the instance chosen from the list, or started outside the window. Choose the raid from the list and link it by hand.

See it working Link to this feature Report on Discord

LootmemberWhere the loot went, and who keeps raiding and gets nothing.

What it does: At the top, whoever shows up most on the nights and for 8 weeks or more gets nothing, or never has. Below, the latest handouts, from newest to oldest: who got it, the item, the raid and the day. Each name opens the person's sheet.
Who sees it: Whoever shares a Discord server with the guild.
Where to find it: In loot, on the guild bar.

How it should behave

The list shows the latest 200 handouts, from newest to oldest.
“Who shows up most and gets nothing” considers only whoever the addon measured and is at the level cap.
It includes whoever was on any recorded night and has gotten nothing for 8 weeks or more, or never has. Whoever was there most comes first.
When nobody is in that situation, the block does not appear.
Loot arrives from the game together with the roster. Sending the same upload again does not duplicate any item.
Dates appear in your time zone.

This is not a bug

Someone still leveling, or a bank character, does not appear among those who get nothing: the block is for people who raid.
Whoever has never gotten anything but has also never appeared on a recorded night is not on the list: they are not waiting for anything.
“No items recorded yet” until the first loot arrives from the game.

Link to this feature Report on Discord

CraftersmemberWho in the guild makes what, by recipe and by profession.

What it does: Search for a recipe by name and see who in the guild knows how to make it. Below, a section per profession that someone has: how many crafters, how many of the game's recipes the guild covers, and each crafter with level, specialization and how many recipes they know. The professions nobody has go in a line at the end.
Who sees it: Whoever shares a Discord server with the guild.
Where to find it: In crafters, on the guild bar.

How it should behave

The search needs at least 2 letters and looks in the recipe's name in the language you read: Portuguese for Portuguese readers, English for every other language.
The search shows up to 50 recipes. If there are more, the page says how many and asks for more of the name.
In each profession, whoever has the addon comes first, from highest level to lowest. Whoever does not comes last.
Whoever does not have the addon appears with the profession the game's roster reports, as “no addon”, with no level and no recipes.
“N of M recipes” counts the game's recipes for that profession that at least one person in the guild knows.
The professions nobody in the guild has appear in a single line, at the end.

This is not a bug

Empty page: the professions appear when someone in the guild publishes with the updated addon.
A crafter without the addon never shows up in the recipe search: the site only knows the recipes of whoever has the addon.

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

Guild pagememberThe page the guild sends to whoever asks: who they are, when they play and what the game said about them.

What it does: Opens with the name, where the guild lives, how many are in the roster, the guild's tagline and the button to its Discord. Shows a few randomly picked characters, the schedule, the average item level and attendance, the pace of the last eight weeks, what the guild is looking for, how loot works, the upcoming raids and the whole roster. Each name opens the character's page, with gear and what the addon published about them. What came from the game and what the guild wrote appear with different marks.
Who sees it: Anyone, without signing in. Whoever manages a guild server also sees a strip, for officers only, with what makes the page weaker. Character pages exist while public pages are switched on in the configuration.
Where to find it: In page, on the guild bar; in the public guilds list; or at guildos.me/g/… A character's page is at guildos.me/c/…

How it should behave

With public pages switched off, each character's page answers that it is not here, and the guild page does not pick anyone.
The characters at the top are up to 4, drawn again on each visit among whoever the addon measured. Nobody chooses who appears.
The team's numbers count whoever the addon measured and is at the level cap. While nobody has reached the cap, all the measured count.
The times of upcoming raids appear in the reader's time zone.
The top says how long ago the roster was published.
Without the guild's tagline, a visitor does not see an empty space. Only whoever manages sees the place to write.

This is not a bug

Progression by raid does not show: the site does not yet know how many bosses WoW: Forever raids have.
Nobody at the top of the page: the addon has not measured anyone yet, or public pages are switched off.
A character with initials in place of the portrait: the site does not know their look yet. They appear anyway.

Link to this feature Report on Discord

Public guildsmemberThe list of guilds on GuildOS, each with what the game said about it.

What it does: One row per guild, in alphabetical order: the Discord crest, the name, where it lives and what the game said, such as how far it got in the raid, the average item level and how many raiders. Clicking opens the guild's public page.
Who sees it: Anyone, without signing in.
Where to find it: In public guilds, in the site footer; in “see all guilds”, on the home page; or at guildos.me/guilds.

How it should behave

All GuildOS guilds are included, in alphabetical order.
Only what the guild has already published appears: a guild without a roster does not show item level 0 or 0 bosses.
Raiders and average item level count whoever the addon measured and is at the level cap, or all the measured while nobody has reached it.
Clicking a guild opens its page in the language you are reading in.

This is not a bug

Your guild appears here even with public pages switched off: that switch applies to each character's pages.
A guild with only a name, without numbers: it has not published anything from the game yet.

Link to this feature Report on Discord

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.