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
A persistent text-roleplay world: lore, character applications, in-character locations, out-of-character spaces, consent guidelines, events and an archive.
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.
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.
Rules and how roleplay works here.
Community rules, including the consent and content guidelines.
World events, new locations and staff news.
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.
What's allowed on screen, what fades to black, content warnings for scenes, and how to ask a partner before intense themes.
Lore maintained by Lore Keepers.
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
Major canon events in order, updated after storylines conclude.
The world map and where each location channel sits in it.
Applications and the approved roster.
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
One line per approved character with a link to their application, so writers can find each other.
Where players talk as themselves.
Out-of-character chat.
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
Character art, playlists and inspiration. Credit other people's work.
Questions about the world, rules or applications.
The world itself. One channel per location; each scene gets a thread.
A busy public location. Start a thread per scene, titled with the characters and a one-line premise.
Social scenes and chance meetings.
Travel, exploration and danger.
Politics and faction scenes.
Staff-run storylines.
Upcoming storylines, with a Scheduled Event for live sessions.
Permissions: Storytellers post; members react to join.
Sign a character up for an event and ask event questions.
Optional voice for live events or planning calls.
Finished storylines and retired locations, kept for reference.
Staff move ended location channels here (or lock them in place) and link notable scene threads.
Moderation and application review.
Coordination and canon decisions.
Discuss applications before replying publicly.
AutoMod alerts and moderation actions, including whether an issue was in or out of character.
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.
Display role for the world's owner.
Manages the server and settles disputes.
Enforces rules, including out-of-character conduct.
Writes lore, reviews applications and keeps canon consistent.
Runs events and plays major NPCs.
Can post in the in-character locations.
Everyone who has completed onboarding. Can read everything and use OOC channels.
Helps writers find partners who enjoy the same kind of scene.
Opt-in notifications for open group scenes and events.
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.
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.
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.
Some worlds resolve conflict with dice.
Native first: Many worlds use collaborative writing instead. Add a dice bot only if your rules need 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.
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.
Write #rp-guide and #content-guidelines before building anything else: they decide what the location channels and application format look like.
Owner → Admin → Moderator → Lore Keeper → Storyteller → Approved Roleplayer → Member → style and ping roles.
Create #lore with its tags, deny post creation for @everyone and allow replies, then seed it with the posts a new writer needs first.
Pin an application format in #character-applications, add moderator-only status tags, and agree who reviews and how quickly.
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.
Add the questions and default channels. Discord requires at least 7 default channels, with at least 5 where @everyone can view and send messages.
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.
Add a location when an existing one is regularly busy. Empty locations make a world feel abandoned.
Add faction roles and a private channel per faction for in-character planning, visible to that faction's role.
If the server is 18+, mark any channel with explicit content as age-restricted and describe it in #content-guidelines.
Run a season as a set of events, then archive its locations and record the outcome in #timeline.
Need stricter or more relaxed wording? Customise these rules in the rules generator.
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.
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.
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.
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.
Lock the channel by denying Send Messages, move it to an ARCHIVE category, and note the storyline's outcome in #timeline.
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.