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.
On the site
Start hereofficerThe wizard that links your guild to GuildOS, from Discord to the first roster.
- What it does
- The door says what you need before sitting down and the four places the path goes through: in the browser (server, bot, guild and the first raid), on Windows (the companion), in the game (the addon sends the first roster) and with the guild (invite, the /register roles and page). You can do it all at once, or only part today: only the raid on Discord, or only the roster from the game. Each step says what to do and follows live what happens outside the page.
- Who sees it
- The door is public: anyone reads it before authorizing anything. The steps ask you to sign in with Discord and only work on a server where you have Manage Server. Whoever manages no server goes straight to picking their character.
- Where to find it
- In Start here, in the header, or at guildos.me/start. While something is missing, the Set up badge in the header and the “guild N of M” ring on the guild bar also lead here.
How it should behave
- Nothing is stored to know whether a step is done: the wizard looks at what already exists. Closed the tab midway? When you come back, it continues from the right step.
- The chosen server only counts if you have Manage Server on it. Someone else's server is ignored.
- The companion step is only done when the companion has talked to the site, or when a roster has arrived. Creating the code is not enough.
- “Call the guild” is done when at least half the roster has the addon.
- In the full suite, the first raid, the invite, the roles and the page are optional and can be skipped. A step that depends on another not yet done does not open.
- While it waits for something from outside, the page refreshes itself: every 5 seconds waiting for the bot, 15 waiting for the first raid, 30 waiting for the companion and the roster.
- “Send to my PC” sends you at most one message per minute.
This is not a bug
- Clicked Start here and landed on Your character? You do not manage any Discord server, and for someone who only plays, saying who their character is is everything.
- “The companion has not shown up yet” after 3 days with the code created: no companion has talked to the site with that code. It is almost always the Windows warning or the code not pasted.
- Played and the roster did not arrive? The game only saves the roster when you do /reload or leave the game, and only after /gos web on.
- “The guild name did not match”: the name on the site has to be the game's. Capitals and the < > signs do not count; accents and spaces do. “Use the game's name” fixes it with one click.
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.
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.
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.
Saw something different from what is written here? Then it is a bug, and we want to know.