Royal Road Author Discords
Where Royal Road authors find swaps, critique, beta readers, and launch conversations.
Practical angle
Focus on concrete author operations: launch cadence, reader trust, community rules, and evidence-backed planning. Avoid claims that imply ranking outcomes or platform manipulation.
Enter as a participant
Author communities work best when the author participates before asking for anything. Use Discords for craft talk, critique, swaps, and feedback, but read the current server rules before posting links. A launch plan should treat each server as a community with norms, not as a traffic source. The author who shows up only to request swaps or clicks will usually get weaker responses than the author who understands the channel structure, gives useful feedback, and asks specific workflow questions before promotion.
- Observe channel norms before starting a promotion thread.
- Keep swap requests specific and genre-aware.
- Do not DM authors cold unless the community explicitly allows it.
- Use public channels and opt-in threads before private outreach.
Track community context
A community note is as important as a contact name. Record where the conversation happened, what was agreed, and whether the server has self-promotion, critique, or swap-specific channels. This prevents a common launch problem: finding an old Discord conversation three weeks later and not knowing whether a swap was actually agreed, where the snippet should go, or whether the channel allowed that kind of request in the first place.
- Keep Discord and Reddit rule notes separate.
- Use the swap tracker only after a real conversation exists.
- Update notes when server rules or channel names change.
- Record the exact channel or thread where an agreement happened.
What to ask for
Good community asks are specific and easy to answer. Instead of asking people to read an entire story, ask whether the blurb matches the opening promise, whether a shoutout snippet is clear, or whether a launch cadence sounds sustainable. For swaps, include genre, tone, content boundaries, expected date, and where the shoutout would appear. That makes it easier for another author to decide whether the audiences actually fit.
- Ask for feedback on one asset at a time: blurb, hook, cover fit, or schedule.
- For swaps, describe audience fit before asking for dates.
- Keep the request short enough that someone can answer without doing unpaid project management.
- Thank people and record any agreed follow-up immediately.
Red flags to avoid
Avoid anything that looks like mass outreach, review trading, or pressure. Communities built around authors are usually sensitive to promotional behavior because everyone has something to promote. The safest approach is to be transparent, ask for workflow advice, and keep links inside channels where links are allowed. If the server has a dedicated promo or swap channel, use it. If it does not, ask a moderator or do not post the link.
- Do not send the same private message to a list of authors.
- Do not ask for reviews in exchange for reviews.
- Do not hide that a post is about your own launch workflow.
- Do not treat silence as permission to follow up repeatedly.
How to use Discord notes in a launch plan
Discord notes should feed the launch plan without becoming a contact database full of cold leads. Record only useful operational context: server name, relevant channels, rule notes, people who opted into a conversation, agreed swap date, and follow-up status. This keeps the author honest about what actually happened. It also makes the launch less fragile, because agreed swaps and critique promises are not scattered across direct messages, browser tabs, and memory.
- Keep opt-in conversations separate from prospects you have not contacted.
- Record rule notes before drafting a post.
- Use the swap tracker for agreed or credible conversations, not scraping member lists.
- Review the notes weekly and close stale items instead of chasing everyone.
- Copy only the operational summary into the launch plan so private chat context is not exposed or over-shared.
- If a server feels unclear about promotion, keep participating normally and skip the launch ask until the rules are explicit, current, and moderator-visible.