• Bugfixes
• Other Changes

Bugfixes​

• Fixed issue that the bot did not check user role corrects on status emojis. This resulted in users being able to sign up to events (with status emojis), which didn't have permission to.
• Fixed issue that the signup cooldown wasn't checked correctly on signups with status emojis.
• Fixed issue that the "Missing Permission" message wasn't printed if a clean_mode was set but the bot missed permission to delete messages.

Other Changes​

• Improved bot stability

• Bugfixes
• Other Changes

Bugfixes​

• Sign-ups and sign-offs occasionally took too long (exceeding 3s), causing Discord-side timeouts. While the action usually completed successfully, the interface would report an error; this has been optimized.
• Fixed an issue where communication between bot shards would occasionally fail.

Other Changes​

• Resolved an issue introduced in the last major release that prevented automatic database backups from running.

This version took a bit longer, but it includes some big changes both feature- and performance-wise.

As always, it includes some new features, minor improvements and a lot of bug fixes!

• Features
  • Bot Personalization (Premium)
  • Temporary Discord Role
  • Website Improvements
  • Notable Mentions
• Bugfixes
• Other Changes

Features​

Bot Personalization (Premium)​

• Added commands /bot avatar set and /bot avatar reset. These commands allow you to set a custom bot avatar or reset it to default.
• Added commands /bot banner set and /bot banner reset. These commands allow you to set a custom bot banner or reset it to default.

Temporary Discord Role​

There is now a new command: /toggle event_roles. See the event roles documentation for full details.

If enabled, the bot creates a temporary Discord role upon event creation. Users who sign up for the event—using a role emoji—will be automatically assigned to this Discord role.

While this is useful on its own, the real benefit is the ability to restrict voice channel access to that specific role. The /event_voice set command now has two new arguments: role_view_only and role_connect_only (naming needs improvement).

• If role_view_only is set to "True", only users with the event role can see the voice channel.
• If role_connect_only is set to "True", only users with the event role can join the channel, though others can still see it.

Additionally: If event roles are enabled and a notification message with "Attending Role" as "state" is used, the role is pinged instead of each user individually.

Website Improvements​

The website UI had a complete revamp to improve both the UI and the UX.

• "Limits" on the "Overview" page now shows an information banner when premium is active.
• The "Upcoming Events" list on the website now also has a "Calendar" view.
• "Create Event" now has a "Simple" and "Advanced" tab to simplify event creation.
• You can now set up channels and remove them from the website.
• Added event notifications, logging and voice channel setup to the "Channel Settings".
• Improved the "Premium" page.

Notable Mentions​

• Sub-Role sign-ups now open a modal. This should make sign-ups easier.
• If an event that was closed automatically gets opened again by a user, the event now stays open and will no longer be closed again by the bot.
• Simplified /event user get_hidden_users. It no longer requires a field name to be passed.
• Added a lot of commands to the documentation.

Bugfixes​

• Fixed an issue where signup_template show broke if the server had too many custom templates.
• Fixed an issue where gears guild consume sometimes didn't throw a proper error message.
• Fixed an issue where the website sometimes didn't display the correct error message. Instead "Unknown Error" was shown.
• Fixed an issue where /event user get_hidden_users broke when top-level emojis were enabled in the used Signup Template.
• Fixed an issue where you couldn't navigate to your server on the website until you completed the bot setup in Discord.
• Fixed an issue where the website displayed the event start/end time in UTC on the repeating event page.
• Fixed an issue where repeating events didn't load correctly on the website if no channel was configured for that server.
• Fixed an issue where the "Upcoming Events" list on the website displayed events although the user didn't have the user role to sign up to them.
• Fixed an issue where /event_start_notification list printed a misleading "User state".

Other Changes​

• Unified "Command timed out." messages.
• The "Sign Up/Off Completed" message, which gets sent when you sign up/off to an event, is now automatically removed after 1 minute.

• Bugfixes
• Other Changes

Bugfixes​

• Fixed an issue where the Channel Settings on the website did not work for some users.
• Fixed an issue where the /limits command did not function correctly.
• Fixed an issue where /channel user set would break if the currently used role had been deleted.
  note

  There is still a Discord limitation where @everyone does not appear in the dropdown list. For now, you need to use the website to configure @everyone. This will be resolved in v6.2.0.

• Fixed an issue where saving role and status signup limits via the website caused those limits to stop working.
• Fixed an issue where, if too many users were hidden from an event due to Discord's message length limit, the /event user get_hidden_users command would no longer function.
• Fixed an issue where the commands logging setup and logging edit did not print a "Timeout" message on timeout.

Other Changes​

Before this release, if you kicked Raid Organizer from the server, all information to this server was dropped from the database. This has now changed. Raid Organizer still drops all user, event, channel, etc. information, however, any limit increases and premium subscription stay.

• Features
  • Customizable Signup Cooldown
  • Signup Groups
  • Allow Multiple User Roles
• Bugfixes
• Other Changes

Features​

Customizable Signup Cooldown​

v6.0.0 introduced buttons for sign-up and also a 10-second cooldown for user sign-ups. That cooldown was later disabled because it annoyed most users.
v6.0.1 reintroduces this feature, but it's disabled by default. It now also allows customization via /signup_cooldown set.
For more information, check out the docs.

Signup Groups​

You can now create Signup Groups, which are basically groups of users with a given role.
Signup Groups are useful for events where the same users always attend. They're essentially a convenient shortcut for using /event user signup.
For more information, check out the docs.

Allow Multiple User Roles​

You can now set multiple user roles in a channel with active Premium. This quality-of-life feature should make managing Discord permissions easier.

Bugfixes​

• Fixed an issue where /upcoming message create displayed events from deleted channels.
• Fixed an issue where the bot did not remove channel configs from the database when the corresponding Discord channel was deleted.
• Fixed an issue where the "Missing Permission" message was not correctly shown when signing up for events via buttons.
• Fixed an issue where /event user get_hidden_users didn't edit the message correctly.
• Fixed an issue where "Upcoming Events" on the website did not show the event start time in your server's local time.

Other Changes​

• The /upcoming message create command no longer asks for channels as command arguments. Instead, a selection menu is used to choose the channels. Due to a Discord limitation, all channels are listed. However, the bot ignores invalid channels (i.e., channels not set up for events) if they are selected.
• Replaced the /signup_template list and /signup_template get commands with /signup_template show. It now takes an optional template as an argument. If a template is provided, it behaves like the old get command; if not, it lists all templates.
• Notification messages no longer include an empty embed if no text is entered in the embed message field.

• Bugfixes

Bugfixes​

• Fixed issue that the bot send and "Unknown Error!" message if you used an emoji that got deleted.
• Fixed an issue that emoji_behavior 2 wasn't working if you used the same emoji info twice in a sub emoji. The following example wasn't working correctly:
  • <emoji_1>,role,DD,DPS
  • <emoji_2>,role,DD,DPS
• Discord events only allow images up to 10240KB (~10MB). If a bigger image was used during event creation (and /toggle discord_event is on), the Discord event creation failed. This is no longer the case. The Discord event will be created but without an image.
• If an unsupported image was used for the Discord event, creating the Discord event failed. This is now also fixed. In case of an unsupported MIME type, the Discord event is created without an image.
• /invite no longer prints some "test" message 😀
• /gears guild share now works again
• Fixed issue that webpage only displayed a "Bot is no longer in the Guild" message instead of redirecting to the invite page.

• Bugfixes
• Other Changes

Bugfixes​

• Fixed a couple of issues where the bot did not send an (command) error message correctly.
• Fixed issue that notification commands (event_create_notification add, etc.) did not correctly send a "Timeout" message on timeout.
• Fixed an issue that signups didn't work correctly if the emoji info had a tailing whitespace. Example: "role,DD "
• Fixed an issue that some custom signup templates did not apply the 10 seconds cooldown correctly
• Correctly send error "Command not found!" if /help was used with an invalid command

Other Changes​

• Since I changed the Discord library with v6.0.0, "Discord Events" finally update their location correctly if you use automatic voice channel creation (/event_voice set)

As always, it includes some new features, minor improvements and a lot of bug fixes!

• Features
  • Buttons For Sign Up
  • Event User (Un)Confirm
• Bugfixes
• Other Changes

Features​

Buttons For Sign Up​

Raid Organizer now uses buttons instead of emojis for event signup.

Since this is kinda the whole news, let's discuss why buttons are better than emojis:

• Anti spam. Currently it's limited to one signup every 10 seconds. I might allow to change that in the future.
• emoji_behavior 2 no longer sends a message to the channel that can be read by all users!
• The buttons now include the name of the signup field. This makes it easier for users to find the right role.
• Closed events have disabled buttons! No more pressing emojis and receiving a DM that the event is closed.
• Role and Status emojis are now separated. Role emojis use normal buttons while Status emojis are combined in an attached drop down.
• Event creation is way faster! While emojis needed to be added one by one, adding buttons it just one API call to Discord.

Changing from emojis to buttons wasn't an easy task. I therefore want to thank all BETA-Testers for their help and bug reports!

Event User (Un)Confirm​

/event user confirm and /event user unconfirm no longer have user 1, user 2, etc. as input. They now work like /event user signup. This allows 2 things:

1) You can now also (un)confirm non Discord users. 2) User selection is more simple.

