Guild League

Creating a GL night

A Guild League night is a special event type. When creating a GL night, you configure:

• •Date and time slots: GL nights usually have 2-3 time slots (e.g., 9 PM, 10:30 PM, 12 AM). Set each slot's start time and duration.
• •Sub-guild: Which sub-guild is participating (main guild or alt guild).
• •Expected opponent: The guild you're facing (optional, or auto-detected from warscore).
• •Season: Assign to a season for long-term tracking.

Signup flow

CoGM posts a GL signup embed to Discord. The embed has individual buttons for each time slot (Slot 0, Slot 1, etc.) plus two bulk signup buttons for convenience:

• •Slot buttons: Sign up for a specific time slot only. Use these when you can only attend part of the night.
• •Pre-War: Bulk signup for all time slots. Use this when attending the full night.
• •Post-War: Bulk signup for later slots. Use this when joining after the early engagements.

Members can also click "Absent" or "Tentative" to update their status at any time.

Match submission and warscore

After each time slot finishes, upload a warscore screenshot showing final scores and opponent name. CoGM uses OCR and image analysis to auto-detect:

• •Your guild's total score.
• •Opponent guild's total score.
• •Opponent guild name (updates expected opponent if not set).

Upload via the web dashboard or the Discord bot command /gleague submit. CoGM records the match instantly.

Leaderboards and player stats

After submitting combat logs for a GL night, CoGM generates per-player leaderboards similar to PvP analytics:

• •Most Kills: Top killers in the night.
• •Best K/D: Highest kill-death ratio.
• •Best Performance: Contribution relative to guild average.
• •Win Rate: % of GL nights (time slots) your guild won.
• •MVP Count: Number of MVPs earned by each player across the season.

Seasonal tracking

Group GL nights into seasons. A season might be one month, one quarter, or one reset cycle. Within a season, CoGM tracks:

• •Total wins, losses, draws across all nights in the season.
• •Season leaderboards by player K/D, kills, and participation rate.
• •Head-to-head records vs. each opponent (win/loss history).
• •Class breakdown and comp trends across the season.

Opponent tracking

CoGM maintains an opponent database. For each opponent guild, view your head-to-head record:

• •Overall win-loss record.
• •Recent matches (last 10 engagements).
• •Average score differential (your score minus opponent score).
• •Comp analysis of that opponent (classes they typically run).

The three teams

Pick All three teams when creating a night and CoGM builds Guardian, Defense I and Defense II for that date. Each is a separate roster with its own signup embed, so they can post to different channels and ping different roles.

• •Guardian is ranked. It is the queue that moves your guild's standing.
• •Defense I and II are unranked.
• •A full slot benches you on the team you picked, and you are told why. Nobody is ever moved between teams automatically; only an officer moves people, deliberately.

Team rosters

A roster is who belongs to a team for the season, separate from who can play a particular night. Anyone can register; officers decide who is selected, either by letting the roster fill against its requirements or by picking every name.

• •Each of the three teams has its own roster, set from Rosters under Guild League. Give a roster a channel and it posts a registration message that stays updated all season.
• •Nobody already on a roster is displaced by a later registration. Someone past the limit waits instead, however well geared they are.
• •A night can be restricted to its team's selected roster. That is per night and off by default, so you can run a gated night and an open night for the same team. A gated night pings the roster by name instead of the role.
• •Guardian can also hold a number of seats that only its selected roster may take. Everyone else fills the remaining seats and waits on the slot's bench once those are gone.
• •How many seats are held is set per night, because the right number changes with who is around. 0 makes Guardian first-come.
• •Seats are reserved, never re-assigned. Nobody already signed up is moved when a roster member arrives late.

Rules and class composition

Each night carries the terms people agree to by taking a slot, shown at the top of the signup embed. Set them when creating the night or edit them any time from the night page.

• •Rules: free text, such as a gear floor or a voice requirement.
• •Max per class benches the extras. A third Shai lands on the slot's bench once the cap is two, ready to be pulled in when a seated Shai drops.
• •Min per class turns nobody away. There is no one to reject when a team lacks a Shai, so it shows on the embed as what a slot still needs before queuing.

Regional schedules

Time slots default to your guild's region. NA uses its live eleven-slot window including the two-hour mid-window break. SA runs 20:00 to 04:00 UTC on weekdays and 16:00 to 04:00 UTC at weekends, and the form switches between them when you pick the date. Regions without a configured schedule keep the previous behaviour, where you choose the slots yourself.

Recurring GL nights

Set up a GL night to recur weekly. CoGM automatically creates next week's GL night when the current one archives. It carries over:

• •Time slots (same times next week).
• •Sub-guild assignment.
• •Season assignment (continues in the same season).
• •Rules, class minimums and maximums, and reserved seats.

A new Discord embed is posted to the signup channel, and members can sign up again for next week.

GL analytics dashboard

The Guild League analytics dashboard shows season-level insights: win rate trend over time, average score differential vs. each opponent, player K/D trends, class composition trends, and peak performance times (which time slot your guild performs best in).

Use these insights to refine strategy, identify strong players for main slots, and prepare specific compositions for known opponents.