Minecraft Discord Server Template

Give players one place to find the server address and rules, apply for the whitelist, report bugs and griefing, get support from staff, and show off builds, while keeping exploits and investigations private.

Built for: Survival multiplayer (SMP) servers · Minecraft networks and minigame servers · Modded server communities · Server owners and staff teams

Create each category with its permissions first, then add channels inside it and keep them synced to the category. Channel types used: Text, Announcement, Forum, Voice.

Create roles in this order, from the top of the role list down. A role can only manage roles below it, and bot roles must sit above any role they assign.

Different staff setup or bots? Adapt this hierarchy in the roles generator.

1. Owner

   Display role for the server owner.

   How members get it

   Owner account.

   Display

   Shown separately · Not mentionable

   Enable

   No permissions (cosmetic or ping role)

   Withhold

   Administrator — not needed

2. Admin

   Runs the Minecraft server and Discord configuration.

   How members get it

   Assigned by the owner. Usually matches in-game operator access.

   Display

   Shown separately · Not mentionable

   Enable

   Manage Server, Manage Roles, Manage Channels, Manage Webhooks, View Audit Log, Ban Members, Kick Members, Timeout Members, Manage Messages, Manage Threads, Bypass Slowmode

   Withhold

   Administrator

3. Moderator

   Handles reports in Discord and in game.

   How members get it

   Assigned by Admins.

   Display

   Shown separately · Mentionable

   Enable

   Timeout Members, Kick Members, Manage Messages, Manage Threads, Manage Nicknames, View Audit Log, Bypass Slowmode

   Withhold

   Manage Roles; Manage Webhooks; Ban Members until trusted

4. Helper

   Answers support posts and reviews whitelist applications.

   How members get it

   Assigned by Admins to trusted players.

   Display

   Shown separately · Mentionable

   Enable

   Manage Threads

   Withhold

   Timeout Members; Kick Members

5. Builder

   Trusted builders who work on spawn, event arenas or shared server projects.

   How members get it

   Assigned by Admins after reviewing previous work.

   Display

   Not separated · Not mentionable

   Enable

   No permissions (cosmetic or ping role)

   Withhold

   Manage Channels; Mention @everyone, @here, and All Roles

6. Whitelisted

   Approved players. Mirrors the in-game whitelist.

   How members get it

   Assigned by a Helper or Admin at the same time as the in-game whitelist entry, or automatically by a bridge plugin with account linking.

   Display

   Shown separately · Not mentionable

   Enable

   No permissions (cosmetic or ping role)

7. Member

   Everyone who has completed onboarding.

   How members get it

   Granted by Community Onboarding: add it to every answer of the required edition question.

   Display

   Not separated · Not mentionable

   Enable

   View Channels, Send Messages, Send Messages in Threads, Create Public Threads, Read Message History, Add Reactions, Attach Files, Embed Links, Connect, Speak

   Withhold

   Mention @everyone, @here, and All Roles

8. Edition roles (Java, Bedrock)

   Shows how a player connects, so support can answer correctly.

   How members get it

   Self-assigned through onboarding.

   Display

   Not separated · Not mentionable

   Enable

   No permissions (cosmetic or ping role)

9. Interest roles (Survival, Building, Redstone, PvP, Events)

   Routes players toward relevant conversations and helps organisers understand what the community wants to do.

   How members get it

   Self-assigned through onboarding or a manual role menu when Community is off.

   Display

   Not separated · Not mentionable

   Enable

   No permissions (cosmetic or ping role)

10. Event Ping / Update Ping

    Opt-in notifications for events and server updates.

    How members get it

    Self-assigned through onboarding; Admins mention them only for the promised topic.

    Display

    Not separated · Not mentionable

    Enable

    No permissions (cosmetic or ping role)

Community Onboarding assigns Member through the edition question, adds low-risk Minecraft interest roles, and keeps update and event notifications opt-in. Without Community, staff can grant Member and Whitelisted manually and members can choose interests from a role menu.

Default channels: rules, announcements, server-info, how-to-join, general, builds, trading, events-chat, player-support, bug-reports, whitelist-applications

Discord requires at least 7 default channels for Community Onboarding, and @everyone must be able to view and send messages in at least 5 of them.

Suggested first steps: Read #server-info and #rules → Choose edition and interest roles → Apply in #whitelist-applications if the server is whitelisted → Ask for help in #player-support or share a project in #builds

Verification level

Medium — A verified email and an account registered for more than 5 minutes filters most throwaway accounts without blocking genuine players.

Explicit media filter

Scan media content from all members.

AutoMod rules

• Block spam contentBlock the message and alert #mod-log.
• Block mention spam (limit around 5)Block and time out for 10 minutes.
• Commonly flagged words: the Insults and Slurs and Sexual Content listsBlock and alert.
• Custom keywords: hacked-client names, x-ray packs, account-selling and "free Minecraft account" phrasesBlock and alert; review the list when new clients appear.

