In the gameofficer

Raids › Cores

The 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.

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.

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.