Bugfixes​

• Fixed an issue that /event user unconfirm did not work correctly if a user had multiple sign ups and was confirmed with the "not primary choice".
• Fixed an issue that in some cases organizers did not receive a DM if a confirmed user signs off and therefore gets "unconfirmed".
• Fixed issue that get_hidden_users did not work correctly if the used signup template had emoji title enabled.
• /user signups get no longer breaks if a user has 0 sign ups in the given timeframe
• /user signups get displays the name of non Discord users correctly
• Fixed issue that /user signups get broke in some conditions if minimum was selected as limit
• Fixed issue that /statistics did not work in DM's.
• /repeating_event show now splits the message into multiple embed fields if the config is too long.
• /event_start_notification list no longer shows No event start notifications found! if at least one notification is set up.
• /event_start_notification list now displays the User state correctly (without abbreviation).
• /event user signoff no longer says "Sending DM notifications" if the users are non Discord users.
• /event user signoff no longer prints the message "Signing off users!" twice.
• /event user signoff no longer displays "Select a User to sign up".
• Fixed an issue that "overlapping events" created an error message with "invalid date/time format" if the followup message wasn't answered within 3 minutes. Now the bot correctly aborts the event creation on timeout.
• Fixed an issue that "overlapping events" in some cases just aborted the event creation.
• If you have an overlapping event and you adjusted the time, but the new time was still overlapping with an event, the bot printed a new questionnaire but did not close the old one. This is now fixed. The first questionnaire is now correctly disabled.
• Fixed a potential issue that event start notifications did not notify all users if the bot performed a restart shortly before the notification.
• Fixed issue that /user signups get did not work if non Discord users were signed up to events and file export was activated.
• Fixed issue that /user signups get had broken formatting for non Discord users in the info message
• Fix issue that under some rare condition the signup template broke in a way that the event displayed sub emojis to main emojis that did not have any.
• logging edit no longer sends an error message if you don't edit anything.

Other Changes​

• template parameter was renamed to signup_template in /event create command.

• Bugfixes

Bugfixes​

• Fixed issue that the website pages to create an event or signup template did not work for most users.

• Bugfixes

Bugfixes​

• Fixed issue that under a rare condition the lifetime premium membership got reset.
• Fixed issue that event messages did not refresh correctly on sign up in some cases.
• Fixed issue that setting server language via webpage did not work.
• Fixed issue that using event user signup with "Non Discord User" also displayed a message suggesting DM are send to those users.
• Fixed issue that it was possible to sign up a user without a name using /event user signup with "Non Discord User". Example: using "user1,," 2 users were signed up. One with "user1" as name and one without a name.
• Fixed issue that sign up numbers did not work on "Non Discord Users"
• Fixed issue that repeating_event show displayed a wrong time for the next event creation.

• Features
  • Reworked repeating_event list
  • Get Users With Least/Most Sign Ups
  • Allow Sign Ups of Non Discord Users
• Bugfixes
• Other Changes

Features​

Reworked repeating_event list​

The /repeating_event list command was renamed to /repeating_event show. By default the show command behaves the same as the old list command. The only only difference is that the show command accepts an additional parameter id. If id is set, only the repeating entry with that id is displayed.

Get Users With Least/Most Sign Ups​

There now is a new command called user signups get. This command allows you to get users that meet certain sign up criteria. For more information refer to the docs.

Allow Sign Ups of Non Discord Users​

The commands /event user signup and event user signoff got a complete rework. They now both allow signing up/off users that do not have a Discord account.

Changes:​

• They no longer have optional fields to allow up to 10 user sign ups.
• Instead they now have a required field called user_type.
• If "Discord User" is selected, Raid Organizer creates a dropdown menu in which you can select all users you want to sign up.
  note

  This is an autocomplete field. If you can't find a user, start typing it's name.

• If "Non Discord User" is selected, a modal pops up where you can enter names in a comma separated list.

Bugfixes​

• Fixed issue that get_hidden_users did not show the correct users under some conditions.
• Fixed issue that repeating_event show did not display the "Next creation" time correctly after DST change.
• Fixed issue that due to some crodwin update the bot saved some invalid values for some languages. That caused the website "Server Settings" page to not work for those servers. This is fixed now.
• event_template setup now correctly throws an error if the server is not set up yet.
• Fixed issue that the link to the website, from the /signup_template create command, was wrong.
• Signup templates created via the website threw an error if shared with others. This is now fixed.
• /signup_template export now correctly exports the new emoji title property.
• Fixed issue that /signup_template edit with emoji title worked with "show" but not with "hide".
• Fixed issue that website did not display the bot servers correctly because of a caching issue. The exact issue was: Bot not on a Discord server => Bot invite to a server via website => Bot still is shown as not on that server.
• Fixed a couple of issues with the website where some users got "Unknown User/Guild/etc" errors.
• Fixed issue that the event start notification got send even when the event itself got cancelled.

Other Changes​

• repeating_event show now shows the "Next creation" time as a discord timestamp.
• Using /patreon key list now also shows the server id and name if a key is set.

• Bugfixes
• Other Changes

Bugfixes​

• Fixed issue that /gears user contribute did not return correctly if the user has never voted.
• Fixed issue that is some edge cases event creation did not work via the website.
• Fixed issue that website did not show signup template errors right on page load.
• Fixed issue that in one edge case it was possible to set redo as timezone. That can caused issues in a lot of other commands.

Other Changes​

• Increased the signup template title max length from 15 to 25.

• Bugfixes
• Other Changes

Bugfixes​

• Fixed issue that creating a signup template via the homepage did not work in some cases.
• Fixed multiple issues that editing a signup template via the homepage did not work in most cases.
• Fixed issue that events created via the homepage ignored the used description.
• Fixed issue that voting no longer gave you gears.

Other Changes​

• repeating_event list now adds a button with a link to error codes if at least one repeating event entry is deactivated.

This version includes some new features, new website functionality and a lot of bug fixes and minor improvements. So let's start!

• Features
  • Event Cancel Notification
  • Website Changes
  • Close Events Relative To End-Time
  • Signup Emoji In Event Field Titles
  • Top Guild Gear Donors
• Bugfixes
• Other Changes

Features​

Event Cancel Notification​

You now have the option to set an amount of users that are required for an event to take place. The event will automatically be canceled if X minutes/hours/days, before the event start, the required amount of users isn't exceeded. This means that the event will be closed and, if configured, all signed up users receive a DM notification.

Added a few new commands to manage event cancellation:

• event_cancel_notification add => Creates a cancel notification for that channel
• event_cancel_notification remove => Removes a cancel notification for that channel
• event_cancel_notification edit xxx => Edits the cancel notification for that channel. xxx is the property to edit

Read more about Event Cancel Notifications

Website Changes​

You can now create events from the website. Simply log in, click "Manage Servers", select your server and click "Create Event".

You can also now create, edit and delete signup templates from the website. In the server view select "Signup Templates" have fun!

Close Events Relative To End-Time​

Some users want to have the advantages from automatically closing events, while also allow late arrivals to still sign up. This is now possible!

Added the command event_close behavior set. With this command you can now choose if the event_close time set is relative to the event start time or to the event end time.

Signup Emoji In Event Field Titles​

signup templates now have the property emoji_title. If emoji_title is true, top level emojis will also be displayed at the field name. See doc for more information.

Top Guild Gear Donors​

Added a new command called gears guild top_donors. Like other gear related commands, this one can only be used in the ⛭gear-exchange on the support server. In addition, it can only be used by users that are moderators, admins or the onwer of the target server!

This command shows the top 10 users of your guild that donated to most gears! I am sure you find some way to reward those brave users! ❤️

2 more additional notes: 1) There is no previous history. The counting starts with this release 2) The message is ephemeral. This means that the bot response is only visible to the user that executed the command.

Bugfixes​

• Fixed issue that changing the default template via the website did not work.

• Fixed issue that event_template create did not work with relative date (now, ...) and time only (20:00) inputs when the event_template signup had no default time.

• Fixed issue that the start time of event templates could not be removed with the /event_template edit command.

• Fixed issue that the bot failed silently on event user signup if the role/sub role combination was too long. Discord has a limit of 80 characters for a button label. If that was exceeded, the bot just exited the command. This should no longer happen, but I still don't recommend using such long (sub) role names.

• Fixed broken links during signup_template create in the emoji_behavior section.

• Fixed issue that creating a repeating event with:

  • a custom interval
  • using Monday/Tuesday/...
  • And only choosing one day

  Always failed with "Invalid interval."

• Fixed issue that using the Import Template button in 🔄template-share did not take server premium into account. It therefore failed when you exceeded the signup template limit.

• Fixed issue that using the Download Template button in 🔄template-share did not work on some templates.

• Fixed issue that servers with a UTC-X timezone were not able to create events with today if the UTC time was already on the next day.

• Fixed issue that /permission did not show the right permissions (library bug)

Other Changes​

• Bumped all dependencies to their newest version and also improved the database performance.
• Reduced the load time of https://raidorganizer.org/guilds by a loot. With my test data I got it reduced from 1.2 seconds to 0.02 seconds. Let's see how it behaves on the live server ;)
• You can no longer add emojis via the signup_template add command. Please now use the website for that. This was done because the current functionality had some issues and it was also not very user friendly. However, you can still change emojis and/or remove them.
• Renamed a couple of commands:
  • change_organizer => channel organizer set
  • change_user => channel user set
  • get_event_channels => channel list
  • toggle event_closure => event_close toggle
  • event_closed_color set => event_close color set
  • event_close_time set => event_close time set
