WoW: ForeverGuildOS will be in the WoW: Forever beta and at launchlaunch inWoW: Forever launches on November 4, 2026.

← Manual

In Discordmember

Cores

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

Report on Discord

Found a mistake in the translation? Let us know on Discord.

Created with by FerionPrivacidadeTermosSuporteApoie ☕