TiaraBot operating guide
What TiaraBot handles for fillers and mana/moni during Project Sekai tiering.
TiaraBot connects an event server’s schedule sheet to Discord. It exposes individual fill schedules, open slots, check-ins, schedule screenshots, room order, saved fill-team information, and service readiness.
It does not choose a runner’s team, spend energy or crystals, play Envy/LnF/Melt/HCM, join a private co-op room, assign an open slot, or write your server’s emergency ping.
Pick your role
Filler / support
Your schedule, team, check-in, room access, and problems.
Mana / moni
Setup, schedule posts, check-ins, room order, slots, and bot health.
Quick command reference
Exact command paths, inputs, output, and boundaries.
Command permissions and parameters
Caller access, required inputs, optional inputs, defaults, and Discord prerequisites.
Check-in timing and procedure
TiaraBot provides the same check-in procedure whether the check-in is automatic or manually triggered. With auto check-in enabled, TiaraBot schedules the check-in timing. A server that keeps its own timing can have mana/moni run /checkin manual instead.
Other procedures can vary. Servers may send schedule-sign-up/open-slot pings earlier or later. Some use standby well before a slot and escalate to emergency. Others go directly to emergency. TiaraBot supplies schedule and slot data for either approach without choosing the server’s escalation policy.
Team submission availability
Unstable, server-gated feature
Team submission requires a configured submission channel and TiaraBot's service-controlled feature flag for that server. A configured channel without the flag is disabled: the bot does not write, react, reply, or create a submission record. If either requirement is missing, use the server's established manual process. The rest of TiaraBot remains usable.