• event_template setup/edit/remove can now be used in any channel by a user that has at least organizer permissions in one of the set up channels.
• On event creation via event_template create, the error message is improved when the event template is using an outdated signup template.
• Many error messages now have a link to the docs page with additional context.
• Fixed some spelling mistakes

• Bugfixes

Bugfixes​

• Fix issue you could not create an event from an event templates without a start time without specifying the full Date/Time.
• Fix issue that removing the start time on an event template did not work.
• Fix issue that using the event user notify command with only "DM" did not work when too many users needed to be notified.

• Bugfixes

Bugfixes​

• Fixed issue that delaying the event start time still closed the event at old the time. For example having an event with a start time at 20:00, and than moving the start time to 20:30, still closed the event at 20:00 instead of 20:30.
• Fixed issue that editing the event start time to something earlier could lead to the event closing on the original time. For example: Event start time 20:00 and than edit it to 19:50. The event would still be closed at 20:00 instead of 19:50.
• Fixed multiple issues, where using an event_template with a default start_time did "funny" things when you created an event from that template and wanted to overwrite the start time. For example a default time of 20:00 became 20:00 21:00 when you wanted to overwrite the start time to 21:00.
• Fixed issue that in some cases signup_templates with an emoji behavior of 1 did print emojis in a "strange" way. Now sub emojis are always directly added after the main role emoji.
• Fixed issue that invalid start/end time inputs did, in rare occasions, not print an error message.
• Fixed error that /statistics did not work

Other Changes​

• The commands event edit, event_template edit and repeating_event edit now allow to reset fields that are not required. For example: description, end time, footer text, ... . To reset those fields, use clear as value.
• The commands event user signup and event user signoff can now be used by users with the user-role in LFG channels.
• Improved some "signup templates" strings by adding "signup" to the template. Example: custom template is now custom signup template.
• Improved error codes when a repeating event stops working.

• Bugfixes

Bugfixes​

• Fixed an issue where a Discord API outage was able to break repeating events.
• Finally fixed an issue that could lead to repeating event being off by 1h after DST change.
• Fixed an issue that get_hidden_users displayed None as sign up number.
• Fixed an issue that could lead not displaying all users when using the get_hidden_users command.
• Fixed a rare issue that could lead to the bot being stuck in typing when using the event user signup command.
• Added a fallback loop when adding a reaction to a message fails because the Discord API is busy.

This is a small bugfix version of v4.4.0

• Bugfixes

Bugfixes​

• Fix the issue where setting a repeating event interval with repetition on Sunday results in the event being repeated on Saturday instead.

This is a small bugfix version of v4.4.0

• Bugfixes

Bugfixes​

• Fixed issue that the guild name in the payment notification wasn't italic. Instead it just had a leading _.
• Fixed a rare issue where the event deletion did not work when attaching a file to the exported event was enabled.
• Fixed a rare issue where auto event closure did not work when attaching a file to the exported event was enabled.
• Fixed issue that setting the export channel via the webpage did not work.
• You now get an error message if the bot is missing permissions when using the event user signup command.
• Fixed issue that creating a repeating event (with premium), did throw "This interaction failed" in some rare cases (when the workload on the bot was high).
• Fixed issue that if you edited the repeating event start time to a time which would be after the end time, the bot did not ask you if you want to change the end time as well.
• Fixed issue that export_event add_file only worked if you set both parameters.
• Fixed issue that attaching the export file to the exported event failed if the event title had certain characters.

This is a small bugfix version of v4.4.0

• Bugfixes
• Other Changes

Bugfixes​

• Fix issue that /upcoming events was not working as intended if you where signed up for at least one event.
• Fix issue that setting limits in a custom signup template did not work if you were using the same emoji multiple times.

Other Changes​

• Changed payment provider for one-time purchases. I now use Paddle instead of FastSpring for one-time purchases on the website.

This is a rather big update, and, due to the big changes made in this version, the Beta-Team was now testing it for ~2 Months.

• Features
  • Share Signup Templates
  • Use Same Emoji Multiple Times
  • Signup Template Clone
  • Change toggle at_mention Command
  • Show Preferred Option
  • Export Events
• Improvements
• Bugfixes
• Other Changes

Features​

Share Custom Signup Templates​

Sharing custom templates with others is something a lot of users do. Since there were a lot of issues in the past with finding the right template and importing it, I added a new command /signup_template publish.
This command should make the process of sharing, finding, and importing templates easier. For more information, check the sticky message in in 🔄template-share.

Use Same Emoji Multiple Times​

This was a highly requested, and very complex, feature request. Basically, you could not use the same emoji multiple times in one signup template. This was due to how I saved the template internally in the database. I now changed the structure of how emojis are saved, which allows you to basically create templates where the same emojis are used multiple times in different subgroups.

1:⛏️,role,Great Axe
2:♥️,role,Great Axe,Life Staff
3:🔨,role,Great Axe,Hammer
4:🔨,role,Hammer
5:♥️,role,Hammer,Life Staff

Signup Template Clone​

Added the /signup_template clone command. This command is a shortcut to using /signup_template export and /signup_template import.

Change toggle at_mention Command​

The /toggle at_mention command was renamed to display_names set. This was needed due to the case that a Discord user now can have up to 3 different names. There are "Account names", "User Names" and "Server Nicknames". You can read more about the command here.

Show Preferred Option​

• Added new command toggle show_user_choices
• If enabled, users with multiple sign ups now have a (Preferred) or (Choice X) next to their user name.
  note

  Preferred is only shown if the user has 2, or more, sign ups with "role" emojis. "status" emojis do not trigger this.

Check out the doc to this feature.

Export Events​

Added new command /export_event add_file. If enabled, a .json or .csv file is added to exported events. The content of the file can be adjusted to have only users exported that are signed up, not signed up, etc. This should help you to have a better overview of how often a user did (not) sign up over the last events.

Improvements​

• You can now buy Event Templates via Gears/Paypal
• Improved help of the command /sign_up_number_behavior set
• Improved help of the command /event reload
• Better errors on the website when API calls fail
• On signup_template create finish, the bot now sends a DM to the user with how to use the newly created template.
• event user confirm now uses buttons instead of emojis. This was
  1. needed because a user can now be signed up with the same sub emojis under 2 different categories. Emojis would not allow that to work.
  2. Buttons are way faster 😉
• Made the signup_template import command a bit smarter
• On signup_template create finish, you now get a message with "How to use it" information.

Bugfixes​

• Fixed issue that confirming a user, which was signed up multiple times in the same event, did not work.
• Fixed issue that no error message was printed if permissions were missing when using the help command.
• Correctly print error message if the log config input misses some fields.
• Fixed issue that event user notify did not trigger an error if the entered message was too long.
  NOTE 1: This can only happen if you use Custom Message Fields, since they take up more space when the fields get resolved.
  NOTE 2: This error message can only be printed on event user notify. If you entere a message ,that might be too long, with the event_start_notification or event_create_notification, there is no way to predict the sice since the length is determined by the event.
• Fixed issue that the event user notify test_message only worked if you selected DM as notify_type
• Fixed issue that /event_start_notification edit message always edited the message 1, even if another nr was passed.
• Fixed issue that ${status_count_xxx} did not work correctly
• Fixed issue that after signup_tempalte create command finished, the channel message wasn't updated correctly
• signup_template edit and only changing the emoji description no longer gives you "emoji already in use". Instead the emoji stays the same but the emoji description is edited.
• Fix issue that in very rare cases usernames were displayed italic in the event.

Other Changes​

• Renamed commands to fit together in the export_event group:
  • export_channel set => export_event channel set
  • toggle export_event_on_close => export_event toggle

This is a small bugfix version of v4.3.0

• Bugfixes

Bugfixes​

• Fixed issue that using the event user confirm command failed if a user was signed up with multiple roles.

This is a small bugfix version of v4.3.0

• Bugfixes
• Other Changes

Bugfixes​

• Fixed an issue that the original information message send by event user notify did not get updated correctly after all messages are send.
• Fixed an issue that event create with only today (note: today 1h was working) was not working.
• Fixed an issue that in a very rare case, the website could not parse and display your server settings.
• Fixed an issue that the search in the nr field of event_start_notification edit/remove/... did not work correctly.
• Fixed an issue that repeating_event remove did not print a "success" message if you removed the first entry of the list.
• Sometimes users import a signup template that they edited manually. If the limit names are wrong, this could cause that the whole template no longer works. I added some temporary guards for that. This way, the bot now uses default values in that case. Since next up is a signup template rewrite, I might find some other solution in the future.
• Fixed an issue that event user notify did send 2 messages to the channel if Channel was selected as notify_type.

Other Changes​

Added a lot of small "bug fixes". Stuff that doesn't really effect the end user experience but spammed my log files.

This is a small bugfix version of v4.3.0

• Bugfixes

Bugfixes​

