Event Notifications
Raid Organizer
has a few ways to send messages to:
- Remind users to sign up
- Tell users that an event is cancelled
- Let users know a new event was created
- Tell signed up users that the event is about to start
And much more.
There are 3 different notification commands to fill all possible use cases:
📄️ Manual Notification
Trigger a notification message manually
📄️ Automatic Notification
Notification messages send automatically by Raid Organizer
📄️ Event Create Notification
Send a notification message on event create
📄️ Cancel Notification
Notification sent on event cancellation
Custom Message Fields
To customize your message, Raid Organizer
is listening to the following fields and replaces them with the correct values:
Event Fields
${event_author}
=> resolves to the event creator or the bot, if it is a repeating one${event_channel}
resolves to the event channel as mention${event_title}
=> Shows to the event title${event_link}
=> Shows to the event link${event_start_time}
=> Shows the event start time${event_end_time}
=> Shows the event end time${time_till_start}
=> Shows a relative time till the event starts (like "in 10 minutes")
Format Links
Discord uses Markdown
inside embed's. To format a link, you need to use the following format [link title](http://link_url)
.
A link to an event could look like this [${event_title}](${event_link})
.
General Sign Up Fields
${total_count}
=> Total amount of sign ups to the event${role_count}
=> Total amount ofrole
emoji sign ups${status_count}
=> Total amount ofstatus
emoji sign ups${total_unique_count}
=> Unique (Every user just counts once) amount of sign ups to the event${role_unique_count}
=> Unique (Every user just counts once) amount ofrole
emoji sign ups${status_unique_count}
=> Unique (Every user just counts once) amount ofstatus
emoji sign ups${max_total_count}
=> Maximum sign ups allowed${max_role_count}
=> Maximumrole
emoji sign ups allowed${max_status_count}
=> Maximumstatus
emoji sign ups allowed
You can also find those numbers at the bottom of the event.
In the example above:
${total_count}
would resolve to4
.- Since there is no total sign up limit (no /),
${max_total_count}
would resolve to0
. ${role_count}
and${max_role_count}
would both resolve to 3.- And
${status_count}
would be 1.
Custom Sign Up Fields
${role_count_x}
=> Sign ups with the passedrole
field${role_count_limit_x}
=> Maximum allowed sign ups with the passedrole
field${status_count_x}
=> Sign ups with the passedstatus
field${status_count_limit_x}
=> Maximum allowed sign ups with the passedstatus
field
Those numbers are located nextto the role/status category name.
In the example above:
${role_count_dd}
would become2
.${role_count_tank}
/${role_count_limit_tank}
would become1/2
.
Other Fields
${ping_user_role}
resolves to a mention of the setuser role
You can not @ping a role in a DM. So if you use @ping or ${ping_user_role}
in a DM, Discord will change it to @deleted-role