Discord Roleplay Formatting Guide: Style Posts That Read Like a Story
Discord is one of the biggest roleplay platforms in the world right now. Forum-style RP servers, PBP (play-by-post) campaigns, character-driven server lore, and live one-shots are all happening in chat channels designed for short messages.
The problem: Discord's message box wasn't built for roleplay. It cuts you off at 2,000 characters. It doesn't differentiate dialogue from narration. It has no built-in way to mark a scene break or indicate "OOC" (out of character) versus "IC" (in character) text.
Roleplayers solved all of this with markdown conventions, Unicode tricks, and a handful of formatting patterns that became unwritten community standards. This guide is the field manual.
Preview every post before sending. The Discord Message Editor renders your dialogue, italics, and code blocks live so you can see exactly how a long roleplay post will look in chat.
The core roleplay formatting conventions
These aren't enforced — they're just what most servers expect. Following them makes you legible to other RPers immediately.
Dialogue in plain text or quotes
Most roleplayers write spoken dialogue in plain text, sometimes inside quote marks:
"I told you we shouldn't have come here," she muttered.
Some servers prefer bold for spoken lines so they stand out from action:
**"I told you we shouldn't have come here,"** she muttered.
Pick one and stick with it across your posts.
Actions in italics
Physical actions, gestures, and movement go in italics:
*She stepped back from the door, hand resting on her sword hilt.*
This is the single most-used roleplay convention on Discord. Italic = action.
Thoughts in italics with quotes or brackets
Internal thoughts vary by server. Common patterns:
*'This is a trap,' she thought.*
*[This is a trap.]*
_Italic underscored thoughts._
Read your server's pinned guide if there is one — thought formatting is the area with the most house-style variation.
OOC vs IC
OOC (out of character) breaks should be visually distinct from your roleplay text. Common methods:
((OOC: brb, dinner — pause for 20 min))
-# OOC: brb, dinner — pause for 20 min
The -# subtext format makes OOC text small and gray, which keeps it from interrupting the visual flow of the channel. Most modern servers have moved to subtext OOC.
Scene breaks
When a scene shifts time, location, or POV, mark it clearly. Popular options:
─── ⋆⋅☆⋅⋆ ───
━━━━━━━━━━━━━━━━━━━━
⋅ ⋅ ⋅ ⋅ ⋅ ⋅ ⋅ ⋅ ⋅ ⋅
A horizontal divider gives readers a clear "new scene starts here" signal in the middle of a long post.
Anatomy of a clean roleplay post
Here's a template that combines the conventions above. Every line plays a specific role.
**[Character Name] — [Location]**
*She moved through the empty marketplace, boots silent on the wet stones.
The lanterns hadn't been lit yet. That was the first sign something was wrong.*
"Hello?" she called, voice carrying further than she'd meant it to.
*A figure stepped out from between the stalls — tall, hooded, hands empty.*
"You're early," it said.
That post has a header (who and where), narration in italics, dialogue in plain text, and a clear rhythm of action → dialogue → action → dialogue.
Character headers and name plates
Many roleplayers preface every post with a styled header so others can scan a channel and immediately identify whose turn is whose. Common formats:
Bold name + location
**Aria — The Crossroads Inn**
Fancy font name (using the Font Transformer)
𝔄𝔯𝔦𝔞 — The Crossroads Inn
Boxed header
╔══════════════════╗
ARIA — Crossroads
╚══════════════════╝
Stat block
**Aria** | HP: 18/20 | Status: Wary
The stat block format is common in stat-tracked RP. Pairs well with colored code blocks for status:
- HP: 8/20 (Wounded)
Long roleplay posts and the 2000-character problem
Discord's character limit hits roleplayers harder than almost any other community. A solid intro post — character description, a few paragraphs of narration, opening dialogue — easily clears 2,000 characters once you add italics, asterisks, and headers.
Manually splitting a post is risky:
- Cutting mid-sentence kills the rhythm
- Cutting mid-italic block leaves an unmatched
*that breaks formatting on the next message - Cutting inside dialogue makes the second half look out of context
Don't split posts manually. The Discord Message Splitter breaks your post at safe boundaries (paragraph breaks, sentence ends) and never cuts inside a markdown block.
The splitter also lets you append part numbers (1/3, 2/3, 3/3) so other players know to wait for the full post before responding.
For more on character limits and Nitro's expanded 4,000-character cap, see the Discord character limit guide.
Useful formatting patterns by post type
Intro posts (entrance to a scene)
Long intro posts benefit from a clear three-part structure:
**[Header: Character — Setting]**
*[Setting description: what they see, hear, smell. 2-4 sentences.]*
*[Their action: what they're doing as they enter the scene.]*
"[Their first line of dialogue, if any.]"
Combat posts
Combat moves fast. Short posts beat long ones. A useful pattern:
*[Action: one clean sentence describing the move.]*
```diff
- HP: 14/20
"[Optional taunt or shout.]"
The colored stat line at the end gives the GM what they need at a glance.
### Emote posts
Pure reaction posts, no dialogue, just an action:
She raised an eyebrow, but said nothing.
Italics-only. Short.
### Multi-character posts (NPCs)
When you control multiple characters in one post, separate them clearly:
Aria: "And what exactly do you want from me?"
The Hooded Figure: It tilted its head, studying her. "Your patience, to start."
Bold name + colon makes it immediately clear who's speaking.
## Stylized character names
Roleplay characters benefit from styled names, especially in fantasy and sci-fi settings. The [Font Transformer](/font-transformer) gives you Unicode styles that survive copy-paste:
| Genre | Style suggestion | Example |
|---|---|---|
| High fantasy | Fraktur (gothic) | 𝔄𝔩𝔡𝔢𝔫 𝔱𝔥𝔢 𝔅𝔯𝔞𝔳𝔢 |
| Royalty / nobility | Bold italic script | 𝓛𝓪𝓭𝔂 𝓥𝓲𝓿𝓲𝓪𝓷𝓮 |
| Sci-fi / cyberpunk | Monospace | 𝙰𝚐𝚎𝚗𝚝 𝙺-𝟸𝟷𝟿 |
| Horror / dark | Zalgo (sparingly) | A̷l̷d̷e̷n̷ |
| Aesthetic / soft | Fullwidth | Ｖｉｖｉａｎｅ |
Don't go heavier than this — entire posts in fraktur are unreadable. Style the **name**, leave the body in plain markdown.
## Status lines and condition tracking
For RP that involves wounds, conditions, or status effects, colored code blocks make tracking much faster than reading paragraphs:
### Active condition
```diff
- Bleeding: -2 HP per turn
Buff or boon
+ Inspired: +1 to next attack
Neutral status
Concentrating: maintaining spell
These can sit at the bottom of an action post or in a separate "status" line.
Common roleplay formatting mistakes
Mistakes that kill immersion, listed in roughly the order they cause problems:
- Mixing OOC and IC without marking it. Other players can't tell if you're talking as your character or as yourself. Always mark OOC.
- Posting walls of unbroken italics. A 1500-character italic block is hard to read. Break paragraphs with blank lines.
- Inconsistent dialogue formatting. Switching between
"quotes",**bold**, and*italic*for spoken lines confuses readers. Pick one per character. - Asterisks left dangling from a copy-paste. A stray
*flips the entire rest of your message into italic. Always preview. - Posting the second half of a split post before the first half lands. Discord can deliver out of order. Number your parts.
- Using fancy fonts for entire posts. Fine for names. Unreadable for paragraphs.
A roleplay-friendly pre-send checklist
Before you press enter, scan your post for:
- Are all
*paired? Same for**,__,~~, and||? - Is the post under 2,000 characters? If not, run it through the Message Splitter.
- Did you mark OOC sections clearly?
- Does the live preview look the way you imagined it?
- If you used a stat block, are the colors right?
If all five check out, you're good. Press send.
Where to go next
- Discord text tools complete toolkit — every tool that helps with RP
- Discord colored text generator — color-coded stat blocks and status lines
- Discord fancy text fonts guide — Unicode styles for character names
- Discord 2000 character limit guide — for when intro posts overflow
- Discord text formatting guide — the underlying markdown reference
Roleplay formatting isn't about being fancy. It's about being readable in the middle of a fast-moving channel. Get the conventions right, preview your post, split when you need to — and the formatting disappears so the writing can stand on its own.