How to set up a Discord trivia bot

Before you start

• Create a bot, invite it to a server you manage, and bring it online. Fun is included on Free.
• Choose a test text channel where the bot can read the conversation and send messages with embeds. Have a second consenting member available to check the difference between a personal trivia turn and a shared icebreaker.

1. Enable Fun and choose a place to play

   Open Modules on your bot dashboard and enable Fun. Start in a quiet text channel where a question will not interrupt support or an important announcement. The commands in this guide reply where they are invoked, so move into the intended channel before beginning. There is no trivia destination setting to redirect a round elsewhere. All examples use ! as the command prefix. If you configured a different prefix for your bot, substitute it in the examples. Keep the first test small enough that everyone can see the question and its result.

   Decide what kind of activity you want before presenting it to members. This module offers a short personal question with answer buttons and separate casual group interactions. It has no trivia question editor, category selector, difficulty setting, or tournament configuration in the current handler. The question bank is built into the module, so repeated rounds can repeat questions. That works for an occasional conversation starter, but it would be misleading to advertise an endless fresh quiz feed or a curriculum tailored to your community’s subject.

2. Start a round and read the answer buttons

   Enter !trivia with no arguments. The bot selects one built-in question and displays four possible answers, with buttons labeled A, B, C, and D. Read the text next to each letter before clicking: the answers are shuffled, so a remembered letter is not a reliable answer on a later round. The person who issued the command should choose a button. After an accepted click, the bot updates the question message to say whether the answer was correct and identify the correct answer. The buttons become disabled once the answer is revealed.

   Watch one full successful turn before adding more activity. Confirm that the question is readable, the button labels correspond to the displayed choices, and the result appears on the same message. The public message lets others observe, but the answer interaction is filtered to the member who started the round. A second member clicking a button cannot submit that player’s answer. Explain this before inviting a crowded channel to participate, since an inactive response to someone else’s click can look like a malfunction when the expected rule has not been stated.

3. Test the timeout and take turns in one channel

   Start another round and deliberately leave it unanswered. The handler waits 20 seconds for the initiating member’s button interaction, then edits the message to reveal the answer and disable the buttons. That time window is fixed in the current module; there is no dashboard control to lengthen it. Check the completed message instead of continuing to press old buttons. A timeout ends that round, so the next player should request a fresh question. Waiting through this test also helps staff distinguish an expired interaction from a bot that has gone offline.

   Only one trivia round can be active in a channel at a time. A second request while the first is waiting receives an active-game response rather than another question. The command also declares a 10-second cooldown, so avoid rapidly repeating requests when testing. Once the first round answers or times out, another player can take a turn. The handler releases its channel lock when a round finishes or encounters an error. If you want everyone to answer together, organize turn-taking explicitly or choose the shared icebreaker below instead of promising multiplayer trivia scoring.

4. Let the channel join a Would You Rather prompt

   Enter !wouldyourather to post a built-in pair of alternatives with Option A and Option B buttons. Unlike trivia, this interaction collects choices from multiple members. Ask your volunteer to pick one option, then choose the other from your own account. The message shows the counts so the conversation can compare preferences. These are prewritten prompts selected by the module, not questions supplied as arguments. If your community needs its own question and answer choices, the related Polls guide describes the separate module designed for that task.

   Each member has one stored choice for that prompt. Clicking the other option changes the vote; clicking the same option again leaves that choice in place instead of removing it. Try both actions and watch the counts so your explanation matches what members see. The collector runs for five minutes and then disables its buttons. Its votes are held in memory for that interaction, not saved as a durable survey database. Treat the prompt as a temporary icebreaker, and write any useful conclusion in the conversation before everyone moves on.

5. Add dice rolls and small decisions between rounds

   For a quick dice check, enter !roll 2d6. The reply includes the individual rolls, their total, and a footer showing the dice notation. Without an argument, !roll uses one six-sided die; !roll 20 uses one die with 20 sides. The implementation clamps the count to 1 through 10 dice and the sides to 2 through 100. Those are command limits, not paid-plan quotas. Read the footer after experimenting with a larger input, because the bot adjusts out-of-range values rather than promising the exact number originally requested.

   Enter !flip for a heads-or-tails result, or !choose Sketching | Puzzle | Trivia for a random selection from three named activities. The vertical bars separate options; spaces alone do not create separate choices. The chooser requires at least two nonempty options and displays the selected one. These outcomes are random prompts for casual play, not community votes. If an actual event decision needs member agreement, ask people directly or publish a poll. No part of this dice or choice workflow automatically transfers money, grants a role, or records tournament points.

6. Troubleshoot the core game and explain its limits

   If a question does not appear, check that the bot is online, Fun is enabled, the prefix matches, and the bot can send embeds in the current channel. If the question appears but an answer does not register, check who started it and whether its buttons have already expired. Verify a fresh round after fixing access. The built-in trivia and dice handlers do not fetch content from an external image provider, so they are useful checks of the core module even when unrelated entertainment commands have trouble retrieving an image.

   The wider Fun module also has !meme, !cat, and !dog, which depend on external services and may fail independently of trivia. Meme selection filters posts marked adult, but that filter is not a promise that every returned image suits your community. Preview those activities separately if you intend to introduce them. Publish a short explanation of personal trivia turns, the answer window, and the shared icebreaker rather than announcing features the module does not provide. Use the signup button below when you are ready to bring these free activities to your own hosted bot.