Bot guide

Everything GuildOS does in your Discord, command by command. Almost all of them open a form: you call the command and fill it in right there.

Add the bot to my server A question the guide does not answer? Ask in the support server.

Getting started

Add the bot to your server with the button above, accepting the permissions it asks for.
Create the guild on the site, at guildos.me/start/raid: pick the server and name the guild. Without it, /register has no roster to look in.
Use /register CharacterName to link your Discord account to your character.
Use /raid create to open the signup for your next raid.
If your guild will use the federated guild — Council, cores, applications — open /council config and follow the panel: channels, roles, Council seats, and switch it on.

For everybody

What anybody in the server uses.

/registerwho uses it: anybody: Links your Discord account to your character and hands out the roles the guild configured. Suggests the roster's names as you type; on Forever, use the name with its surname.
/profilewho uses it: anybody: What the guild knows about you: attendance, your word, the next raid and your characters.
/applywho uses it: anybody not in the guild yet: The application form: character, class, spec, hours and what you are after. The Council answers by DM.
/poolwho uses it: anybody: Who is in no core, with a button to filter by class, spec, role and night.
/availabilitywho uses it: recruits and members: The nights you can raid, the hours and what you are after. It is what people building a core see.
/core infowho uses it: anybody: A core's details and who is in it.
/core applywho uses it: members: Asks to join a core. The same as the Ask to join button on the core's post.
/appealwho uses it: whoever was expelled: Asks the Council, once, to reconsider the expulsion. It works in the bot's DM.

Cores

A core is a small guild inside the guild, with its own Raid Leader, hours and loot. Calling one makes its role, its category and its channels straight away.

/core createwho uses it: members: Calls a new core: name, size and style, hours, loot and which channels it gets. The call goes to the forum of cores.
/core editwho uses it: the core's Raid Leader: Changes hours, style, loot and rules. Deleting the rules text takes the rules away.
/core cancelwho uses it: whoever called it, or the Council: Calls off a core that has not formed. The role and channels it made are deleted.
/core invitewho uses it: the Raid Leader and officers; whoever called it, while the core calls: Invites somebody into the core. They accept or turn it down by DM; while the core calls, accepting is answering the call.
/core removewho uses it: the core's Raid Leader: Takes somebody out of the core, with a reason only the leadership sees.
/core promotewho uses it: the core's Raid Leader: Changes somebody's role in the core: raider, reserve or officer.
/core handoverwho uses it: the core's Raid Leader: Hands the core over to somebody else. They accept, and the Council validates it.
/core interimwho uses it: somebody in a core nobody leads: Names an interim for the core. The Council validates it.
/core log-raidwho uses it: the Raid Leader and officers: Records that the core raided. With the addon using the core's groupTag, that counts on its own.
/core leavewho uses it: whoever is in the core: Leaves the core. The Raid Leader leaves only by handing it over first.
/core closewho uses it: the core's Raid Leader: Closes the core. Its channels go to the archive and whoever is left with no core goes first in the pool.
/core mergewho uses it: a Raid Leader of either core: Merges one core into another. The other Raid Leader accepts.

The Council

The Council looks after the configuration, the front door, conduct and the blacklist. The seat decides, not the Discord role.

/council configwho uses it: the Council, the GM and whoever has Manage Server: The federation's panel: channels, roles, deadlines, names and rules, seats, and switching it on or off.
/council intervenewho uses it: the Council: The only door through which the Council touches a core, and only with an open case about it: remove the Raid Leader, remove somebody, or close the core.
/council blacklist addwho uses it: the Council: Adds an account or characters to the blacklist. Applications matching it are marked and cannot be approved.
/council blacklist removewho uses it: the Council: Takes somebody's entries off the blacklist, with a reason.
/council blacklist listwho uses it: the Council: The blacklist's active entries.
/case openwho uses it: the Council, and a core's leadership about somebody in it: Writes down a problem with somebody. Level 1 is on record; levels 2 and 3 go to a Council vote.
/case closewho uses it: the Raid Leader of the case's core, else the Council: Closes a level 1 case, saying what was done. With no core, nobody leading it, or a case about the Raid Leader themselves, the Council is who closes it.
/case involvewho uses it: councillors (about themselves) and the GM: Marks a councillor as involved: they do not vote on that case.

Raids

Raid signups work with or without the federated guild switched on.

/raid createwho uses it: whoever may create raids: Opens the signup: title, when, instance and size. The post carries the signup buttons.
/raid lockwho uses it: whoever may create raids: Closes the raid's signups.
/raid cancelwho uses it: whoever may create raids: Cancels the raid and tells whoever had signed up.

Forms and buttons

Commands that ask for more than one thing open a Discord form, already holding the current values where there are any.
The messages the bot posts carry buttons: confirming a core's call, approving an application, asking to join a core, voting on a case.
Every click is checked again by the site. A button showing is not permission: whoever may not do it hears why.

How to set the bot up, step by step