General Usage

The main way to interact with OpenQOTD is using Slash Commands.
OpenQOTD also only acts once the configuration has been initialized, otherwise it does nothing.

Configuration

OpenQOTD must be configured initially using /config initialize.
Afterwards, /config set and /config reset can be used to set the config, and /config get can be used to view it.

/config can only be run by users with the "Administrator" server permission.

Variables

The following config variables can be set using /config initialize or /config set:
Required fields are marked with "field", and default values are shown using "value".

• basic_role: This is the role that is required to run non-administrative commands, which includes:
  • /suggest (if suggestions are enabled)
  • /leaderboard
  • /topic
  • /sentquestions
  This is set to everyone by default. That means, if this variable is unset, everyone in your server is able to run these commands.
• admin_role: This is the role that is required to run administrative and potentially destructive commands, which includes:
  • /questions
  • /suggestions
  • /presets
  • /trigger
  The "Administrator" server permission overrides this role, and anyone with this permission can run every command regardless of what roles they have.
  

  ⚠️ Warning: While people without this role cannot run /suggestions, they can accept or deny suggestions using the buttons of the messages, so make sure to have your suggestions_channel set to a channel that is only viewable by people you trust!
  It's recommended to set it to a staff-only channel, and it can also be within a thread, to make it easier for organization purposes.

• qotd_channel: This is the channel that QOTDs are sent to, which includes the daily QOTD and the QOTDs that are triggered manually using /trigger.
• qotd_ping_role: This is the role that gets pinged when a QOTD is sent manually or using /trigger, even if it is a preset or there is no QOTD available.
  If this variable is unset, no role is pinged.
• enable_automatic_qotdtrue: Determines whether the QOTD is sent automatically every day at the set time.
  If this variable is set to false, the QOTD has to be triggered manually using /trigger.
• enable_qotd_pin_messagetrue: Determines whether the old QOTD, if existant and pinned, is unpinned and the new QOTD is pinned automatically after it is sent.
• enable_qotd_create_threadfalse: Determines whether to create a thread for the QOTD when it is sent, with the auto-archive duration being 24 hours.
• enable_qotd_automatic_presetstrue: Determines whether Presets are sent if there are no custom questions available.
  See Presets for more information.
• enable_qotd_unavailable_messagetrue: Determines whether a message is sent if there are no QOTDs available, which happens if there are no custom questions available and presets are disabled or exhausted.
  
• qotd_time_hour_utc & qotd_time_minute_utc: The hour and minute at which the QOTDs are sent (if enable_automatic_qotd is enabled), in UTC time.
  The hour must be between 0 and 23, and the minute must be between 0 and 59.
  For example, if you want the QOTD to be sent at 3:47 PM UTC, you would set qotd_time_hour_utc to 15 and qotd_time_minute_utc to 47.
  You can use this tool to convert your local time to UTC, and keep in mind that it might change due to daylight saving time.
• enable_suggestionstrue: Determines whether suggestions are enabled.
  If suggestions are disabled, the /suggest and /qotd commands are not available.
• suggestions_channel: The channel where new suggestions are sent to, with buttons to accept/deny them.
  If this variable is unset, suggestions are not sent anywhere and can only be viewed using /suggestions.
  See Suggestions for more information.
  ⚠️ Warning: Make sure to have this set to a channel that is only viewable by people you trust, as anyone can accept or deny suggestions using the buttons of the messages!
  It is recommended to use this if you have suggestions enabled, as it makes them much easier to manage.
• suggestions_ping_role: The role that gets pinged alongside with the message in the suggestions_channel when a new suggestion is received.
  If this variable is unset, no role is pinged.
• notices_levelAll: Notices are messages that are sent alongside QOTDs, which are written by the developer and are used to inform users about updates, changes, suggestions and thelike.
  The following options are available:
  • All: All notices are sent. Keep in mind that some of these notices may include encouraging users to join the community server, donate, contribute, or similar. Consider keeping this enabled to help this free and open-source project work out. Thank you ♡
  • Important: Only important announcements are sent, including maintenance times and breaking changes. It is recommended to keep at least this level enabled.
  • None: No notices are sent whatsoever.
• logs_channel: The channel where logs are sent to, which includes changes being made to the config, questions or suggestions.
  ⚠️ Warning: This currently does not log QOTDs being sent automatically or using /trigger, or the config getting re-initialized using /config initialize.
  I'm working to fix this in a future update, but for now, keep this in mind.

Questions

Questions are the main feature of OpenQOTD, and they are what the bot sends every day.
They can be added by staff members or suggested by users (if suggestions are enabled). Presets work a little differently, to learn more about them see Presets.

Types

Each question has one of three types, Suggested, Accepted or Sent:

• Suggested questions are questions that have been suggested by users, and have to be accepted or denied by staff members to be sendable. In listings, they are denoted using a red square (🟥)
• Accepted questions are questions that have been accepted or added by staff members, and are sendable. In listings, they are denoted using a blue diamond (🔷)
• Sent questions are questions that have been sent already, and are not sendable again. In listings, they are denoted using a green circle (🟢)