• Fixed an issue that after event edit <description>, the newlines in the Discord event view were broken
• Fixed an issue that users with the moderator role and/or administrator permissions were not able to edit server wide settings on the homepage.
• Fixed an issue that even if changing setting, changed via the homepage, failed, the homepage returned "Saved successfully".

This is a small bugfix version of v4.3.0

• Bugfixes

Bugfixes​

• Fixed an issue that no error message was printed if setup_channel was used with @everyone as organizer role
• Fixed an issue that event reload did not remove the old event message if a thread was attached
• Fixed a few minor issues regarding the website to bot communication. This should now be a bit more smooth.

"Improvements"​

• Applied latest translation progress. Forgot that during the 4.3.0 release 😅

This is a fairly small update on the bot side, but a huge update on the website side. I have rewritten all API communication between the bot and the website. I also layed the foundation for further API exposure, which would allow you to access the bot without Discord or the website.

• Features
  • Website Rewrite
  • Overlapping Events
• Bugfixes
• Improvements

Features​

Website Rewrite​

The Rewrite​

I have, more or less, completely rewritten the old interaction website. So... What changed?

• It now uses routes! This means you can use the back and forward buttons of your browser to navigate through the website.
• You can also press F5 to reload the page without getting moved back to the guild selection page.
• The website is now fully responsive! This means you can use it on your phone or tablet without any issues.
• The white is gone! The website now uses a dark theme. Better for your eyes ;)
• I reduced the json payload size, which was send back and forth between the website and the bot. However, I have also split up the requests per route. The reason behind it is that you always see the newest data. Since I am not a web developer, I don't know if that brings longer loading times or not. In my tests it looked fined. If you have any issues, please let me know!

Some Side Notes​

Sadly I am not nearly done with the website. There are still a lot of things missing. I will try to add them over time. But I wanted to get the new website out asap, since it is a lot better than the old one.

• The website is still not fully finished. I mainly migrated everything to the new API and page layout, so there are still some commands missing.
• I planned to make the website open source, but I am having some issues with secrets. If someone really wants to contribute, please let me know and I will try to get it done asap.
• A lot of features (like event creation, event sign ups, creating templates, ...) are still missing. I will add them over time. Just need to find the time for it.

Payment System Changes​

PayPal is gone, FastSpring is here!

• I switched away from PayPal to FastSpring for one time payments. This was needed for various reasons, unfortunately. Since FastSpring automatically applies VAT, all prices are, depending on your country, a bit higher than before.
• FastSpring also has higher fees than PayPal, so I had to increase the price for the 1 Month Premium Membership a bit. All other prices stayed the same.
• In addition I added the option to try out the Premium membership for 1 week for free. This can be done via Patreon!

Overlapping Events​

Added a new feature that allows you to get notified if you create an event that overlaps with another event.

• New command toggle event_create_overlap_note

If enabled, you will get a note if you create an event that overlaps with another event. You can then decide if you want to create the event or change the start/end time.

Bugfixes​

• Fixed an issue that confirming a user with multiple sign ups did not work.

• Fixed an issue that creating an event with now as start time did not create a voice channel.

• Fixed an issue that the caused the help command to not work on some shards.

• Fixed an issue that event user notify did not let you know about missing permissions if the send message permission was missing.

• Fixed an issue that log messages appeared in the wrong channel due to a rare race condition.

• Only send "Max length of event xxx reached" on user sign up.
  The message that either the whole event message length, or a field length is reached was printed both on sign up and sign up. Furthermore, it was also printed on:

  • Event reload

  • Channel change

  • If a user got removed from the server / lost it's user role

  • Event close

  • Event edit

  • Confirming a user

  • ...

    So everything that touches the event message itself.

    This is now changed. Only sign up actions trigger the message if a limit is reached.

• Fix that "Max length of event xxx reached" is only printed on sign up on the right field. Only print the "Max length of event ..." message if the user signed up for a field that is actually limited. Before:

  • "Attending" field was full

  • User signed up with "Not attending"

  • User got message that max length is reached.

    This no longer happens

• Fixed issue that a "user signed up" log message was triggered if a user signed up to a role/emoji that has a sign up limit that is reached. This means that the user wasn't signed up, but the log messages suggested that the user was signed up.

Improvements​

• If you already have an event create notification you now get an error on using event_create_notification add.
• Renamed toggle account_names to toggle at_mention to make it more clear that the command toggles between @username and username.

This update brings 2 new quality of life features, some improvements and bugfixes!

• Features
  • Notification Rewrite
  • Relative Date/Time Support
• Bugfixes
• Improvements
• Other Changes

Features​

Notification Rewrite​

Customization​

• event_start_notification now allows full* customization for Premium users.
• event user notify also allows full* customization now, but für all users (as before).

You can both edit the Text Message field of a Discord message (this is where you can for example ping @user) and the Embed Message (in here you can use for example links with [link name](link url))

* Sadly only the Embed Description is currently up for customization. The Embed Title isn't enabled yet due to a Discord limitation for which I need to find a workaround.

New Commands​

• event_start_notification edit message to edit the notifications message
• event_start_notification edit notify_type to edit the notifications notify_type
• event_start_notification list to list all entries

Premium​

Premium users can now use more than 1 event_start_notification per server. This allows you to send different messages at "1 day" before event start and another one "5 minutes" before the event starts. Or you can send a message once to users that aren't signed up yet and another message to users that are signed up.

Relative Date/Time Support​

Till now you needed to enter a full date/time when creating an event. Like 2023-05-14 20:00.

NOW you can use stuff like tomorrow 20:00 or today 1h!

So what are valid options and how to they resolve?

• now => creates an event with the date of today and a start/end time of now
• today => creates an event with the date of today and no start/end time
• tomorrow => creates an event with the date of tomorrow and no start/end time

Combine! You can combine now, today and tomorrow with either a precise time (like 08:00pm) or a relative time (1h 10m) Examples:

• today 20:30 will resolve in the date of today and the start/end time of 20:30
• today 1d 30m will resolve to the date of tomorrow (1d) and the time of you executing the command + 30 minutes. So this would actually be the same as tomorrow 30m.

Read more about that feature here.

Bugfixes​

• Fixed issue that a "channel" notification (former "ping" message) got printed with "Pinged 0 users" if no users met the required sign up state.
• Fixed issue that the wrong event start time was shown in the notification message footer.
• Fixed issue that events do not get created via a repeating event entry, once the repeating event entry was deactivated once. Even after setting it to active again.
• Fixed issue that events with an end time in the past did not get deleted immediately if the event_deletion_time was over. Instead they got deleted with a delay of a few minutes. This is currently mainly caused by repeating event entries if they get activated again. On activate the bot creates all missed events. Since the deletion does not happen instantly, it causes a lot of confusion and also unnecessary API calls (like sending notification messages, creating and deleting voice channels, ...). I am working on a solution that the bot will skip those events in general. But till than, this is a workaround.
• You now get a "missing permission" error if the bot misses access to the channel during the event user notify command.
• If the signup_template had invalid limit fields (due to manual edit of the .json file), so sign ups were possible. This is now fixed by ignoring invalid fields and using default values for missing fields.
• Fixed an issue that Discord server with a timzone in UTC+2 (or higher) were not possible to create events within the new future (next few hours).

Improvements​

• Most missing permission message now have a link directly to the doc page with additional information about the permission required.

Other Changes​

• Related to the Notification Rewrite, the notification types were renamed from "ping" and "message" to "Channel" and "DM" because the "ping" message got always printed to a server channel, while the "message" was always a DM to a user.

• Added the fields:

  • ${signup_state} resolves to "sigend up", "not sigend up" or "confirmed", depending on the choosen state.
  • ${maching_users} resolves to all users that match the state and mentions (@user) them.

  Those fields can be used with the different notification commands. Read here for more information.

This update contains a few bugfixes that came up since v4.1.0.

• Bugfixes

Bugfixes​

• Fixed issue that sign ups did not work correctly if emoji_behavior 2 or 3 was selected.
• Fixed issue that the sign_up_count at the bottom of the event no longer showed the sign up limits.
• Fixed issue that the bot did not handle sign ups correctly that were missed during a downtime.
• The ping message from event user notify now correctly links to the event message.
• If at least one user could not be reached with the event user notify, the command issuer now again gets an info message with the users not reached.

This is a rather small update since I had my issues with the PayPal API, not being a web dev and there was a lot going on in RL.

The update contains 4 new features, some improvements and bugfixes!

• Features
  • Customizable Signup Count Line
  • Event Creation Notification
  • New Repeating Event Interval
  • Logging
  • Patreon/Premium Rewrite
• Bugfixes
• Improvements
• Other Changes

Features​

Customizable Signup Count Line​

At the bottom of the event there is a line that shows the current amount of sign ups (Sign ups: Total: 0 - Role: 0 - Status: 0). This line is now customizable!

• Removed the command toggle sign_up_count
• Added the commands:
  • sign_up_count set
  • sign_up_count get

With the new set command you can now choose between:

• Not displaying that field at all
• Displaying sign ups as total (If the same user is signed up twice, the count is incremented twice)
• Displaying the sign ups as unique count (If the same user is signed up twice, the counter is incremented only once)
• Or display both options

Event Creation Notification​

This new feature is a channel setting. It allows you to set:

• A channel to which a message is posted on event creation.
• A normal text message where you can add pings and stuff.
• An embed message for the nicer look and possibility to add links.

