Scheduling System

Announcements

The announcement system is used for all content schedulable through Prima. It's also integrated with Google Calendar, so you can view upcoming events in your calendar application of choice.

Understanding announcements

Announcements have the following elements, in this order:

• The message ID of the message used to schedule the event

• The host of the event

• The event time, shown in your system's time zone

• The event description, which may be cut off if it's too long

• A link to copy the event to your calendar, if you don't already have the whole calendar saved

• A link to the event message

• The message ID of the message used to schedule the event (again)

• The event time (again), shown in your system's time zone

• A button you can press to get a notification half an hour before the event starts

Each announcement channel has its events sorted: the soonest event is at the bottom of the channel, and the event furthest in the future is located at the top of the channel.

Announcing events

To announce an event, use ~announce EventDateAndTime | EventDescription in the appropriate scheduling channel for your event type. Currently, EventDateAndTime must use a MM/DD date format. Times are interpreted in Pacific Time by default, but alternative time zones can be specified (see next section).

Event descriptions can span multiple lines - just press Shift+Enter to create a new line without sending the command. This command will create a Discord embed in the corresponding schedule channel, and create an event on the appropriate Google Calendar.

If you would like to schedule an event for the following year, extend the date to include the year, in MM/DD/YYYY format. If you leave off the year, the bot will assume you are scheduling an event in the current year.

30 minutes before your event begins, you and anyone who clicks the notification button on your event's announcement will be DM'd with a reminder that your event is starting soon.

In addition, 30 minutes before your event begins, you will be given the Current Host and Run Pinner roles, which will temporarily give you access to additional event commands. If you are hosting a Delubrum Reginae (Savage) run, you will also be given the Delubrum Roler role. All of these roles will be granted for 4.5 hours. If you begin preparing a channel for your event more than 30 minutes before your event begins, please be aware that these commands will only be unlocked 30 minutes before your event actually begins.

Time zones

Additionally, you can specify a specific time zone that your input should be read in. The following time zones are supported:

Time zone	UTC offset
HST	UTC-10
HT	UTC-10, following Honolulu
AKST	UTC-9
AKDT	UTC-8
AKT	UTC-9 or UTC-8, following Anchorage
PST	UTC-8
PDT	UTC-7
PT (Default)	UTC-8 or UTC-7, following Los Angeles
MST	UTC-7
MDT	UTC-6
MT	UTC-7 or UTC-6, following Denver
CST	UTC-6
CDT	UTC-5
CT	UTC-6 or UTC-5, following Chicago
EST	UTC-5
EDT	UTC-4
ET	UTC-5 or UTC-4, following New York

Additional time zones may be supported on request, assuming their abbreviations do not overlap with an existing supported time zone.

Event host commands

~setroler @User: Temporarily grants the Delubrum Roler and Run Pinner roles to the specified user.

~setpriority @User: Temporarily makes a user a priority speaker in voice channels. This is useful for raid settings, where it is helpful to make a caller easier to be heard over others.

~removepriority @User: Removes priority speaker permissions from a user.

~mute @User: Mutes the voice communications of a user for 3 hours, or until they are unmuted.

~unmute @User: Unmutes a previously-muted user.

Run Pinner commands

~pin: Temporarily pins a message in a run channel. You can either provide the message to be pinned as a message link, or you can use the command while using the Reply feature on a message. Messages will be pinned for 4.5 hours.

~unpin: Unpins a message that was pinned using the ~pin command.

Delubrum Roler commands

For the following commands, the supported progression roles are:

• Trinity Seeker Progression

• Queen's Guard Progression

• Trinity Avowed Progression

• The Queen Progression

~addprogroles FFLogsLink: Adds progression roles for an entire raid according to the provided FFLogs link. Non-Rolers can also use this command in order to get roles for runs that were done outside of the server.

~addprogrole @User RoleName: Adds a progression role, and any previous progression roles, to a user. You can also provide multiple users in order to avoid using the command multiple times.

~removeprogrole @User RoleName: Removes a progression role from a user. You can also provide multiple users in order to avoid using the command multiple times.

Cancelling events

To remove an announcement that you have created, use the ~unannounce command. There are two variants of this command: One which takes the event's date and time, and another which takes your ~announce command's message ID.

The version of this command that takes your event's date and time works similarly to the ~announce command. Just use the command, and your event will be updated in the schedule channel and removed from the Google Calendar.

If you've scheduled multiple events at the same date and time, a prompt will be given for you to specify which event you would like to cancel. Simply send the number of the event you would like to cancel in order to continue.

To use the message ID variant of this command, use the message ID of your ~announce message. The message ID of your ~announce message can be found right above the announcement.

When an event is cancelled, its corresponding announcement will be updated to show that the event was cancelled. The announcement will then eventually be removed.

Rescheduling events

To reschedule an event that you have created, use the ~reannounce command. This takes two options: an identifier for your event (either a date and time or the message ID of your ~announce command), and the date and time you would like to reschedule your event to.

This will update both the embed in the schedule channel, and the corresponding event in the Google Calendar.

If you use this command with a run date and time as the first option, and you have multiple events scheduled at that date and time, a prompt will be offered for you to specify which of your events you would like to reschedule.

Saving community calendars

All calendar links end with a time zone written in their URLs, usually at their end. You can recognize the time zone in a URL by the text ctz= immediately preceding it.

An example URL. Note the ctz=America/Los_Angeles at the end of the URL.

Google Calendar uses time zone names as defined by the tz database. To adjust how events are displayed, replace America/Los_Angeles with the appropriate label from the TZ database name column of the table on the linked Wikipedia page.

You can add a community calendar to your own Google Calendar using the + Google Calendar button at the bottom-right of the webpage.

Clicking this button will take you to your own Google Calendar and give you an option to add the community calendar to your own calendar set.

If you would like to then save a calendar to an external application, click the settings button under the Other calendars section of the interface.

From here, scroll down to the Integrate calendar section and copy the text under Public address in iCal format. Refer to your calendar application's documentation to use this address to finish integrating the calendar.

The relevant address is located at the bottom of this settings section.

Run dates must be within the next 28 days, as that is the number of columns set in the Google Sheet.