As you can see, the only questions that are sendable are Accepted questions, and they are prioritized over Presets if they are available.
If a QOTD is triggered either daily automatically or using /trigger, a random Accepted question is sent, and that question is marked as Sent.

Commands

The following commands are available to manage questions and are only available to Administrators or users with the admin_role set in the config:
Required parameters are shown in square brackets ([required]) and optional in angled brackets (<required>), and default values are shown using "value".

• /questions view [question_id]: View all available information about a question, including its type, content, author, the date it was added, the person who accepted it, and more.
• /questions list [type] <page1>: List all question of a certain type, which can be Suggested, Accepted or Sent.
• /questions search [query] <page1>: Search for questions using a query. All questions that contain the query in their content are shown, no matter the type. This is case-insensitive.
• /questions add [question] [type]: Add a question to the bot with a certain type, which can be Suggested, Accepted or Sent.
• /questions changetype [question_id] [type]: Change the type of a question to Suggested, Accepted or Sent. Note that setting a question from Suggest to Accepted works, but it is recommended to use /suggestions accept instead.
• /questions changetypebulk [from_type] [to_type]: Change the type of all questions of a certain type to another. For example, you can change all Sent questions to Accepted. Unlike /suggestions acceptall, running this command with Suggested→Accepted will not notify the suggesters.
• /questions remove [question_id]: Remove a question from the bot. This is irreversible, and the question is removed from all listings.

Suggestions

If suggestions are enabled, users can suggest questions using /suggest or /qotd.
These suggestions (=questions with type Suggested) have to be accepted or denied by staff members in order to be sendable, and they are sent to the suggestions_channel with buttons to accept or deny them.
Note that anyone can accept or deny suggestions using the buttons of the messages, so make sure to have your suggestions_channel set to a channel that is only viewable by people you trust!

Commands

The following commands are available to manage suggestions and are only available to Administrators or users with the admin_role set in the config:
Required parameters are shown in square brackets ([required]) and optional in angled brackets (<required>), and default values are shown using "value".

• /suggestions accept [suggestion_id]: Accepts a suggestion. This changes the type of the question to Accepted and notifies the suggester in private messages.
• /suggestions deny [suggestion_id] [reason]: Denies a suggestion with a reason. This permanently removes the suggestion from the bot and notifies the suggester with the denial reason in private messages.
  
• /suggestions acceptall: Accepts all suggestions. This changes the type of all suggestions to Accepted and notifies the suggesters in private messages.
• /suggestions denyall: Denies all suggestions without reason. This permanently removes all suggestions from the bot and notifies the suggesters in private messages.
  

Note that if you want to list all suggestions, you can use /questions list type:Suggested.

Presets

Presets are a special type of questions that are sent if they are enabled and there are no custom questions available.
Once a preset is sent, it is marked as completed, and is not sendable unless it is manually enabled again. They do NOT show in the /questions or /suggestions listings, and they are not editable, however it is possible to disable them individually by manually marking them as completed using /presets setactive.
Just like questions, they get sent in a random order and not as a queue.

Commands

• /presets list <type> <page1>: List all presets of a certain type, which can be Active or Completed.
  If no type is specified, all presets are shown.
• /presets setactive [preset_id] [active]: Set a preset to be Active or Completed. If a preset is active, it is sent if there are no custom questions available.
  
• /presets reset: Reset all presets to be active. This makes all presets sendable if there are no custom questions available.
• /presets suggest: Suggest a preset to be added to the bot globally. This is similar to /feedback, only that it is specifically for suggesting presets.

Other Commands

The following commands are other commands, most of which are available to everyone with the basic_role role (with a notable exception being /trigger being admin-only):
Required parameters are shown in square brackets ([required]) and optional in angled brackets (<required>), and default values are shown using "value".

• /help: Print general information about the bot.
• /leaderboard <page1>: View the leaderboard of the server, which shows the top users by the amount of Sent questions they have added (questions that have been accepted and sent as QOTD).
  This is the same as /lb.
• /topic <include_presetstrue>: Send a random question of type Sent to the current channel.
  This can be used to revive a dead chat and find an interesting topic to talk about.
  Using a button below the message, the person who ran the command can reroll the question as many times as they want.
  This command is purely visual, and does not alter the questions in any way, and the same topic can be sent multiple times.
• /sentquestions <page1>: List all questions that have been sent as QOTD.
  This is the same as /questions list type:Sent, except that it is available to all users with the basic_role (not just admins).
• /suggest [question]: Suggest a question to be added to the server, which will create a Suggested question that has to be accepted or denied by staff members to be sendable.
  This is the same as /qotd.
• /trigger: Trigger a QOTD manually. This sends a random available QOTD, as if it was sent automatically.
  This command is only available to Administrators or users with the admin_role set in the config.
• /feedback [message]: Send feedback to the bot's developer.
  This is available to all users globally, even if they don't have the basic_role.