Added 4 new commands:

• event_create_notification add
• event_create_notification remove
• event_create_notification edit channel
• event_create_notification edit message

Documentation about this feature can be found here.

New Repeating Event Interval (Premium)​

Added a new custom interval for repeating events with which you can let the event repeat every Monday/Tuesday/... in a week.

There isn't really much to say. For an example you can check out the repeating event documentation.

Logging (Premium)​

Raid Organizer now has the ability to send log messages on certain triggers. The triggers are:

• Event creation
• Event edit
• Event closed
• Event opened
• Event deleted
• User signed up
• User signed off

The new commands to manage the log config are:

• logging setup => Setup the channel to which the events should be logged
• logging edit => Edits the settings
• logging get => Returns the logging config
• logging remove => Removes the logging config. After this nothing will be logged anymore.

Documentation about this feature can be found here.

Patreon/Premium Rewrite (Part 2)​

Find part 1 here.

Patreon​

The Patreon migration is now complete which means:

• The prices did change
• The currency changed from $ to €
• There is an annual payment option. If you select it, you get a discount.
• New Patrons are now charged on the day they join. Always. Before they where charged on the join date and than on every 1st of a month. That sometimes lead to being charged twice within a few days.

PayPal​

The bot now finally uses the PayPal API. Till now I had to manually handle payments via PayPal :/

This means:

• The PayPal donation buttons are gone.
• If you now want to increase your limits or buy Premium you have to:
  • Go to the webpage
  • Log in with your Discord account
  • Select Interactive
  • Choose your guild
  • Head over to the PayPal tab
  • Select the item you want to buy
    note

    PayPal needs about ~10 minutes to verify the payment. When everything is processed, the bot will send you and the server owner a confirmation DM.

Part 3?

I have a few more things I want to add. Those are in the pipeline but I have no specific date / milestone for them ATM.

Bugfixes​

• Fixed the description of the template_id parameter in the /event_template create command. It now correctly shows that an event template id is requested.
• Fixed issue that you could not edit Premium parameters with the event_template edit command.
• Fixed issue that the event_voice remove command did not work.
• Fixed issue that users that got confirmed via the event user confirm command did not receive a notification.
• Fixed issue that events created from an repeating entry got posted in english, even if another language was set.
• Fixed issue that servers without Premium were able to use Premium fields (like image, footer, etc.) when using the event_template create command.
• Fixed issue that voice channels did sometimes not get deleted correctly after event end.
• Fixed issue that voice channels where never deleted if /toggle event_closure was off.
• Fixed issue that the command get_hidden_users did return nothing if "signup numbers" where enabled.
• The event user notify command now prints an error if the passed event got deleted in the meantime.
• channel config now shows the correct value of the toggle discord_event state.

Improvements​

• The template parameter in the event create commands now have the description "Signup template"

Other Changes​

• Allow Discord Thread channels in Forums to become event channels (/channel setup command)

• Added a note for those channels that the /thread command won't work in Thread channels.

• Added the fields:

  • ${role_unique_count}
  • ${status_unique_count}
  • ${total_unique_count}

  Those fields can be used with the different notification commands and will be replaced with the unique counts. Read here for more information.

  • ${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
  • ${ping_user_role} resolves to a mention of the set user role

This update contains a few bugfixes that came up since v4.0.1.

• Bugfixes

Bugfixes​

• Updated the Discord Library to fix a bug that the "Discord event" creation did not work
• Fixed a bug that broke repeating event creation if the event channel got deleted between 2 repeating event creations.
• Fixed an issue that the channel setup command did work in threads which leaded to some funny behaviors.
• Fixed an issue that new Patreons sometimes did not get keys right away.

This update contains a few bugfixes that came up since v4.0.0.

• Bugfixes
• Other Changes

Bugfixes​

• Catch an issue that repeating events could be created with a start/end time but no timezone set. That resulted in the bot not being able to convert it properly
• Print an error message if the days in advance value, when creating a repeating event, is not an integer.
• Fixed an issue that channel remove did not print a success message on success.

Other Changes​

I have added a bit more logging to find out why:

• Sometimes new Patreons do not automatically get keys assigned.
• Discord Events creation does not work for some servers.

This update contains 2 new features, some improvements and bugfixes!

• Features
  • Scheduled Events
  • Voice Channel creation
  • Patreon/Premium rewrite
• Breaking Changes
• Bugfixes
• Improvements
• Other Changes

Features​

Scheduled/Discord Events​

This new feature allows you to automatically create Discord event on event creation!

In the gif below you see me creating an event with a start and end time + an image.

Some more notes:

• You will be able to en/disable the creation of those events with the new command /toggle discord_events. It is off by default. If on event creations will also create Discord events.
  info

  The bot needs additional permissions for this feature. You will find more information in the /permission command.

• Scheduled events are deleted on event delete.
• They are linked with the voice channel (if set and the voice channel is already created).
• If you edit the event, the scheduled event is also edited.
• The image from event create is also used for the scheduled event.

Voice Channels (Premium)​

In the gif below you see me setting up a voice config with the following settings:

• Name of the voice channel will be created dynamically by the event title and the event date.
• The voice channel will be created 5 minutes before the event start time is reached
• The category in which the voice channel is created is called Voice Channels

Voice Channel behaviour:

• Voice channels are only created if the event has a start time.
• Voice channels get removed:
  • After the event end time is reached and no user is in the channel.
  • If a user is in the channel after the end time is reached, the voice channel will be removed right after the last user leaves the channel.
  • If the event has no end time, the voice channel will be removed when the last user leaves the channel and the start time is in the past.
  • If an event gets deleted/closed and no user is in the channel, the channel will also be removed.
  • If a user is in the channel during deletion, the channel will be removed right after the last user leaves the channel.
• If the corresponding event gets edited (example the title changed), the voice channel will also change its name (if the ${event_title} variable was used).

Patreon/Premium Rewrite (Part 1)​

The first Part of the Patreon/Premium rewrite is live now.

This includes:

• All features are now the same for all Patreon/Premium types.
  This means:
  • Premium/Patreon Bronze now have also unlimited channels/templates and stuff.
  • And all other features listed here.
• Patreon will now change to a key based system.
  When you become a Patreon, you get a key. This key can be set to a Discord Server which than has Premium active.

Part 2?
Part 2 will contain:

• A PayPal rewrite to make the usage easier
• Buy Premium via PayPal
• Add a lifetime Premium membership
• And more stuff!

Breaking Changes​

• The template command was renamed to signup_template to reduce confusion with event_templates.
  More Information

  Full list of changed commands:

  • /template create => /signup_template create
  • /template remove => /signup_template remove
  • /template edit => /signup_template edit
  • /template get => /signup_template get
  • /template list => /signup_template list
  • /default_template set => /default_signup_template set

Bugfixes​

• Event delete now correctly updates the upcoming message.
• Fixed some issues where the "missing permission" message wasn't printed on error.
• On event edit the length of the title, text, description and footer text is now checked correctly to prevent hitting Discord message limit.
• Fixed a race condition in the communication between the bot shards that could lead to the bot not responding during DM messages.
• You now get an error message telling you to set a timezone if your server does not have a timezone set and you create an event with a start time.
• Removing the user role from a user, no also correctly removes the user from the thread.
• Using the command event user signup/signoff now correctly adds/removes the user from the thread.
• The event start notification now gets always triggered correctly if you create an event that has a start time within the next few minutes.
• language set now shows english correctly at 100%

Improvements​

• If you remove a signup_template that is in use, you get a warning. This warning now:
  • Uses Discord buttons instead of emojis
  • Is ephemeral (only visible to the user that uses the command)
• If you exchange Gears for goodies, you will now see them right away active on your server. (Before it took some minutes to update the settings)
• If you enter a date to the creation time(repeating event creation), you now get an error message that tells you "Only pass a time".
• Patreon/Premium loose no longer deletes channels/repeating events, etc. over the limit.
  More Information

  Before this update, if you lost your Patreon/Premium membership, all limits were enforced and everything above the limits got removed from the database.
  This caused the issue, that if you get Patreon/Premium again, you would need to set those channels up again.
  Now they are just "deactivated". This means:
  

  • Sign up in channels above the limit are no longer possible.
  • You can not create events in there.
  • etc.

  If you reactivate your Patreon/Premium membership, they are also activated again
• language set now hides all language below 10% translation progress
• During the initial DM setup, the bot now is case insensitive to the "channel name" and "channel type" input to make the setup easier.

Other Changes​

• New channels now have the thread creation off by default.
  More Information

  I noticed that most people are not using it, find it irritating or disable it anyway.
• The text field (during event create) now has a maximum length of 2000 (instead of 80).
• The text field now also supports \n to make a new line.
• The notify/event start notification user limit for non Premium users got decreased from 100 to 25.
  More Information

  Sending that many messages is heavy on the Discord API and slows down the bot.
• Removed the command display_timezone because all times are now displayed with Discord timestamps
• Removed the commands black/whitelist bot/hook because the new slash commands can not be triggered by other bots anyway.

This update brings 2 new quality of life features, some improvements and bugfixes!

• Fixes

Fixes:​

• Fixed an issue that if the automatic notification message was sent at event start, the notification string was a bit broken.
• Fixed a bug that the export_event command did not work in some cases.
• Fixed a bug that the date of the next event creation was wrong when creating a repeating event.
• Fixed an issue that the bot silently aborted when a date instead of a creation time is entered during the create_event command.
• Fixed a rare issue that during the create_event/create_repeating_event command triggered an abort when entering a date.

This update brings 2 new quality of life features, some improvements and bugfixes!

• General
• New Stuff
• Fixes
• Improvements

General:​

With the update v2.3.0 I did a rework of how the bot handles time stuff. Since the old time implementation was my first time working with different timezones, daylight saving time, ..., it was a bit messy. Also it had a few small bugs and issues. This should now be more clean and should allow me to add more time related features in the future. Anyhow, since that included some big code change (how events and repeating events are working) I was happy to have some beta testers! That hopefully makes this release more secure :)