Escalation

1. Warning in Discord or in game
2. Timeout or temporary in-game ban, logged in #mod-log
3. Permanent ban from the Minecraft server
4. Discord ban for harassment, scams or repeat offences

• Bans don't cross over automatically: a Discord ban doesn't remove someone from the game whitelist, and an in-game ban doesn't remove them from Discord. Log both in #mod-log.
• Exploits and item duplication should never be posted publicly. Ask players to report them privately so the fix can ship before others copy it.
• Never ask players for their Microsoft or Minecraft account passwords, and warn them that staff will never ask.

Try Discord's built-in features first. Bot names are examples to evaluate, not endorsements; CordNexa has no affiliation with any bot. Review the permissions a bot requests before adding it.

These steps are specific to this kit. For the reasoning behind each stage — permissions, onboarding, testing and launch — see how to make a Discord server.

1. Create the server and choose Community features

   Turn on multi-factor authentication (2FA) for the owner. Enable Community if you want Forum channels, an Announcement channel and native Onboarding; it requires a verified-email verification level, the explicit media filter set to scan all members, a rules channel and a community updates channel. If Community stays off, make #announcements read-only and use ordinary text channels with threads for builds, applications, support and bugs.

2. Create roles top-down

   Owner → Admin → Moderator → Helper → Builder → Whitelisted → Member → edition, interest and ping roles. Administrator stays with the owner account; Builder and interest roles need no elevated server permissions.

3. Launch with the compact core

   Start with #rules, #announcements, #server-info, #how-to-join, #general, #introductions, #builds, #trading, #events-chat, #how-to-get-help, #player-support, #bug-reports, #player-reports, the two voice rooms and the three staff channels. Add #screenshots, #changelog, whitelist applications and the optional console only when your workflow needs them.

4. Write #server-info and #how-to-join

   Include the address, versions and edition support, and a copyable whitelist application format.

5. Build the forums or text fallbacks

   With Community enabled, add the tags to #builds, #whitelist-applications, #player-support and #bug-reports; make status tags moderator-only and require tags on new posts. Without Community, create those names as text channels, pin the posting format and open one thread per build, application or support case.

6. Separate help from reports

   Use #player-support for public connection and gameplay questions. Keep #player-reports read-only with private submission instructions, then review evidence in staff-only #reports-review. Never ask players to post account details or moderation evidence publicly.

7. Configure Community Onboarding

   In Server Settings → Onboarding, add the edition, interests and ping questions and choose the listed default channels. Discord requires at least 7 defaults, including at least 5 where @everyone can View Channel and Send Messages. If Community stays off, assign Member and Whitelisted manually and use a role menu for edition, interests and opt-in pings.

8. Set up AutoMod and verification

   Set verification to Medium and add the AutoMod rules, including your hacked-client keyword list.

9. Connect the game (optional)

   If you use a bridge plugin, create its channels, give the bot only the permissions it needs in them, and restrict any console channel to Admins.

10. Test the whitelist flow

    Have a trusted player apply, get approved, receive Whitelisted and join the game. Use View Server As Role to check STAFF is hidden.

1. Discord community rule: treat players respectfully. No harassment, slurs, threats, doxxing or unwanted private messages.
2. Discord community rule: no spam, phishing, fake giveaways, staff impersonation, account selling or attempts to evade moderation.
3. Minecraft gameplay rule — customise this for your server: define whether griefing, theft, PvP, farms, client mods, macros and exploits are allowed before launch.
4. Report exploits, suspected cheating and duplication methods through the private route in #player-reports. Do not publish instructions or evidence that others could misuse.
5. Use #trading only for honest in-game trades. State what you offer and want; staff cannot recover items unless your published gameplay policy says otherwise.
6. Submit player reports privately with the relevant username, time, location and evidence. Do not make public accusations or organise retaliation.
7. Never share Microsoft or Minecraft account passwords, recovery codes, addresses or payment details. Legitimate staff will never ask for them.

Need stricter or more relaxed wording? Customise these rules in the rules generator.

Welcome! Read #rules, then check #server-info for the address, supported version and join steps. Choose your edition and Minecraft interests, say hello in #general, find players through #events-chat, or share a project in #builds. Connection problem? Start with #how-to-get-help and post in #player-support. Use the private route in #player-reports for player conduct or sensitive evidence.

Want a shorter, professional or bot-ready version? Try the welcome message generator.

• v1.1 · 2026-10-03
  • Expanded the compact launch path, Minecraft interest onboarding, public support/private report separation, safer specialist roles, customisable gameplay rules and setup FAQs.
• v1.0 · 2026-09-28
  • First release: server info, whitelist and support forums, private exploit and grief reporting, and in-game/Discord staff coordination.