ROLEPLAY DISCORD TEMPLATE / FREE SETUP KIT

Roleplay World Hub

A persistent text-roleplay world: lore, character applications, in-character locations, out-of-character spaces, consent guidelines, events and an archive.

  • 20–1,000 members
  • Advanced
  • ~75 min setup
  • 24 channels · 9 roles
  • Needs Community features

Is this template right for you?

Run a shared fictional world that many people write in at once. Lore is easy to find, characters are approved before they enter the story, locations keep scenes organised, and clear consent and out-of-character rules protect the people behind the characters.

Best for

  • Ongoing worlds with dozens or hundreds of writers
  • Communities that approve characters before they play
  • Worlds with many locations and storyline events

Not ideal for

  • A fixed group playing sessions with one game master — use TTRPG Campaign
  • Fan communities that discuss a series rather than write in it — use Anime Fan Community

Built for: Text-roleplay communities · Fantasy, sci-fi and modern-setting roleplay worlds · Worldbuilders opening a setting to other writers · Roleplay moderation teams

Categories & channels

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.

START HERE

Read-only

Rules and how roleplay works here.

Category permissions: @everyone: deny Send Messages. Admin and Lore Keeper: allow Send Messages.

rules Text

Community rules, including the consent and content guidelines.

Read-only
announcements Announcement

World events, new locations and staff news.

Read-only
rp-guide Text

How to roleplay here: post length, turn etiquette, how to mark brief out-of-character notes (for example in double brackets), and how to join or leave a scene.

Read-only
content-guidelines Text

What's allowed on screen, what fades to black, content warnings for scenes, and how to ask a partner before intense themes.

Read-only

THE WORLD

Read-only

Lore maintained by Lore Keepers.

lore Forum

One post per topic, written by Lore Keepers. Members ask questions in the post's replies.

Permissions: Deny Send Messages (creating posts) for @everyone; allow Send Messages in Threads so members can reply.

Forum tags: History, Factions, Places, Magic & technology, Creatures, Canon update

Read-only
timeline Text

Major canon events in order, updated after storylines conclude.

Read-only
map Text

The world map and where each location channel sits in it.

Read-only

CHARACTERS

Public

Applications and the approved roster.

character-applications Forum

One post per character using the pinned application format. Reviewers reply with feedback and set the status tag.

Permissions: Make every status tag moderator-only (Manage Threads) and require a tag on new posts.

Forum tags: Pending, Needs changes, Approved, Retired

Public
character-directory Text

One line per approved character with a link to their application, so writers can find each other.

Read-only

OUT OF CHARACTER

Public

Where players talk as themselves.

ooc-general Text

Out-of-character chat.

Public
rp-requests Forum

Looking for a scene partner: a post per request with setting, tone and availability.

Forum tags: One-on-one, Group, Combat, Slice of life, Mystery, Found a partner

Public
art-and-music Text

Character art, playlists and inspiration. Credit other people's work.

Public
questions Text

Questions about the world, rules or applications.

Public

IN CHARACTER — LOCATIONS

Role-gated

The world itself. One channel per location; each scene gets a thread.

Category permissions: Deny Send Messages for @everyone; allow View Channels, Send Messages, Create Public Threads and Send Messages in Threads for Approved Roleplayer. Everyone else can read.

the-market-square Text

A busy public location. Start a thread per scene, titled with the characters and a one-line premise.

Role-gated
the-tavern Text

Social scenes and chance meetings.

Role-gated
the-wilds Text

Travel, exploration and danger.

Role-gated
the-citadel Text

Politics and faction scenes.

Role-gated

EVENTS

Public

Staff-run storylines.

event-board Text

Upcoming storylines, with a Scheduled Event for live sessions.

Permissions: Storytellers post; members react to join.

Read-only
event-signups Text

Sign a character up for an event and ask event questions.

Public
Event Voice Voice

Optional voice for live events or planning calls.

Public

ARCHIVE

Read-only

Finished storylines and retired locations, kept for reference.

Category permissions: Deny Send Messages and Send Messages in Threads for everyone except staff.

archived-scenes Text

Staff move ended location channels here (or lock them in place) and link notable scene threads.