New stuff:​

Repeating Event Rework​

With this rework you can now:

• create_repeating_event now lets you choose if you want to create the repeating event via a create --advanced string (one line) or if you want to get guided through the creation.
• Use the edit_repeating_event like the edit_event command. This means, instead of using the create --advanced string, you can now edit each field parameter on it's own. This makes it way more user friendly.

Closing Events​

You can now close events. Closed events will not allow further sign ups!

New commands:

• toggle_event_closure => On by default. If on, events will get closed automatically after the event start time is reached. If an event does not have a start time, it will be closed at midnight local time.
• open_event => Opens a closed event. However, if toggle_event_closure is true, the event will get closed again after some time!
• close_event => Closes an event manually.
• set_event_closed_color => Sets the color for events that are closed for sign ups.
• set_event_close_time => This command sets the time how long before the event start an event should get closed by the bot.

Export Events​

New feature to export events to a given channel. Both manually and automatically!

New commands:

• set_export_channel => This command sets a channel where events will get exported.
• export_event => Exports a given event. Those exported events are not effected by the event deletion time. This is some kind of "fire and forget". The bot takes the current state of the given event, posts it to a given channel and than forgets about that command.
• toggle_export_event_on_close => If true than events will automatically get exported to the given channel when the event close time is reached.

Display Event Start Time In Local Time​

Since discord messages are the same for all users, there is no way to display different start times for different users if they are in different timezones. However, the footer of a message allows that. So I added a new command:

• toggle_footer_time => Show the event start time in the footer of the event message

Automatic Notifications​

Yes, there already is a notify command. However, that one needs a manuall trigger. The new added notification system will automatically send a message X (days, hours, minutes) before the start time is reached. New commands:

• add_event_start_notification => Adds a new notification entry that an event is about to start. (Currently only one entry is supported. May increase this in the future!)
• edit_event_start_notification => Edits a notification entry.
• remove_event_start_notification => Removes a notification entry.

Sign Up/Off Users​

Added new commands to sign up/off users to a given event:

• signup_user => Signs up a giver user (or multple users) to a given event.
• signoff_user=> Signs off a given user (or multiple users) from a given event.

Users that are signed up/off will receive a notification message from that bot.

Fixes:​

• Fixed a bug that the confirm command dit not work if the user was signed up with a custom emoji and was signed up multiple times in the event.

Improvements​

• You now receive a DM from the bot if you try to sign up for an event but you do not have the user role.

This update brings 2 new quality of life features, some improvements and bugfixes!

• General:
• Fixes:
• New stuff:

General:​

Another small bugfix update to fix the last outstanding issues from the v2.2.0 release.

Fixes:​

• Fixed an issue that list_templates has thrown an error on some server.
• Fixed an issue that you did not receive a "missing permission to execute command" error if your input for the command was too long (like a too long description for an event).
• Fixed an issue that a too long event description did not only throw an error that the description was too long.. It also had thrown a "missing permission" message which was printed to the command executor in a DM. The message was misleading because it told you that the bot was missing some read/write/etc permissions.
• Fixed an issue that edit_template <id> emojis did not pars whitespace characters correct. That resulted in the bot sometimes not being able to correctly assign emojis.
• Fixed some (actually a lot!) spelling mistakes. Thanks to TheOmega#8160
• Fixed an issue that newly created event/lfg channels had the wrong sign up number behavior.
• Fixed an issue that the user sign up number wasn't reset correctly if the behavior was selected that sign up numbers reset on role/status change.

New stuff:​

• Added new command set_confirm_behavior. This command lets you choose if you want the confirm emoji next to the user, confirmed users in a separate column or both.

This update brings 2 new quality of life features, some improvements and bugfixes!

• General
• Fixes

General:​

This is a small bugfix update to fix the most critical bugs.

Fixes:​

• Fixed an issue that the edit_event and reload_event command showed that no help is available on wrong usage :/
• Fixed an issue where the notify command went on cooldown even if the command failed (due to invalid input or something else). The cooldown now only applies if the command was executed correctly.
• Fixed an issue that the notify command did send the cooldown message as a DM.
• Fixed an issue that you did not receive an error message if the command set_sign_up_number_behavior was executed with just a single digit (like 1 instead of 11)
• Fixed an issue that multi user sign up did not work if you used a custom emoji as a sub role emoji. Instead of singing the user off again when using it twice, it signed up the user 2 times with the same emoji.
• Fixed an issue that max_sign_ups_per_user 0 resulted in only allow 1 sign up for a user. Since 0 should mean infinitely many sign ups, this was a bug :D

This update brings 2 new quality of life features, some improvements and bugfixes!

• General
• New stuff
• Fixes
• Improvements

General:​

With update v2.2.0 I wanted to tackle some long outstanding requests and I wanted to change how the bot works with time...\ Long story short: I did not manage to do the time rework yet, but it will be my next milestone!\ Now, lets come to the fun part, the new stuff :)

New stuff:​

Added a "moderator"-role​

Users with this role have the same rights (to the bot) as users that are server owner or have administrator permissions.

This was done because:

• Server owners often do not have the knowledge or the time to deal with the bot setup
• And giving a member administrator permissions also brings some risk with it.

Changes:

• Now you can use the new command set_moderator_role to give users in that role all privileges to use the bot!
• The get_server_config command now also shows the moderator role.
• The get_my_guilds command now displays information about the moderator role (if you have the moderator role).

Add new command: "notify"​

notify is a new command that allows you to ping, message (or both) users with the user role that either are signed up or are not signed up for a specific event.

The syntax is: !notify <notify type> <event id> <user status> [message]

• <notify type> has to be ping, message or ping&message
• <event id> is the id of the event
• <user status> is either attending to notify all attending users or nattending to notify all not attending users
• [message] is the optional message that will be send to all users

Notes:

• This command has a cooldown of 10 minutes to avoid spam and please the discord API :D
• It also has a limit of 100 users. This could be an issue if you run @everyone as a user-role and try to reach all not attending users! However, there is no limit for Premium servers and servers with a Patreon subscription.

Allow multiple sign ups!​

This update brings the long requested feature to allow multiple sign ups for one user!\ During the template creation you can now specify the limit how often a specific user can be signed up on a given event.

This needed some rework of basic functions:

• Before you could only sign off by using a remove emoji. Now the remove emoji removes all sign ups of a user.
• Before you could only sign up by pressing an emoji. Now emojis are "toggle buttons", which means they sign you up and off if you press them twice!
• Having the same user signed up multiple times in an event also messes with the sign up numbers, so I have changed the behavior of them. (read more about it below!)
• The late emoji adds the +5 minutes to all sign ups of the user.
• The confirm command now needs to know for which role you want to confirm a user that is signed up multiple times. Now, if a user has signed up multiple times, the bot asks you for which role you want to confirm the given user.
• Confirmed users now have a "check" emoji next to their role. Before they were displayed separately from other users.

Changed how the command "set_sign_up_number_behavior" works​

Till now you could choose if you want to

• (0) not reset sign up numbers on emoji change
• (1) reset the sign up numbers on emoji change between role and status emojis
• (2) reset them on every sign up

since now a user can have multiple sign ups we have new behaviors that needs to add up to the already existing one. Those new behaviors are:

• (1) Count every sign up of a given user. This results in a user having 2 different numbers if the user signed up twice. Example image
• (2) Only count the first sign up. Example image

To make those work together, the already existing behaviors are now the lower digit (example: x2 would reset the number on every sign up) and the new added behaviors are the tens (example 1x would count every sign up of a given user with a new number).\ The examples above would result in the command set_sign_up_number_behavior 12.

Added new command: Beta​

Added a new beta command. This command displays some basic information about how to join the beta crew.

Fixes:​

• Fixed an issue that translated messages got changed back to english. For example: If you have your language set to x and create an event, the event will be in language x. If now a user signs up to the event, the event message changed back to english.
• Fixed an issue that sometimes the list_repeating_events had some parsing issues and than the message got messed up.
• Fixed an issue that too long descriptions in repeating events broke the list_repeating_events message.
• Fixed an issue that edit_event did not send you an error message of wrong usage.
• Fixed a translation issue which resulted in showing code instead of the stuff that needs to be translated :D
• Fixed an issue that edit_template displayed None as prefix on error.

Improvements​

• Improved and cleaned up the command permission checks! You now receive a more detailed error if you lack permissions to use a command.
• Moved the set_date_format from the Channel to the Server command group since it is a server wide setting.
• Renamed the commands edit to edit_event and reload to reload_event. edit and reload will stay as aliases but the new default names make it more clear what the command does.
• Fixed some spelling mistakes.

