THE CALENDAR GETS A CONTROL ROOM
Saber is initialized as the control channel and Snow immediately starts building recurring event infrastructure. UL has decided remembering Tuesday is now a software problem.
five years of people arguing with the calendar
Commands fail. Humans remember. Recurring events continue.
Snow opens the room with "!init" at 08:06. By 08:56 he has entered **Spank Mugs Booty** as a weekly Saturday event. At 14:33 Sye is configuring the new schedule into Announcements; forty minutes later she tells Gilli "Hi gili just helping snow out". Then come timezone checks, "Nvm I did it", "Iβm look at github", Snow's "awesome thanks Syen", and Mugs' "Thank you guys!". The next morning: "IT WORKSSS". This is not an Officer-appointment receipt. It is Sye doing technical work on the bot's deployment day, more than a year before her October 2021 full-Officer promotion.
November 2020: Sye changes the timezone and discovers the timezone change also changed the event time. January 2021: she proposes a second seasonal schedule instead of re-editing everything twice a year. March 2022: she leaves a full spring/summer versus fall/winter command sheet with the event IDs and times. November 2022: another note to convert DST to EST. March 2023: "Forgot time change". Gabu answers from Brazil that they do not do that there anymore. This server had an international technical department and its recurring enemy was the clock.
Gabu says she is testing Carl because she is thinking of replacing Saber, then recreates a whole week before touching production. Her January 22 note is the important part: Carl is using **her local timezone**, the interface does not clearly identify who created or modified a record, and there are about thirty records. Her proposed fix is boring and correct: one person owns the configuration; since she built it, she can be responsible for the announcements. The attached Carl-bot screen literally says "Uses your local time zone". Mugs says "Thank you gabu!". Sye says "Ty Gabu". Three days later Gabu files the final benchmark: "Saber is faster bro".
Human messages in "saber_control" during 2024: **0**. Bot messages: **1,831**. Demolition, Yakuza Peak, Club Clash and the rest keep firing into an otherwise human-silent control room. This does not mean UL itself had no humans left in 2024. It means this particular machine room could keep performing activity after the people stopped needing to discuss the machine in public.
Sye tries "/kill saber" on July 30. On August 4 she comes back with "Think itβs time to kill this bot", later admits "i forgot how to uses this bot xD", and finds the right command. At 19:49 Saber says **"That schedule has been removed"** and **"Completed execution of delete command."** Sixty-nine seconds later Sye notices the loose end: "snowden has the other schedule ;O". Saber gets an ending. The replacement calendar does not obligingly die in the same scene.
Saber is initialized as the control channel and Snow immediately starts building recurring event infrastructure. UL has decided remembering Tuesday is now a software problem.
Sye edits the same Spank Mugs Booty event id created by Snow in 2020. The joke is not merely remembered; the same scheduled object is still being maintained.
Carl-bot / Snowden emits Spank Mugs Booty during migration-era testing. The software changes; the house language gets ported.
Saber keeps emitting test reminders after the Carl migration work, so the surviving record does not support one neat cutover date. The old bot remains in the building.
On September 22, 2020, Saber confirmed #saber_control as its control channel, created a schedule channel, and stated that schedules could be synced to Google Calendar; Snow immediately began creating and editing recurring events.
On September 22, 2020, Snow issued the command `!create #deleted-channel βSpank Mugs Bootyβ 20:50 repeat saturday`; Saber accepted `Spank Mugs Booty` as the event title and created it as a weekly Saturday schedule item, after which Snow edited its date and start time.
On November 24, 2020, Sye told Gabu to 'change the date'; Gabu replied 'omg how.'
On January 21, 2021, Snow said he no longer recalled how to fix the bot, asked Gabu if she wanted to try, and Gabu replied that she could fix it one by one.
The 2021 Saber-control transcript shows Gabu repeatedly editing event dates, event configuration, and announcement routing; on September 28 she corrected her own `starte-date` typo after Saber rejected it.
On April 5, 2022, Gabu asked Sye to add an event-time edit; on March 12, 2022 Sye directly edited event id m1k2w9, which Saber identified as the weekly `Spank Mugs Booty` event.
By March 2021, Saber was publicly announcing `Spank Mugs Booty` to Staff in Announcements; on November 20, 2021 Nelph followed the automated reminder with `COME TO CLUB BASE TO SPANK SOME DRAGONS BOOTY` for Dragon Breath.
In April 2023, Gabu maintained a pinned seven-day alert checklist and wrote that if the checks worked she would try to replace Saber with Carl; Carl-bot / Snowden emitted test alerts in the same control room.
Carl-bot / Snowden emitted `Spank Mugs Booty` during 2023 migration/test traffic, while Saber continued emitting the same title in later test reminders through at least 2024; Snowden continued emitting the title in 2025.
On July 30, 2025, Sye posted `/kill saber`. On August 4, she wrote `i forgot how to uses this bot xD` and later `snowden has the other schedule ;O`.
The retrieved receipts place `Spank Mugs Booty` inside the same operational culture as Dragon Breath reminders, but no retrieved command explicitly states `Spank Mugs Booty = Dragon Breath`; the site therefore does not publish a one-to-one mapping as archive fact.
Preserves the difference between recurring name adjacency/house vocabulary and an explicit event-name mapping.
The precise post-2023 division of schedule responsibilities between Saber and Carl-bot / Snowden is not fully reconstructable from the surviving control-room export alone.