Read-only

STAFF

Staff only

Moderation and application review.

Category permissions: Deny View Channels for @everyone. Allow Admin, Moderator, Lore Keeper and Storyteller.

staff-chat Text

Coordination and canon decisions.

Staff only
application-review Text

Discuss applications before replying publicly.

Staff only
mod-log Text

AutoMod alerts and moderation actions, including whether an issue was in or out of character.

Staff only

Role hierarchy & permissions

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 world's 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

    Manages the server and settles disputes.

    How members get it
    Assigned by the owner.
    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
    Withhold
    Administrator
  3. Moderator

    Enforces rules, including out-of-character conduct.

    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
    Withhold
    Manage Roles; Ban Members until trusted
  4. Lore Keeper

    Writes lore, reviews applications and keeps canon consistent.

    How members get it
    Assigned by Admins.
    Display
    Shown separately · Mentionable
    Enable
    Manage Threads, Manage Messages
    Withhold
    Kick Members; Ban Members
  5. Storyteller

    Runs events and plays major NPCs.

    How members get it
    Assigned by Admins.
    Display
    Shown separately · Mentionable
    Enable
    Manage Threads, Create Events, Manage Events, Mention @everyone, @here, and All Roles
    Withhold
    Kick Members; Ban Members
  6. Approved Roleplayer

    Can post in the in-character locations.

    How members get it
    Assigned by a Lore Keeper when their first character is approved. Not granted by onboarding, so reviewers stay in control.
    Display
    Shown separately · Not mentionable
    Enable
    Create Public Threads, Send Messages in Threads
  7. Member

    Everyone who has completed onboarding. Can read everything and use OOC channels.

    How members get it
    Granted by Community Onboarding: add it to every answer of the required experience question.
    Display
    Not separated · Not mentionable
    Enable
    View Channels, Send Messages, Send Messages in Threads, Read Message History, Add Reactions, Attach Files, Embed Links
    Withhold
    Mention @everyone, @here, and All Roles
  8. Style roles (Combat, Slice of life, Mystery, Worldbuilding)

    Helps writers find partners who enjoy the same kind of scene.

    How members get it
    Self-assigned through onboarding.
    Display
    Not separated · Mentionable
    Enable
    No permissions (cosmetic or ping role)
  9. Scene Open Ping / Event Ping

    Opt-in notifications for open group scenes and events.

    How members get it
    Self-assigned; Storytellers mention them.
    Display
    Not separated · Not mentionable
    Enable
    No permissions (cosmetic or ping role)

Onboarding flow

Community Onboarding introduces new members to the world and routes them to the application process. The Approved Roleplayer role is given by reviewers, not by onboarding.

Question 1 · required

How much roleplay have you done?

  • I'm new to roleplay→ Member
  • I've roleplayed before→ Member
  • I'm here to read and chat→ Member
Question 2 · optional

What kinds of scenes do you enjoy?

  • Combat→ Combat role
  • Slice of life→ Slice of life role
  • Mystery→ Mystery role
  • Worldbuilding→ Worldbuilding role
Question 3 · optional

Which notifications do you want?

  • Open group scenes→ Scene Open Ping
  • Events→ Event Ping

Default channels: rules, announcements, rp-guide, content-guidelines, lore, character-applications, ooc-general, rp-requests, art-and-music, questions, event-signups

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 #rp-guide and #content-guidelines → Browse #lore → Submit a character in #character-applications

Moderation setup

Verification level
Medium — A verified email and an account registered for more than 5 minutes; the application step adds a human check before anyone posts in character.
Explicit media filter
Scan media content from all members.

AutoMod rules

  • Block spam contentBlock 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. Review alerts before acting, because in-character dialogue can trigger them.
  • Block words in member profile names (slurs list)Block and alert.

Escalation

  1. Out-of-character reminder in the scene thread
  2. Private conversation with a Moderator
  3. Timeout
  4. Character suspended from play
  5. Kick or ban for harassment or ignoring consent
  • Moderate the player, not the character: villains can be villainous in character, but bullying through a character is harassment.
  • If members may be under 18, keep all content suitable for them. Explicit content is only allowed in channels marked age-restricted, and only on an adults-only server.
  • Archiving: when a storyline ends, lock its channel (deny Send Messages) or move it to ARCHIVE, and add it to #timeline.