This update brings 2 new quality of life features, some improvements and bugfixes!

• Fixes
• Improvements

Fixes:​

• Fixed an issue that the list_repeating_events command did not work for some/most users.
• Fixed the issue that the bot status message for the version had 2 "v" instead of one.
• Fixed an issue that the bot did not send you a message if you used the setup_channel command but your limit was exceeded.
• Fixed an issue that the premium command did not work in rare cases.

Improvements:​

• The bot now correctly asks for a number if emoji behavior 3 is selected. Before the bot asked for an emoji, which is only correct for behavior 2.

This update brings 2 new quality of life features, some improvements and bugfixes!

• General
• Fixes

General:​

This is a small bugfix update to fix the most critical bugs.

Fixes:​

• Fixed an issue that the interactive create command and entering only --advanced as a title confused the heck out of the bot. It than tried to create an event with an empty title which is against Discord rules :/ The bot will now print you an info message if no title is set!
• Fixed an issue that animated emojis did not work anymore... again -.-
• Fixed an issue that might has resulted in the bot not being able to send you a DM if you loose Premium membership.
• Fixed an issue that the step count on setup_channel was off which resulted being in step 4 out of 3 ¯\_(ツ)_/¯
• Fixed an issue that some strange strings were printed during the setup_channel command. The bot tried to speak a strange language.
• Fixed an issue that the limits and set_event_deletion_time command did not work anymore for some users.
• Fixed an issue that the statistics command did not update all fields properly.
• Fixed an issue that the statistics command did not get deleted if posted in a guild. It now has a deletion timer of 60 sec. The message still does not get deleted if the command is triggered via DM.

This update brings 2 new quality of life features, some improvements and bugfixes!

• General
• New stuff
• Fixes
• Improvements

General:​

Update v2.1.0 is here and with it comes the translation of the bot + a few small things! Although the patch notes look short, making the bot ready for translation was a lot of work ^^. The translation process is still in progress! So if you want to help with the translation, hop over to our Discord server and check out the translation section! :)

New stuff:​

• The bot is now ready to support multiple languages! It's now your turn (beloved community :) ) to make the bot speak other languages than english. The commands to do this are:

  • set_language and
  • get_language

  Keep in mind, the translation process is still in progress!

• Added command statistics. This command returns you some general information and statistics about the bot!

Fixes:​

• Fixed an issue that the help <command> command wasn't working for a few commands :/
• Fixed an issue that abort messages weren't printed correctly if your server wasn't running on the right shard.
• Fix an issue that the change_channel command did not work proper on veeeeery old events. (looks like some users are creating events and than keep changing the date.. like for ever :P)
• Fixed an issue that events with no title crashed during the event creation. Still dunno how you guys managed to create an event without a title... So if you know, let me know :D

Improvements​

• The bot now runs on Python 3.9! This was needed to make the translation work but also will be needed in the future to support slash commands and so on :)
• The premium command now is also available in non event channels + DM's. A general cleanup of this mess will be tackled in the next update.

This update brings 2 new quality of life features, some improvements and bugfixes!

• Fixes
• Improvements

Fixes:​

• Fixed an issue that for some users/guilds the export_template command did not work.
• The bot now again prints the right "timeout abort" message if the an interactive command (like create_template) times out.
• Fixed an issue that sometimes the google link did not work proper. This should now finally be fixed once and for all! :)
• Fixed an issue that the bot sometimes did not recognize new patreon members on its own.
• Fixed an issue that role and status emojis sometimes did not work if they were custom emojis.
• Template limits now work proper if you have a "+" in the field name. Example <emoji>,role,Tank + Offtank.
• Fixed a problem that animated emojis in custom templates sometimes did not sign you up if you used the emoji behavior 2.
• Fixed an issue that the "remove" emoji did not remove you from the event, if it was pressed during a bot downtime.
• Fixed an issue that "guild owners" and "administrators" could not remove events from other users in an "lfg" channel.
• Fixed an issue that caused the bot to silently abort an event creation if you entered the first of a moth as a date and 00:00 as end time.
• Fixed an issue that repeating event creation got stuck.

Improvements​

• Add a note about adding emojis as a nitro member to the custom template "set icon" text. Before that note was only shown during the "emoji setup" process.
• Added a note that [ and ] are not allowed in the field name of an emoji. Example <emoji>,role,[tank] is not allowed!
• The bot now prints an info message if you react to an event but the template that was used for the event was deleted/modified.

This update brings 2 new quality of life features, some improvements and bugfixes!

• General
• Fixes
• New stuff
• Other Stuff

General:​

Hey guys and girls!

First of all, I am very sorry that it took soooo long for this update to come, but this update was a really huge challenge for me. Not just the programming but also with all the covid related stuff, huge work load at work and so on.. but its finally here! :)

So before we come to the "new stuff" (mostly some small fixes), I want to let you know on what I've worked. If you are not interested in the technical details, go ahead and skip to the fixes ;)

I guess most of you remember the pretty long bot downtime in the beginning of November (small side note, back than the bot was on 1200 server. Now it is on ~2100!). The downtime was related to some big discord API changes. Long story short: Before those changes the bot was able to retrieve all guilds on startup without any delay. Now the guilds are requested via hooks and there is a limit of 120 guilds each minute. That resulted in a huge increase of the bot restart time (back than 10 minutes).

Since the bot is growing constantly this wasn't really something that I could ignore and the only solution was/is using "different bots processes" instead of one. That is called sharding. Since I never did something like this before, I first thought that doing some "soft sharding" should be enough.. but I was wrong. So what I had to do was starting multiple instances/processes (shards) of the bot, giving each shard a rough amount of guilds to deal with. In theory this means; Before there was one instance running with 1200 guilds (10 minutes startup), now there are 2 instances running with each 600 guilds (startup 6 minutes).

So far, so good. Now the big problem hit me. Discord API is returning every DM on shard 0, no matter what. This means, if you execute a command on shard 1 (example create_template), shard 1 sends you a DM guiding you through the process of creating a template. However, your answer gets returned to shard 0. But shard 0 doesn't know anything about the fact that you want to create a template. It just sees a message (which most likely isn't a command) and throws it away.

This is where IPC (Inter Process Communication) joins the game. Again.. young and green as I am in this field.. I first thought "easy, let's find out all cases where a communication via DM is required and transfer them to shard 0" and I did that. Worked pretty well.. but soon I found out that there are a lot more cases where IPC is needed. To give you some examples: nearly all gear commands (because you might be in a guild in which the current shard isn't), getting the overall guild count, all commands on the webpage (webserver runs on one shard but you can handle all your guilds on all different shards there.), and a loooot more.

Since those changes were huge, I am happy that I have a hand full of beta testers (BTW: I will expand that. Maybe soonish? :) ). They didn't even noticed most of the bugs, but I saw them appearing in my log files and fixed them silently :P This leads me to my last point. I finally "got time" (actually, had to do it) to implement a better logging system :) It's still not perfect and I will improve it step by step, but it's already way better than what I had before.

Lastly, to give you a rough overview of how much I changed:

• I touched nearly every code file for this rewrite
• Touched about 10k lines of code

Such big changes pose a great risk of breaking a lot of stuff. However, those changes were needed and I will monitor the bot closely in the next days. If something is off, I am ready to role back to v1.6.0 or push a hotfix.

Fixes:​

• Fixed an issue that in rare cases the wrong patreon rank was applied.
• Fixed an issue where the bot resets premium features on a patreon server.
• You now get proper help when using the command show_sign_up_numbers with wrong parameters.
• You now get proper help when using the command blacklist_webhook with wrong parameters.
• If you used the create command wrong and your input was >1024 symbols, you did not receive an error message with what went wrong. This is now fixed.
• Fixed an issue where the template creation sometimes aborted silently if did not pass the whole message when editing sign up limits.
• Fixed an issue where sometimes the bot aborted silently on the setup_channel when printing the existing roles on the server.
• Fixed an issue that did not allow you to edit the emoji behavior of a custom template.
• Fixed an issue during edit_template where the bot asked you what emoji "you want to change" even if you selected that you want to "add an emoji".
• Fixed an issue where creating a template failed if an invalid color is used by the template.
• Fixed an issue at create_template where the bot allowed you to enter emoji,role, which resulted in an empty name for the role. The bot now informs you that this is not allowed.
• Fixed an issue that import_template did not take into account the patreon limits of the role silver and above.
• Fixed some spelling mistakes

New stuff​

• The help command had a full rework. Hope you like it :)
• footer_text now also is a valid argument for creating/editing an event. (before it was only footer_txt and ft)
• Add command get_template. This command returns you details about the passed template number.

Other stuff​

• The patreon message now also prints your patreon rank
• Fix/Improve the help of whitelist_webhook, blacklist_webhook and get_clean_mode

This update brings 2 new quality of life features, some improvements and bugfixes!

• Fixes
• New stuff
• Other stuff

Fixes:​

