Advanced Settings

The advanced settings can be set via the !advancedsettings command as well as for each event individually. The advanced settings that you define via command are the default values for each event. You can then deviate from those default values for each event by changing the advanced settings of that event.

deadline

Example
< deadline: 24 >
< deadline: -12 >

 

Description
The deadline dictates the time of event closure. It is provided as an offset in hours before the event. A value of 24 will close the event 24 hours before the events time. A value of -12 will close the event 12 hours after the events time. A closed event does not accept further Sign-Ups, except if it's done via the adduser/removeuser commands.

limit

Example
< limit: 25 >
< limit: 10 >

 

Description
The limit is the number of overall Sign-Ups allowed for the event. If set to 25, the event will accept 25 Sign-Ups and queue/bench all after that.

lock_at_limit

Syntax
< lock_at_limit: true >
< lock_at_limit: false >

 

Description
Events with a set limit will by default not accept further Sign-Ups. If this setting is set to false however, the limit will only be cosmetic on the event. Members will be able to sign up and the event will show the soft limit.

limit_per_user

Example
< limit_per_user: 1 >
< limit_per_user: 3 >

 

Description
Members can only sign up once to an event by default. This setting allows you to increase that. If the value is set to 3, a member can sign up to 3 times for the same event.

allow_duplicate

Example
< allow_duplicate: true >
< allow_duplicate: false >

 

Description
If multiple Sign-Ups per user is allowed via limit_per_user, then this setting will determine wether the user can place multiple Sign-Ups within the same role or not.

horizontal_mode

Example
< horizontal_mode: false >
< horizontal_mode: true >

 

Description
Sign-Ups on events are sorted vertically by default. If this setting is set to true, Sign-Ups will be sorted horizontally. This can save you some vertical space if your events have a lot of Sign-Ups on some classes.

bench_overflow

Example
< bench_overflow: true >
< bench_overflow: false >

 

Description
Sign-Ups that cross a limit, be that an overall or a class/role limit, will be pushed to the bench/queue by default. If this setting is set to false, the Sign-Up will just be denied without the push to the bench/queue.

queue_bench

Example
< queue_bench: true >
< queue_bench: false >

 

Description
There are 2 different ways of handling Sign-Ups that cross a limit. If this setting is set to true, members will be queued and if a spot opens up the queue will adjust accordingly. If this setting is set to false, members will just be pushed to the bench and remain there until a manager changes it.

temp_role

Syntax
< temp_role: true >
< temp_role: name >
< temp_role: date >
< temp_role: namedate>
< temp_role: Raider >

 

Description
If this setting is set to anything but false, a temporary role will be assigned to members that sign up to this event. If true is provided, the bot will create a role with the events ID as the name. If a role name is provided, the bot will create a role with that name instead. If a role with the same name already exists, that role will be assigned instead. If the role is created by the bot, it will be deleted 24 hours after the event. If it is an already existing role, the bot will only remove the role from signed up members and leave the role itself intact. The keywords "name", "date" and "namedate" are special because they will cause the temporary role to be named after the name of the event, its date or both.

vacuum

Example
< vacuum: false >
< vacuum: true >

 

Description
If this setting is enabled, the bot will attempt to clean up the channel on creation. It will check the last few messages and delete non-event and non-pinned messages.

force_reminders

Example

< force_reminders: false >

< force_reminders: true >

< force_reminders: 15 >

 

Description
By default, reminders are a premium feature that each user of a premium server decides individually for themselves. If this setting is set to true, the participants of the event will receive a reminder regardless of their personal setting. You can also enter a number to define the time in minutes before the event for the reminder is to be sent.

pin_message

Example

< pin_message: false >

< pin_message: true >

 

Description
If this is set to true, the bot will pin the event for as long as it's active. The pin will be removed once the event is closed or goes inactive.

deletion

Example

< deletion: false >

< deletion: true >

< deletion: 3 >

 

Description
If this is set to true, the bot will delete the event 24 hours after the events time. You can also customize the deletion time by putting in a number. The number reflects the deletion time in hours after the events time.

color

Example
< color: none >
< color: 5 >

 