Recommended bots

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.

Character posting (proxy) bots

Optional

Some communities let writers post under a character's name and avatar.

Native first: Plain posting with the character's name in bold works without a bot. Proxy bots use webhooks, so check the permissions they request and limit them to IC channels.

Dice rolling

Optional

Some worlds resolve conflict with dice.

Native first: Many worlds use collaborative writing instead. Add a dice bot only if your rules need it.

Step-by-step setup

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 enable Community

    Turn on multi-factor authentication (2FA) for the owner, then enable Community (it requires a verified-email verification level, the explicit media filter set to scan all members, a rules channel and a community updates channel). Community is needed for the forum and announcement channels.

  2. Write the guidelines first

    Write #rp-guide and #content-guidelines before building anything else: they decide what the location channels and application format look like.

  3. Create roles top-down

    Owner → Admin → Moderator → Lore Keeper → Storyteller → Approved Roleplayer → Member → style and ping roles.

  4. Build the lore forum

    Create #lore with its tags, deny post creation for @everyone and allow replies, then seed it with the posts a new writer needs first.

  5. Set up applications

    Pin an application format in #character-applications, add moderator-only status tags, and agree who reviews and how quickly.

  6. Create locations

    Start with three or four locations. Deny Send Messages for @everyone and allow it for Approved Roleplayer, so everyone can read but only approved writers post.

  7. Configure Community Onboarding

    Add the questions and default channels. Discord requires at least 7 default channels, with at least 5 where @everyone can view and send messages.

  8. Test both paths

    Use View Server As Role as Member (can read IC, can't post) and Approved Roleplayer (can post). Then approve a test character end to end.

Make it yours

Grow locations slowly

Add a location when an existing one is regularly busy. Empty locations make a world feel abandoned.

Faction play

Add faction roles and a private channel per faction for in-character planning, visible to that faction's role.

Adults-only worlds

If the server is 18+, mark any channel with explicit content as age-restricted and describe it in #content-guidelines.

Seasonal storylines

Run a season as a set of events, then archive its locations and record the outcome in #timeline.

Community rules

  1. Treat people with respect out of character. No harassment, slurs or hate speech.
  2. In character and out of character are separate. What a character says isn't the player's view, and bullying someone through a character isn't allowed.
  3. Ask before intense themes. Use content warnings in scene titles, and anyone can leave or fade a scene to black.
  4. Don't control other people's characters or make your character unbeatable.
  5. Only approved characters post in location channels. Keep brief OOC notes in double brackets.
  6. Canon comes from #lore and Lore Keepers. Propose additions in #questions instead of inventing major world facts.
  7. Credit art and writing that isn't yours.

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

Welcome message

Welcome to the world! Read #rp-guide and #content-guidelines, then explore #lore to find your footing. When you're ready, submit a character in #character-applications — once it's approved you can post in the locations. Until then, say hello in #ooc-general and find scene partners in #rp-requests.

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

Roleplay World Hub FAQ

How do character applications work on Discord?

Use a forum channel with one post per application, a pinned format and moderator-only status tags. Reviewers discuss privately, reply in the post, and give the Approved Roleplayer role when a character is accepted. Forum channels need Community features.

How do I keep in-character and out-of-character chat separate?

Give IC and OOC their own categories, allow only approved writers to post in IC locations, and agree a convention such as double brackets for short OOC notes inside scenes.

How do I handle dark or mature themes?

Write content guidelines, require content warnings and partner agreement before intense scenes, and allow anyone to leave a scene. Explicit content is only allowed in age-restricted channels on an adults-only server.

What do we do with old locations?

Lock the channel by denying Send Messages, move it to an ARCHIVE category, and note the storyline's outcome in #timeline.

Version history

  • v1.0 · 2026-09-28
    • First release: lore forum, character applications, IC locations with scene threads, consent guidelines, events and archiving.

CordNexa is independent and not affiliated with or endorsed by Discord. Discord features change over time; this kit was last reviewed on 2026-09-28.