Sample Bot
Updated 22 September 2026

Update log

Everything that changes in Sample Bot, in full, and how to turn each thing on. The announcement in Discord is the short version; this is where every detail lives.

v2.6.0

22 September 2026. Everything since v2.4.0.

The biggest update Sample Bot has had. A rebuilt message builder, a session dashboard, full Discord moderation with automod and ban appeals, merging servers, copying a setup between servers, a social feed, quota promotions, and ticket transcripts you can read on the website. Each section says how to set it up.

01

The message builder, rebuilt

Design any message the bot posts instead of typing a heading and a body into Discord. It is built so a good-looking message takes about a minute.

  • Every message starts from Default, exactly what your bot posts today, with Card, Card with logo, Modern, Just text and Blank beside it.
  • Only the parts you use are on screen, and clicking any part of the preview jumps to the box that edits it.
  • Fill-ins work everywhere they can. The player count, join code, server name, date and session status now work in every message.
  • Banners are edited right there, and they are the same setting as /config Banners.
  • Custom messages get their own command, like /rules, limited to the staff boards you choose.
How to set it up
  1. Go to samplebot.app/builder and sign in with Discord.
  2. Pick your server, pick what the message is for, then pick a look.
  3. Change the words and press Save. Panels and session posts use it straight away. Sticky messages and auto pings need it picked on their page in /config.
  4. To let a team design messages without full access, tick Use the message builder on their board in /config Staff boards.
02

Session dashboard

One message in your session channel that keeps itself up to date: whether a session is running, the server name, join code and owner, the player count, online staff, the queue, and how a community vote is going. It has a Game Quick-Join button and a Notifications button that turns the session ping on or off for whoever presses it. It stays at the top of the channel when a session ends.

  • The low-player command is now /session boost. Full and boost post a new message, and a boost pings your session role.
  • A boost no longer rewrites the original session post into a second copy.
  • Staff votes never appear on the dashboard. Only community votes do.
How to set it up
  1. In /config Channels, set Session Announcement Channel.
  2. For the Notifications button, set Session Ping Role in /config Roles.
  3. Optional: in /config Wording & images, write a Session Dashboard Intro.
  4. Run /send sessiondashboard. Change how it looks in the builder under Session dashboard.
03

Discord moderation and automod

  • Warnings, mutes, kicks, bans and timed bans, each filed as a numbered case with a reason. Timed bans lift themselves.
  • Automod, sixteen filters, from spam and scam links to mass pings and zalgo. Each can delete, warn, or both. Every filter is off until you turn it on, and staff are never filtered.
  • Automatic punishment decides in advance what happens when somebody keeps collecting cases.
  • The moderation dashboard is rebuilt, with one log for Discord, in-game and automod, and a card for every person.
How to set it up
  1. In /config Staff boards, give boards the moderation permissions they need: Warn, Mute, Kick and Ban members.
  2. In /config Moderation, pick a log channel and add preset reasons.
  3. Use /warn, /mute, /kick and /ban.
  4. For automod, turn on the filters you want in /config Automod.
04

Ban appeals

When somebody is banned with /ban, the message telling them why can carry an Appeal this ban button. What they write lands in a channel you choose, pinging the boards you choose. Accepting unbans them and sends them an invite back; denying tells them the ban stands. Only permanent bans made through /ban can be appealed.

How to set it up
  1. Open /config Moderation and press Ban appeals.
  2. Pick the channel appeals land in. That turns appeals on.
  3. Optional: pick the boards to ping, and set a fixed invite link. Without one, a single-use invite is made when an appeal is accepted.
  4. Anybody who can ban can accept or deny an appeal.
05

Tickets that close themselves

When the member stops replying, the ticket warns them and then closes, per ticket type. Nothing closes before staff have replied, and a ticket where the member spoke last is never closed.

How to set it up
  1. Open /config Tickets and pick a ticket type.
  2. Press Auto-close and set how many hours of silence close it, how many warnings to send, and how far apart. Zero hours turns it off.
  3. This is part of Sample Plus+.
06

Ticket transcripts on the website

Every closed ticket's transcript is kept and can be read at a link after signing in with Discord. Only the person who opened the ticket, staff who can handle that kind of ticket, and whoever runs the server can read it. The member gets the link when their ticket closes.

How to set it up
  1. Nothing to turn on. Every ticket closed from now on has one.
  2. Optional: to also post each transcript for staff, set a transcript channel on the ticket type in /config Tickets. The post carries a View transcript button.