Description
The value of the setting will change the color of the event embed. You can provide it a hex color, write out the color name or choose from the bots list of colors (most reliable).

mention_mode

Example
< mention_mode: false >
< mention_mode: true >

 

Description
If this setting is set to true, the bot will use mentions instead of plain names on the event. This feature is not recommended, as it is possible that a member is not cached for your discord client. If that is the case the mention will be displayed with the user id of the member instead of its name. This can especially happen a lot on the mobile app.

preserve_order

Example
< preserve_order: false >
< preserve_order: true >
< preserve_order: full >

 

Description
If this setting is set to true, the bot will preserve the order number in front of the users name if that user changes his Sign-Up. The order number will still reset if the user goes from or to one of the default emotes (late, bench, tentative, absence). If this setting is set to full, the bot will preserve the order number in all cases except absence. If it's set to false, the order number will reset every time the user changes his Sign-Up.

apply_unregister

Example
< apply_unregister: false >
< apply_unregister: true >

 

Description
If this setting is set to true, the bot will apply a unregister reaction to the event. Clicking on the unregister reaction will fully remove the user from the event.

attendance

Syntax
< attendance: true/false >
< attendance: [tag] >

 

Description
All Sign-Ups will be counted towards attendance if this is set to true. The attendance can be viewed via !attendance command. If the setting is set to false, this event will be excluded from the attendance calculation. You can also define a tag (for example < attendance: Raid1 > will enable you to only check the attendance for events with that tag via !attendance Raid1.

show_header

Syntax
< show_header: true >
< show_header: false >

 

Description
If this setting is set to false the events header will be hidden. The header is the part above the title containing the Leader and ID of the event.

show_title

Syntax
< show_title: true >
< show_title: false >

 

Description
If this setting is set to false the events title will be hidden.

show_info

Example

< show_info: true >

< show_info: false >

 

Description
If this setting is set to false, the date & time row on the event will be hidden. This is set to true by default.

show_roles

Example
< show_roles: true >
< show_roles: false >

 

Description
If this setting is set to false, the roles will be hidden on the event. The roles are the counters between the date/time and the Sign-Up content.

show_content

Example

< show_content: true >

< show_content: false >

 

Description
If disabled, the Sign-Up content will be hidden. This is set to true by default.

show_classes

Syntax
< show_classes: false >
< show_classes: true >

 

Description
Classes/fields are generally not shown on events until at least 1 member has signed up to it. Enabling this setting will always show the classes/fields on the event. This can be helpful if your members are struggling to know what reaction means what, as the field and class name will now be visible from the start.

show_emotes

Syntax
< show_emotes: true >
< show_emotes: false >

 

Description
If this setting is set to false, the emotes in front of Sign-Ups will be hidden.

show_numbering

Syntax
< show_numbering: true >
< show_numbering: false >

 

Description
If this setting is set to false, the order numbers in front of Sign-Ups will not be displayed. The order numbers serve the purpose of displaying in which order the members have signed up.

show_allowed

Syntax
< show_allowed: true >
< show_allowed: false >

 

Description
If this setting is set to false the allowed roles at the bottom of an event, if any are set, will be hidden. The allowed roles will still function and decline users without one of the roles. This will only hide the text.

show_footer

Example
< show_footer: true >
< show_footer: false >

 

Description
If this setting is set to false, the footer of the event will be hidden. The footer is the small print at the very bottom.

show_localtime

Example
< show_localtime: true >
< show_localtime: false >

 

Description
If this setting is set to true, the event will display a line with the local date & time of the viewing user. The shown time will reference the users system time/zone. The shown date & time format depends on the users discord language settings.

show_zonedtime

Example
< show_zonedtime: true >
< show_zonedtime: false >

 

Description
If this setting is set to false, the default display of the date & time with the currently set timezone will be hidden. You can consider turning this off, if you are using the local time via < show_localtime: true >.

localtime_as_link

Example
< localtime_as_link: true >
< localtime_as_link: false >

 

Description
This is a temporary setting to allow you to circumvent a bug on the Discord Android app. Currently timestamps that are wrapped by links don't show properly on Android. If you have a lot of users on your server that are on android and you want to use the local timestamp reliably, it is advised to put this setting to false. Not having the local timestamp wrapped by a link will have it be shown properly on Android as well.

show_countdown

Example
< show_countdown: true >
< show_countdown: false >

 

Description
If this setting is set to true, the info section of the event will also display a countdown to the event start. The countdown is a special discord markdown field and will show the correct time to the event for each user individually based on their system time/zone.

defaults_pre_req

Example
< defaults_pre_req: true >
< defaults_pre_req: false >

 

Description
Members who sign up for one of the default roles (Bench, Late, Tentative, Absence) will be prompted to pick an actual role first before they can sign up to a default role. If this setting is set to false, members will be able to sign up to a default role directly instead.

disable_archiving

Example

< disable_archiving: false >

< disable_archiving: true >

 

Description
If you have archiving enabled on your server but you want a specific event to be excluded, set this to true.

bold_all

Example

< bold_all: false >

< bold_all: true >

 

Description
If this setting is set to true and members are allowed to sign up multiple times to an event, then each Sign-Up will be displayed in bold text. That means each Sign-Up will also be fully counted in class and role counters. If this setting is set to false, then subsequent Sign-Ups will keep the standard behaviour of not being displayed in bold text and not counted in class and role counters.

bench_emote, late_emote, tentative_emote, absence_emote

Example

< bench_emote: :fire: >

< late_emote: 779447159669915698 >

< tentative_emote: default>

< absence_emote: remove >

 

Description
The currently set default emotes. You can replace them with your own emotes by entering the emote or its ID. You can reset the setting to the default emote by entering default. You can remove the default emote entirely by entering remove.

spec_saving

Example
< spec_saving: true >
< spec_saving: false >

 

Description
Wether the spec choice is to be saved or not. This only applies to templates with spec select Sign-Up. If spec_saving is set to false, the bot will not remember the previously picked spec and ask the user to choose on each Sign-Up. If spec_saving is set to true the bot will remember the previously picked spec of the reactions and skip the spec select.

font_style

Example
< font_style: none >
< font_style: 2 >

 

Description
Determines the font style of the event title. 1-3 are different emote sets that can be used. The style can also be set to none to have the title displayed in normal discord font.

alt_names

Example
< alt_names: false >
< alt_names: true >

 

Description
If this setting is set to true, members will be messaged after their Sign-Up with the option to change their displayed name on the event.

allowed_roles

Example
< allowed_roles: all >
< allowed_roles: Raider >
< allowed_roles: Officer, Raider, Member >

 

Description
There are no restrictions for signing up by default. Providing roles to this setting however will only allow the provided roles to sign up to the event.

response

Example
< response: 3 >
< response: Please whisper Mitmoc for invite! >

 

Description
A response that will be sent to members on Sign-Up. You can either enter a message directly or provide the ID of a saved embed message (check out the !embed command). Enter none to remove send no response on Sign-Up.

opt_out

Example
< opt_out: none >
< opt_out: 822942478373879859 >

 

Description
Provide the ID of an existing event and the bot will copy over the Sign-Ups from that event to the new event. This allows you to have your users opt out of events instead of having to opt in.

mentions

Example
< mentions: none >
< mentions: Member >
< mentions: Officer, Member, Mitmoc >

 

Description
Provide roles or members to be mentioned on event creation. Separate roles and members with a comma.

image

Example
< image: none >
< image: https://www.imgur.com/szgu76.png >

 

Description
The image is placed at the bottom of an events embed. It is recommended to use a wide image, because the formatting that discord applies has the effect of reducing content space of the embed. Regardless of the dimensions, the max-width of the embed will be slightly reduced if any image is set. This is just how discord embeds work currently and there is no workaround.

thumbnail

Example
< thumbnail: none >
< thumbnail: https://www.imgur.com/szgu76.png >

 

Description
The thumbnail is placed at the top right of an events embed. It is not recommended because the formatting that discord applies has the effect of reducing content space of the embed if a thumbnail is set. Use at your own discretion.