From a single "Create event" button that opens a menu of everything — combat groups and casual activities alike, in one place.

Combat groups sign up by role (DPS, Healer, Tank) and build, with per-build capacity caps the organizer sets when creating the event. Four presets are built in — Sword Trial, Hero's Realm, Guild War, Skyward Bond — or a fully custom combat group with its own name and caps. Guild War is the exception, and has a section of its own below.

Two presets ask a follow-up. Hero’s Realm and Sword Trial each offer a sub-type — plain, Guild, or Challenge Mode — and Skyward Bond asks for a difficulty (Normal, Hard, Abyss) and then a floor from 1 to 10. That last one is two steps rather than one because a Discord menu carries a single flat list, and difficulty and floor are independent choices.

Signing up runs two checks in order. The build cap first, if the organiser set one for that build; then the event’s total capacity. Tentative signups count toward neither, and switching your build or role replaces your signup rather than adding a second one.

Other Activities are simpler: just Attending or Tentative, no roles or builds. Five types cover the casual side — Other Games, Movie, Exploration, Oddities & Treasure, Meeting — and Other Games and Movie support matching a real title via Steam or IMDb, so the event card shows real artwork instead of a placeholder.

Persistent Teams is its own kind, for a season-long roster rather than a single night — a start and end date instead of just one, and Attending or Tentative like a casual activity, but still asking for a build like a combat group does, since the point is knowing who's committed and what they're bringing for the whole season.

A date is optional when creating an event — leaving it blank triggers the same suggest-a-time flow whether it's a combat group, a casual activity, or Persistent Teams. Everyone who signs up gets a direct, private nudge to suggest a time if the event still needs one, and the organizer can leave rough guidance ("Saturday evening, 6-10PM ET") for members deciding what to suggest. The organizer closes suggestions, and Discord's native poll resolves it once everyone's voted — with an automatic tiebreak flow if it's close. Reminders go out on their own, one hour before and again at the exact start time.

Guild War is its own kind. The preset looks the same from the create menu, but what it makes is different: a war event, and an assignment board in the war room on the website, linked to each other from the moment either exists. Signing up asks for a role and a build as usual — and because a build is a path and a path is exactly two martial arts, picking one records both arts you are bringing. Anybody running a pair from two different paths picks the arts one at a time instead.

A war asks for no build caps, because it could not keep them: a cap is checked against the build you pick, and anybody choosing a cross-path pair by hand walks past it. It reports what the line-up is missing instead — two more Menders, somebody on your bottom lane, a commander — worked out from the war functions of the arts people are actually bringing.

The war thread is the assignment board seen from Discord, not a copy of it. It groups people by duty — commander, the halftime duellist, each of the three lanes at both ends, both jungles — and an unfilled duty takes a line whether or not anybody took it, so a gap is visible on Thursday rather than at 20:00 on Saturday. Assign somebody on the website and the thread re-renders; sign up in Discord and the board fills.

A war also gets a reminder ten minutes before kick-off, on top of the hour-before one every event gets — long enough to finish what you are doing, short enough that you go now. Both mention the people who said yes rather than pinging a role, so they reach the thirty who committed and nobody else.

Deleting an event on Discord deletes it on the website too. There's nothing to separately clean up — and for a war, its board goes with it, unless the match has already been played, in which case the board stays as a record of what was planned.