how it works

One signup, three places

Follow one raid week through one person's signup. It leaves Discord, reaches the site with what the game measured, and becomes an invite inside the game. Nobody types anything twice. The names are made up.

Step 1 of 7

Discord

An officer books the raid

On the site, under Schedule a raid, or with /raid create in Discord. The bot posts the raid in the guild's channel: when, where, slots by role and who is already going.

Why: The guild sees the raid where it already talks. The time shows on each reader's own clock, no time zone maths.

Discord

# raids

GuildOS APP Today at 7:12 PM

Hyjal Summit

📅 WhenThursday, 8:00 PMin 2 days

📍 WhereHyjal Summit

👥 Roster7/20▰▰▰▰▱▱▱▱▱▱

🛡 2/2 · ➕ 1/5 · ⚔ 1 · 🏹 3 · 4/13 DPS

Warrior (1)• Dorrgan HollowhandTank

Paladin (1)• Brumhold StonehelmTank

Priest (1)• Elarion BrightwellHealer

Mage (1)• Ilyndra FlameheartRanged

Druid (1)• Feyclaw ThornpawMelee

Hunter (1)• Kestrin SwiftarrowRanged

Warlock (1)• Morgrave BlackmoorRanged

1 signup without the addon: the item level shows on the guild's site once installed.

Ember Vigil — Normal · GuildOS

✅ Sign up⏱ Late❓ Tentative❌ Absent🚪 Leave

Install the addon ↗

guildos.me

← Raids

Thursday · 20:00

Hyjal Summit

open 20 people

Signed up · Confirmed 7

Dorrgan Hollowhandcan goTank WarrioriLvl 63 · 100%

Brumhold Stonehelmcan goTank PaladiniLvl 63 · 90%

Elarion Brightwellcan goHealer PriestiLvl 61 · 80%

Ilyndra Flameheartcan goRanged MageiLvl 62 · 100%

Feyclaw Thornpawcan goMelee DruidiLvl 61 · 70%

Kestrin Swiftarrowno addonRanged Hunter

Morgrave Blackmoorcan goRanged WarlockiLvl 63 · 90%

in the game

GuildOS Ember Vigil

NowRosterRaidsLootDKPWishlistProfessionsGuildAllianceRecruitmentTrialsLeadershipWebSettings

PLANNED RAID

Nothing loaded.

The week's seven steps:

An officer books the raid. On the site, under Schedule a raid, or with /raid create in Discord. The bot posts the raid in the guild's channel: when, where, slots by role and who is already going. The guild sees the raid where it already talks. The time shows on each reader's own clock, no time zone maths.

Ashwind signs up from their phone. Ashwind has no account on the site and does not need one. The character is the one the game already knows. That is how the site will know its item level without anybody typing it.

The signup reaches the site with what the game measured. On the raid's page, Ashwind shows up with their spec, item level and attendance over the last nights. Nobody typed those numbers: the addon measured them in the game. Whoever has no addon shows as "no addon". The officer knows at once who the site knows nothing about.

The officer builds the groups. Whoever confirmed goes into the groups. Drag them one by one, or let the site arrange them. Only those who confirmed and whose character the game recognises go into the invite. The waitlist stays out.

The roster is already inside the game. The companion brought the site's roster to the addon. With publishing on, it shows up on the Web tab when you log in or /reload. Invite skips whoever is already in the group, but it does not turn the group into a raid: convert it first if there are more than five. Groups needs you as the raid's leader or an assistant.

The night happens, and the addon takes notes. The addon takes a snapshot of the raid group every 5 minutes and notes the bosses and the wipes. Attendance is who was there, not who clicked Sign up. Each raid lockout is worth 100 points, even when the guild goes on two nights. Arrive after the first snapshot or leave before the last and you lose 10. When somebody logs out or /reloads, the companion takes the night to the site.

The site shows who said they would come, and who came. On the night's page, what was agreed in Discord sits next to what the addon measured, name by name. That is the difference no signup-only tool can see. It becomes history: each person's page shows how often they said yes and came.

Found a mistake in the translation? Tell us on Discord.