Operations, training blocks, and selection cycles. Click any event for the full brief. Check the Discord for last-minute changes.
RRC members: your Discord name and PIN. See who is attending and mark yourself.
RRC cadre: the cadre password. Add, edit and remove events, and see who is attending.
Allied units: the same access code as the Allied Portal. See who is attending.
The Allied Portal access code. It shows who from RRC is attending each event, by unit name. It does not let you mark attendance.
Your Discord name and PIN, issued by cadre. This is what marks you accepted, tentative or declined on an event — it is not the cadre password. Forgotten it? Ask cadre to reset it.
Adding events uses the cadre password — the same one that opens the Cadre Portal. Signed in as a member whose account has cadre access? Cadre login opens this on your own account, no password needed.
Set Runs until for an event over several days — a Red Phase stand-down over the holidays, a selection weekend. Leave it empty for a one-day event.
Signed-in members see these buttons on the event and can mark themselves. Untick the whole thing for an event nobody signs up to, or drop Tentative for one where you want a straight yes or no.
Insert a blank row directly under the header, click cell A2, and paste.
Publishing and deleting run through one Apps Script deployment, shared by news, events and the allied portal. Use AppsScript_v8.gs from the site package — the snippet below is an older cut-down copy, kept here as a fallback.
SCHEDULE_WEBHOOK script property to have a single Discord message mirror the schedule and rewrite itself on every change. The steps are in the comment at the top of the script.The current script ships with the site package as AppsScript_v12.gs. Paste that whole file in — it is kept up to date, where a copy printed on this page would not be.