Skip to main content

Create Sign Up Templates

Sign up templates define stuff like the sign up roles (emojis) and how often a user can sign up. Basically stuff that is more "game based" (How many players do you need?) and not "event based" (When does the event start?)

Create the Template​

To create a custom template, use the /signup_template create command.

Step 1: Name​

First the bot asks you for a name. This will help you to keep your templates organized. Example: 10 player raid, 20 player raid, 5 player dungeon or PvP Raid.

Step 2: Icon​

This icon is only for organizing, as well as the name.

Step 3: Emoji Behavior​

In this step you will select how you sign up with the emojis. There are 3 options:

  • One emoji for each role/sub role. (Max 20 emojis) - Example
  • One emoji for each role. Sub role selection happens after the main role is selected. (Max 20x20 emojis) - Example
  • One emoji for each role. Sub role selection happens via number input. - Example

Step 4: Add Emojis to Your Template​

In this step you will add emojis to the template. Actually, the bot will describe you in details how to do that. There isn't really much more to say.

Instead here is a picture of what value effects which part of the event message:

note

Special emojis (remove, late and rlate) do not have fields in the event message itself.

info

Every emoji can only be used once atm! If you need to have the same emoji twice, you currently need to upload it to Discord twice. This way the emoji has an other emoji ID.

Changing that is on my todo list, but it sadly isn't that easy. :(

Step 5: Add Sign Up Limits​

In this step you can configure all sign up limits. And if I say all, I mean all!

You can:

  • Set the total amount of users that can sign up
  • Set the total amount of sign ups with the role emoji
  • Set the total amount of sign ups with the status emoji
  • Set how often a user can be signed up to the same event
  • Set the limit of every role field main emoji/category
  • Set the limit of every role field sub emoji/category

Just follow the instructions of the bot: Copy & Paste the whole message and adjust the number in between [ and ].

Step 6: Set the Color of the Event Message​

The color you set here will be the stripe on the left side of the event message (black in the picture above). The color needs to be added in hexadecimal. Just google color code in hex or use this link.

Done!​

Thats it. Your template is created and ready to use! You can either use the /event create command and pass the template with the template option, or you can set it as default with /default_template set.

Notes​

Discord Message Limits And Custom Emojis​

Raid Organizer is using so called embeds for event messages. An embed has an overall message length limit of 6000 characters. However, each field inside that embed has a limit of 1024 characters.

note

A field is one column where the user names are displayed. For example DD would be one, Maybe would be another one.

With Default Emojis​

If we now say that the average username has 10 characters, ~75 users would fit in one field. That usually is enough.

note

I went with 75 because standard emojis have a length of 1, plus one space for formatting, plus the possibility of showing the sign up number (3) adds a 5 to the name length.

With Custom Emojis​

If we now use custom emojis instead of default emojis, things look different. A custom emoji has the length of the emoji name, the emoji id + formatting payload.

  • The emoji id is either 18 or 19 digits long.
  • Name is custom, so lets say 5.
  • Formatting is either 4 or 5, depending on animated or not.

Which brings us to a length of ~28. Only for the emoji!

If we now add the 10 characters for the average user name, we can see that only ~26 users (instead of 70) are able to sign up to one field.

Learning?​

If you are managing a huge guild with a lot of sign ups, better use default emojis. If you can't, try to keep the emoji names as short as possible (maybe only 1 character).

What If I Can't?​

Don't worry! If the field message length is reached, the sign up will not be lost. You can always use /event user get_hidden_users to get all sign ups.