RSVP events

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. Five presets are built in — Sword Trial, Hero's Realm, Guild War, Skyward Bond, Talent Run — or a fully custom combat group with its own name and caps. Create one with the Create event button, or by command from any channel: /hr, /st, /gvg, /sb and /talentrun start that kind, and /event opens the whole menu. An event's post has the three role buttons, Maybe and Can't make it; picking a role opens the build list with the build you used last time at the top. The organiser's tools — Announce, Edit, Add member, Delete — sit behind ⚙, and each member only sees the ones they can use. Guild War is the exception, and has a section of its own below.

Some presets ask a follow-up. Hero’s Realm and Sword Trial each offer a sub-type — plain, Guild, or Challenge Mode — then the pair of bosses you’ll fight in a row, which fills in the requirements and adds a card for each boss with three skills to watch for. Talent Run picks one boss and the talent challenges you’re going for: the post shows how many of those signed up still need each, from their Boss Talents trackers, and We got it ticks them for everyone who was there. And Skyward Bond asks for a difficulty (Normal, Hard, Abyss) and then a floor from 1 to 10, and its post shows that floor’s two bosses the same way. 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. Maybe signups (your role and build in one form) 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 Maybe, 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 Maybe 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 — leave it blank and the members decide, in one step. Everyone signed up taps Pick times that work and ticks every time they can make, and anyone can Add a time that's missing. The bot locks in the time most people can make: as soon as everyone signed up has answered, or at the deadline (48 hours, or a day before the earliest time), with a reminder to whoever hasn't answered 12 hours before. A tie goes to the earlier time, and the organizer can Lock it in whenever they like. Everyone sees the times in their own time zone, and types them in it too — each member picks theirs once, or with /timezone. Reminders go out on their own — one hour before and at the start unless the organizer picks others under ⚙ → Edit → Reminders (a day, 3 hours, an hour, 30 or 10 minutes before, and at the start, in any mix, or none). When an event is made, its organizer picks the roles its invite pings; Announce (under ⚙) pings them again, and anyone can announce an event once an hour.

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 squad — five a side, named Seal, Clover, Quatrefoil, Star and Plum, with a badge each and a crown on whoever is leading it — beside the commander, the halftime duellist, and two columns of towers showing which ends are held and which are not. Anunfilled 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 is the one event that must have a kick-off time. Everything else can be left undated and voted on; a war cannot, because the time is what the reminders fire against and what the announcement tells thirty people. A board opened on the website asks for it in the same breath as the match type, and refuses without it rather than filing a war nobody can be reminded about.

A war also gets a reminder ten minutes before kick-off by default, on top of the hour-before one every event starts with — 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.

During the match, the thread keeps the clock. Starting the match clock on the website posts a Match clock message in the war thread that counts itself down: every objective still to come — the Outposts, the camps, Zhang Bao, the halftime duel, Zhuxie Gule — with the squads on it, or a gap where nobody is. Pause or sync the clock on the website and the message follows. A minute before each one, the members of the squads on it are pinged.

Mark what falls, and the thread keeps the record. Whoever runs the clock marks the match on the war map as it goes — a Bulwark down, a Goose killed, a camp or an Outpost taken, where a boss spawned, who won the duel. When the match ends, a Match log is posted in the thread with everything that was marked and when, in time left as the game shows it; a mark made afterwards updates it. It says only what was marked, and says so.

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.

Members see every list with /movies — privately — and pick one to see its movies; the ones already watched at a movie night are struck through.

Give the lists a home with /setmoviesforum: a thread in a forum channel with a message for each list, edited in place whenever a list or movie changes.