A roleplay atlas where every story has its own world, its own rules, its own voice.
Bring your world to life. The Atlas is free, forever.
Build your world, set your rules, invite your writers.
#lf-nav-modal).Character biography will appear here once created.
Character relationships will appear here.
Recent posts will appear here.
Character gallery will appear here.
Fill out the fields below. Changes save to your profile instantly.
Read the core pages for the atlas.
Loading designs…
Loading suggestions…
Changes are saved immediately when you click Save.
Send a direct message to another writer
Choose how character profiles are structured. All modes are fully customisable with admin CSS.
Apply a visual theme to character profiles. Works with any display mode above. Inspired by popular RP forum designs.
These shapes apply to the live profile and the preview together, so you can style each display mode with the exact avatar treatment you want.
Choose how category headers are placed on the fable front page. These settings apply to regular, tabbed, and large-banner categories.
Types shown when a writer creates a new thread. Each has a label, description, and a color tag.
This information appears on the Fable Atlas hub front page and in the recruitment listing.
Direct image URL shown as the fable card banner on the hub. Ideal size: 700×400px.
Shown on the hub card. Keep under 160 characters.
Shown when a visitor clicks your fable card. BBC supported.
Rename the currency for your fable. This name appears in shop prices, post footers, and character profiles.
A single character or emoji shown before prices. Examples: ◆ ★ 💎 ⚡ 🌙
How much currency new members receive when they join.
Set minimum words to 0 to reward every post. Otherwise, a post must meet or exceed that word count.
Set automatic badges for reaching a number of posts. Use text pips, emoji, or an image URL for each milestone.
Choose how author info and post content are arranged.
Admins can create one-click toolbar buttons and custom BBCode tags here. Writers use the resulting button or BBCode tag in their posts - they do not need to write raw HTML in posts.
One-parameter tag: [style1]writer text[/style1]
In this case, (PARAM1) = the writer's text between the tags.
Two-parameter tag: [style1=Header Text]writer body text[/style1]
In this case, (PARAM1) = the value after the equals sign, and (PARAM2) = the text between the opening and closing tags.
Enable Use admin HTML conversion on a custom tag, then set a template such as:
<div class="PostStyle1out">
<div class="PostStyle1title">(PARAM1)</div>
<div class="PostStyle1in">(PARAM2)</div>
</div>Writers would use:
[style1=Header Text]Writer body text[/style1]That renders only inside the post output. It does not change the Atlas page layout, admin UI, or saved forum data outside the post content itself.
Custom BBCode HTML is sanitized before render. Script tags, forms, embeds, event handlers, and javascript: URLs are stripped.
If an admin tries to include blocked markup, it is removed so the code only affects the rendered post content.