• Quick and dirty fix that the help command is working again. I plan a rework of the help command soon. For now I just reduced the amount of information on the category usage (example help organizer) to not hit the Discord limits.
• You now receive an info message if you forget a space between users when using the confirm or unconfirm command.
• Messages from a webhook now are correctly deleted when using a clean mode that should delete those messages.
• set_event_deletion_time now prints a correct error message if no number was passed.
• Reloading an event and changing the event channel now correctly recreates the "LFG" message (if the channel is an lfg channel and those messages are enabled)

New stuff​

• I now enabled sharding for the bot. This isn't really a new feature for you. It is more something that discord requires you to do when you reach a certain amount of servers. The reason why I am doing it now is that with sharding I can limit the restart time of the bot to 10 minutes.

Other stuff​

• The amount of gears needed to get premium (for 1 and 4 weeks) is cut in half. You now need 25 and 75 gears instead of 50 and 150. This means that you can keep up premium for your server now more easily by voting.

This update brings 2 new quality of life features, some improvements and bugfixes!

• Fixes
• New stuff

Fixes:​

• Using emojis of the type "late" and "rlate" will no longer increase the total sign up number (if you are not already signed up).
• Prevent users from being able to "sign up twice" which results in having the same user with the same emoji twice in an event.
• The success message on edit_template is now sent as a DM if the edit was done in a private window.
• The success message on import_template is now sent as a DM if the import was done in a private window.
• Removed the additional "<" and ">" in the "template overview" during a custom template creation.
• Fixed an issue where the "template overview" (during create_template) sometimes did not display the entered emojis + description correctly.
• Removed the break line (the one that is between "role" and "status" emojis) after "role" emojis if a template does not have "status" emojis.
• Fix that set_default_template sometimes did not send you a success message.
• Fix that the bot sometimes stopped responding on edit_template.
• Bot now correctly throws an error if the used emoji in an event isn't known to the bot (maybe got deleted).

New stuff​

• New command toggle_sign_up_count. This command toggles the line in the footer of the event that shows you the Total/Role/Status sign ups.

• Fixes

Fixes:​

• Fixed a bug that the bot sometimes went rampage on import_template.
• Fix that the bot really aborts on writing "abort" during import_template.
• Fix that if you enter multiple lines of emojis during the template setup, the bot sometimes could not handle it and saved a wrong input. Now (again) only the first line is saved.
• Fixed a bug that resulted in being unable to sign off if the bot has the "organizer role"
• Fixed a bug that if you used remove, late and rlate during template creation, the bot stopped messaging you and aborted the template creation.

• New Stuff
• Bugfixes
• Improvements
• Other Changes

Fixes:​

• You now receive a message if you try to confirm a user for an event and the template (that this event is using) got deleted.
• Fixed a bug that !setup_channel stopped working when you entered !channel to get a list of all available channels and your discord server channel list was too long to fit in one message.
• Fixed a bug that change_organizer and change_user sometimes did not return you an error message on failure.
• Fixed a bug that during "custom template creation" => "emoji setup" the following 2 lines resulted in different output:\ emoji, role , DD ,range\ emoji,role , DD,range
• Fixed a bug that during custom template creation the "example event" and especially the "break line" looked different than the actual event later on.

New stuff​

Ok, now to the good stuff! I did a (nearly) full rework of the custom template. Let's start!

New setting emoji behavior \ This setting allows you to use one of the following three modes:

1. Default behavior. All emojis that you used during template creation are reactions on the event message. This limits you up to 20 emojis. Example GIF
2. Have one emoji for each field name. If you click the emoji the bot will create a new message with the sub roles as reactions. This would allow you 20x20 emojis on a template. Example GIF
3. Have one emoji for each field name. If you click the emoji the bot will create a new message with the sub roles as numbers. This would (in theory) allow you up to 20x"infinite" emojis. Example GIF

Sign up limits \ You can now limit nearly everything (regarding sign ups) on an event.\ To do this, follow the instructions during the template creation process.\ If you have already an existing template, you just need to use the new edit_template command!

Edit a custom template \ New command edit_template This command allows you to edit a given template. Things that you can edit:

• emojis = emojis + their description *
• name = the name of the template
• icon = the icon of the template
• color = the color of the event message
• emoji_behavior = display behavior of the emojis *
• limits = sign up limits

Note: With * marked points are breaking changes. This means that if you edit one of those fields, all events that a currently using this template will stop working!

Sharing templates You can now share templates with other users! How?

• Use the new command export_template [nr] to get the template configuration for a given template. (use list_templates to get all available templates ;) )
• Use the command import_template and pass an exported template to the bot. The bot will parse the input and makes it available for your server!
• Head over to our discord server => #template-share to share and use templates! Please read the pinned message for more details.

Other stuff

• Added a command to get the current default template used in this channel => get_default_template

Improvements​

• Total sign up numbers are shown in the event footer (Over all total, total sign ups with role emojis, total sign up with status emojis)

Other stuff​

• Fixed some spelling mistakes
• !homepage now actually prints a link to the homepage.
• Lifted the "event channel only" restriction for a couple of commands. My aim is to do a rework on command restrictions "soonish".. but that is something a bit down the list The following commands are no longer restricted to an event channel: vote, paypal, patreon, create_template, remove_template, set_timezone, whitelist_bot, blacklist_bot, whitelist_webhook, blacklist_webhook, limits

• Fixes
• Known issues

Fixes:​

• create_template now again works as expected. Fixed a bug that the guide "how to enter an emoji" raised an exception.
• Fixed that editing a template did not work on some servers.
• On edit_template with the "emoji" or "emoji_behavior" option you now receive a warning if you have events that are using this template.
• Fixed a bug that the bot parsed animated emojis the wrong way which resulted in: Bot removed the reaction but did not sign up the user.

Known issues:​

• edit_template currently ignores repeating event entries that are using this template.
• If a user unconfirmed himself and the organizer messages on unconfirm is enabled, the user needs to press the emoji twice.
• Sometimes the user count on an event is off by one.

• New Stuff
• Bugfixes

Fixes:​

• Fix that show_sign_up_numbers 3 had some strange behavior and some users had the same sign up number.

New stuff:​

• New command get_server_config. This command returns basic configurations that are serverwide. For this command you need to have organizer role (or higher). This command is not limited to an event channel.
• New command get_channel_config. This command returns the configuration settings for the current channel. For this command you need to have organizer role (or higher).

We also did some minor improvements to the website

• Add loading indicator when you go to the guild selection
• Add some nerdy statistics about the bot
• Fixed an iOS display bug (Already a couple of days ago)
• And added a "scroll to the top" if you click a link in the footer

• New Stuff
• Bugfixes
• Improvements
• Other Changes

New stuff:​

• New command !limits. This command will return your current limits/limitations for the server. (Things like max event channels, max templates, etc.) This command can be used by server owners and administrators.
• New commands !whitelist_webhook and !blacklist_webhook. This commands allow you to whitelist a webhook. They are similar to !white/blacklist_bot. By default RaidOrganizer does not listen to webhooks. IMPORTANT: Since a webhook is not a real user, you can't give it permissions. This means every webhook on the whitelist has the organizer_role by default! This means a webhook has the same rights as users in the organizer_role which may be a security risk! So be careful with this function :) NOTE: To whitelist a webhook, the bot needs permissions to manage webhooks.
• Patreon (Bronze and above) and Premium Servers are now allowed to create repeating events that are created more than 7 days in advance. Anyway.. Keep in mind, if you create a repeating event with let's say !create --advanced -t "Repeating event" -date 2020-10-01 -days 30 -ct 12:00 it will create 5 events. The first one for 2020-10-01, one for 2020-10-08, ... till 2020-10-29. Because you want to have them created 30 days in advance ;)
• Reworked command toggle_sign_up_numbers. The command is now called show_sign_up_numbers and allow you to set them more individually. You can now:
  • Show them not at all
  • Show them on roles emojis only
  • Show them on status emojis only
  • Show them always
• New command set_sign_up_numbers_behavior. This command allows you change the behavior of the sign up numbers. By default the number of a user resets every time they switch between a "role" and a "status" emoji. Now you can select if you want to reset it every time, never or between "status" and "role" changes.
• New command get_hidden_users. In a hot fix a couple of days ago I fixed that events could break if the message gets too long. Now if events (or fields inside an event) get too long for discord, the bot cuts of the players name from the event but signs up the user. Users with the organizer role can now use this command to get all hidden users of event X in field Y that are not displayed because the message got too long.

Fixes:​

• Fix that you could use the change_channel command to change the channel to a voice channel. Since the bot isn't able to speak, I limited it to text channels ;)
• Fix that the sign up numbers did not reset on custom templates with a remove emoji
• Fix that some new lines on some devices broke the google calendar link.

Improvements:​

• The bot will now print you an info message if you create a repeating event but no event is created because the date of the first creation is in the future.
• Updated the !help of consume_gears. It still showed the old help info before the rework :(
• The bot will now listen in all channels to change_prefix (before the command was allowed only in event channels)

Other stuff:​

• admin_role is gone for good. I changed all appearance of admin_role to organizer_role. This was done because admin_role sounded a bit like the administrator permission you can give a role in discord. To avoid confusion and owners giving administrator rights to users that should not have those rights, I renamed it. I hope it's more clear now and improves the security a bit :) BTW: This means all commands that had "admin" in their names have now "organizer" instead. For example: change_admin now is change_organizer (don't worry, only change_admin and toggle_admin_unconfirmed_messages changed.^^)