07

Quota promotions and infractions

Promote whoever reaches two or three times the weekly quota by one rank, onto the next board if that is where the next rank is, and file an infraction of your choice for whoever misses it. It is decided every Monday for the week that just ended. Staff on approved leave are never punished, and a week is only judged if these rules were on for all of it.

How to set it up
  1. In /config Wording & images, set Weekly Shift Quota (minutes).
  2. To promote, set Promote At 2x Or 3x Quota to 2 or 3.
  3. To punish a miss, set Infraction For Missing Quota to warning, strike, suspension, demotion or termination.
  4. Make sure your ranks are set up on each board in /config Staff boards, with a role for each, and that Promotions Channel and Infractions Channel are set in /config Channels.
08

Merging two servers

/merge folds two servers into one: the roles, the channels, your Sample Bot setup, then the members. Nothing happens until the other server's owner reviews the whole list and accepts. Members who have not moved get reminders on your schedule.

How to set it up
  1. Merge requests are off by default. Allow the direction you want in /config Merge settings.
  2. The owner starting it runs /merge with the other server's ID and chooses what carries across.
  3. The other owner accepts from the message they are sent.
09

Copy a setup into another server

Panels, ticket types, automations, applications, FAQ answers, moderation setup, auto pings, sticky messages, roleplay types and the marketplace can be copied to another server. Tickets, shifts and punishment records never travel.

How to set it up
  1. In the server you are copying from, open /config Export and import and export it. You get a code.
  2. In the other server, import that code in the same place. Anything that cannot be matched is shown before anything is written.
10

Staff

  • Boards hand out roles. Set them with Roles it gives on the board in /config Staff boards.
  • Duty nicknames in your own words. Set the three Nickname Tag settings in /config Wording & images.
  • Demotions say what an accepted appeal hands back. Pick the rank with the appeal_rank option on /infraction issue.
  • Nobody decides their own infraction appeal, and roles the bot owns put themselves back if removed by hand. Both are automatic.
11

Community

  • A social feed. Members make accounts with /account and post with /post. Set the forum channel, the log channel and account limits in /config Posts.
  • Sticky messages and auto pings: set them up in /config Sticky messages and /config Auto pings. Both are part of Sample Plus+.
  • The marketplace is a shop, with a picture and a Buy button per item. Add items in /config Marketplace, then run /send marketplace.
  • Suggestions can ping boards and limit how many one member has waiting. Set both in /config Suggestions.
  • Counting saves: servers that have reviewed the bot at samplebot.app/reviews get one save a day. Choose when it is used in /config Counting.
  • /blacklist keeps your server's list of servers you will not deal with. Set Server Blacklist Channel in /config Channels, and give boards Blacklist other servers in /config Staff boards.
12

The assistant works without paying for AI

The ticket assistant, the application reader and the automation builder run on six AI providers: Anthropic, Google Gemini, Groq, OpenAI, xAI and OpenRouter. Gemini and Groq are free with no card.

How to set it up
  1. Get a key from the provider you want.
  2. Paste it in /config Connections. The bot checks it and picks a model that key can use.
13

Sample Plus+

One payment of $50 USD or 8,000 Robux for one server, with our team setting it up for you. Card payments become your slot the moment they go through, slots stack, and every free server gets three days of Plus to try a week after the bot joins.

How to set it up
  1. Run /buy plus, or see the pricing page.
  2. Redeem the slot on the server you want from the same command.
14

Fixed

  • People joining a busy server were welcomed as member number one.
  • Buttons failed with "This interaction failed" for over a minute after every restart.
  • The staff boards page would not open once a server had about fifteen boards. The same fix covers ticket types, applications, dashboard pages and the marketplace.
  • The website took about a minute to load your servers in the CAD and the staff dashboard.
  • Tickets that close themselves never actually did once a ticket was claimed.
  • Adding a marketplace item failed in every server.
  • /config Automod would not open.
  • Panel wording could not be saved.
  • A suggestion with a ping role never posted.
  • Continue with verification failed for members who were already verified.
  • Live in-game events could not be set up without buying the CAD.
  • Voice channels never appeared in the status channel pickers.
  • One deleted emoji could take a whole ticket panel down.
  • Verify and ticket buttons disappeared the second time a design was saved.
  • A panel lost its top banner as soon as it was given a design.