Defines the core community standards of Ash & Blood, including writing and immersion, IC/OOC separation, scene continuity, respectful conduct, good-faith play, LFRP courtesy, zero-tolerance community behavior, reporting procedures and handbook scope.

Introduction

BOOK I
Community & Conduct Guidelines
The Foundation of Every Story

Ash & Blood is a roleplay-first community. These rules define the conduct expected from every player so that the Exiled Lands can remain immersive, fair and enjoyable even when the characters within it are cruel, hostile or divided.

CORE PRINCIPLE
The rule above the rules
“Create stories worth remembering, not victories worth forgetting.”
01
The Foundation

ROLEPLAY
Story First
Roleplay takes priority over mechanics, personal gain and competitive success.
COMMUNITY
Respect
Challenge characters without attacking the people behind them.
GOOD FAITH
Fair Play
Use rules and systems honestly. Do not turn technicalities into unfair advantages.
REMEMBER
Common sense applies to all rules
No rulebook can describe every situation. If a technical reading gives you an unfair advantage, choose the interpretation that best supports fair and believable roleplay. Loophole hunting is not acceptable. If you ever find yourself asking, "The rules don't explicitly forbid this, so can I do it?", you are likely approaching the situation incorrectly. Instead, ask whether your decision contributes positively to the roleplay experience of everyone involved.
Quick Reference
This book covers
  • Community conduct and sportsmanship.
  • Writing and immersion standards.
  • IC and OOC communication.
  • Scene continuity and disputes.
  • LFRP courtesy.
  • Reporting and community-level prohibitions.
Detailed elsewhere
  • Character integrity and emotes › Book II.
  • Combat, escalation and raiding › Book III.
  • Building, clans and followers › Book IV.
  • Thievery and disguise › Book V.
  • Character creation › Book VI.
  • Consent and sensitive content › Book VII.
  • Administration and enforcement › Book VIII.
Ash & Blood Principle
If a decision wins the mechanic but damages the shared story, it is usually the wrong decision.

CHAPTER I — The Community Standard

CHAPTER I
The Community Standard
Collaborative Storytelling Before Competition

Your character may pursue victory. You, the player, are expected to protect the shared experience. Success is measured by the quality of the story created, not by how often your character wins.

01
Core Conduct

01.01
Roleplay before mechanics
Game systems support the story. They must not replace believable roleplay or be used to force an outcome simply because the game allows it, always be realistic.
01.02
Share the spotlight
Give other characters room to speak, act, succeed, fail and influence the direction of a scene.
01.03
Accept setbacks and consequences
Defeat, injury, embarrassment, political loss and failed plans are valid parts of roleplay. Do not erase them because they are inconvenient to you.
01.04
Do not treat yourself as the main character
Your story matters, but so do the stories around you. Avoid monopolizing scenes or forcing every event to revolve around your character.
01.05
Create opportunities, not dead ends
Whenever practical, leave other players meaningful ways to respond, negotiate, resist, recover or continue the story.
01.06
Do not weaponize the rules
Rules exist to protect the community. Do not use them as threats, traps or technical tools for winning disputes.
Encouraged
  • Slow-burning and long-term stories.
  • Meaningful failures and consequences.
  • Sharing attention with other characters.
  • Scenes that create future roleplay.
Discouraged
  • Playing only to dominate or win.
  • Searching for loopholes to your own advantage.
  • Ignoring consequences when inconvenient.
  • Ruining scenes for amusement or personal gain.
Ash & Blood Principle
Even your rivals are collaborators helping to tell your character's story.

CHAPTER II — Writing & Immersion Standards

CHAPTER II
Writing & Immersion Standards
Clear Writing Protects the Shared Atmosphere

Ash & Blood is a text-heavy roleplay server. Players are not expected to write perfect prose, but everyone is expected to communicate clearly enough for others to understand and respond without repeatedly stopping the scene.

02
Writing Standards

02.01
All forms of IC roleplay must be in English
All in-character dialogue and emotes must be written in English. English does not need to be your first language and occasional mistakes are completely acceptable.
02.02
Clarity matters more than perfection
Use reasonable grammar, punctuation and sentence structure. The goal is readability, not literary performance.
02.03
Give others something to respond to
Avoid consistently vague, one-word or low-effort replies that provide no meaningful information during an active scene and avoid shotgunning emotes..
02.04
Match the pace of the scene
Avoid unnecessarily large walls of text during fast-moving scenes. Give others a fair chance to read and respond before the scene moves on.
03
Immersion Standards

02.05
Keep IC language appropriate to the setting
Do not use modern internet slang, memes, emojis, contemporary gaming terminology or obvious real-world references in-character.
02.06
Do not deliberately break the tone
Comedy is allowed, but intentionally anachronistic or immersion-breaking behavior should not disrupt the grounded Hyborian atmosphere.
02.07
Live AI-generated roleplay is prohibited
AI tools may not generate your dialogue, reactions, emotes or decisions during an active roleplay scene. Spell-checking, grammar correction and proofreading of text you wrote yourself are permitted but not recommended, it's much better for you to do mistakes and learn from them than have a machine correct them for you.
Clear and immersive
  • Readable dialogue and emotes.
  • Setting-appropriate wording.
  • Responses paced for the scene.
  • Proofreading your own writing when needed.
Immersion breaks
  • Memes, emojis or internet slang IC.
  • Modern gaming terms used as character speech.
  • Unmarked real-world discussion.
  • Copy-pasted AI roleplay replies.
WRITING STANDARD
Quality does not mean perfection
Ash & Blood is an international community. Good writing means being understandable, considerate and responsive. It does not require flawless English or elaborate prose.

CHAPTER III — IC, OOC & Information Separation

CHAPTER III
IC, OOC & Information Separation
Keep the Character Separate From the Player

Characters act on what they know. Players know far more. Protecting the line between those two perspectives is essential to believable roleplay.

04
Communication

03.01
Remain in character all the time.
While actively playing, communicate through your character unless an OOC message is genuinely necessary.
03.02
Mark OOC with double parentheses
Brief local OOC communication must be clearly marked with ((double parentheses)).
03.03
Use clan chat, private channels or Discord for general OOC
Local OOC is for short necessities such as a brief absence or immediate technical clarification. Longer discussions belong in the private Tot!Chat feature or the appropriate Discord channel.
03.04
Unmarked local communication is IC
If a message or action is not clearly identified as OOC, players may treat it as entirely in-character... as a rule of thumb, every action and message in the local chat will be treated as IC.
05
Information Separation

03.05
Use only information your character learned
Information from Discord, streams, screenshots, private messages, websites, character sheets or OOC conversation cannot become IC knowledge unless your character learns it through roleplay... avoid metagaming.
03.06
Do not selectively forget
Established events, relationships, promises and consequences remain part of your character's history unless a legitimate story explains otherwise.
03.07
Do not use OOC knowledge to avoid danger
Knowing as a player that a person, location or plan is dangerous does not automatically give your character that knowledge.
Quick Reference
Appropriate local OOC
  • (( BRB, answering the door. ))
  • (( Sorry I crashed, let's continue. ))
  • A brief accessibility or technical clarification.
Move elsewhere
  • Game-mechanic discussions.
  • Rule debates.
  • General conversation.
  • Extended explanations or planning.
PROHIBITED
Metagaming
Knowing something as a player does not mean your character knows it. If the information was not earned in-character, behave as though your character is genuinely unaware of it.

CHAPTER IV — Scene Continuity & Rule Disputes

CHAPTER IV
Scene Continuity & Rule Disputes
Do Not Turn Active Roleplay Into a Rules Argument

Ordinary rule disagreements should be handled after the scene. Preserving continuity gives staff better context and prevents a minor dispute from disrupting everyone involved.

06
During an Active Scene

04.01
Do not pause for an ordinary rule dispute
Only staff may pause a scene for a normal rules disagreement. Continue roleplay whenever it is reasonable and safe to do so.
04.02
Do not 'ruleplay'
Do not quote rules, declare another player's actions invalid or attempt to moderate them during the scene.
04.03
Accept the immediate scene and preserve evidence
Continue the roleplay, take screenshots or recordings and report the issue afterward. If a violation is confirmed, staff may correct or retcon the outcome where appropriate.
04.04
No public backseat moderation
Do not publicly police other players. If a minor correction is genuinely helpful, discuss it privately after the scene; otherwise use a staff ticket.
04.05
Do not threaten reports
Statements such as “I'm reporting you” should not be used to pressure another player or influence the scene.
07
Resolution Process

STEP 01
1. Continue
Keep the roleplay moving whenever reasonably possible.
STEP 02
2. Preserve
Capture screenshots, video or relevant logs.
STEP 03
3. Finish
Let the scene reach a natural stopping point.
STEP 04
4. Report
Open one clear staff ticket with the evidence.
EXCEPTION
Consent boundaries are an immediate exception
If an established consent boundary is ignored and the ongoing scene makes you uncomfortable, you may immediately pause using ((OOC)), state that the boundary has been crossed and contact staff. Full consent and sensitive-content rules are defined in Book VII.
EXCEPTION
Other immediate exceptions
A scene may also be interrupted when staff instructs you to stop, a serious safety or harassment issue requires intervention, or a technical failure makes continuing impossible.

CHAPTER V — Respect, Sportsmanship & Good Faith

CHAPTER V
Respect, Sportsmanship & Good Faith
Challenge Characters Without Targeting Players

Intense character conflict is welcome. Personal hostility is not. Players are expected to communicate respectfully and to participate in good faith even when their characters are bitter enemies.

08
Respect & Sportsmanship

05.01
Keep IC and OOC conflict separate
Character hatred does not justify hostility toward the player, and OOC dislike does not justify in-character retaliation.
05.02
No harassment, baiting or personal attacks
Do not insult, provoke, intimidate or repeatedly antagonize another player OOC.
05.03
No OOC retaliation
Do not target, exclude, punish or sabotage another player's character because of a report, Discord disagreement or personal grievance.
05.04
Assume misunderstanding before malice
Most disputes begin with different interpretations or mistakes. Ask calmly before accusing another player of deliberate misconduct.
05.05
Know when to disengage
If a discussion is becoming hostile, stop the argument and use staff channels rather than escalating it publicly.
05.06
Respect disengagement
If someone asks to end an OOC conversation, stop contacting them about the dispute and use the appropriate staff process if the issue still requires resolution.
09
Good Faith

05.07
Do not exploit loopholes
An omission, ambiguous sentence or technical gap does not grant permission to gain an unfair advantage.
05.08
Do not exploit obvious mistakes
An accidental unlocked door, misclick, bug or similar oversight is not automatically an invitation to take advantage of another player.
05.09
Report exploits instead of abusing them
If you find a bug, unintended mechanic or server vulnerability, report it privately rather than using it for personal, clan or economic gain.
05.10
Do not engineer unavoidable outcomes
Do not manipulate rules, mechanics or OOC circumstances to trap another player in an outcome they had no reasonable opportunity to engage with.
Good sportsmanship
  • Thank players after difficult scenes.
  • Accept defeat without OOC hostility.
  • Communicate calmly after misunderstandings.
  • Help new players learn the community.
Bad faith
  • Loophole hunting.
  • Mechanical exploitation.
  • Retaliatory targeting.
  • Public dogpiling or callout campaigns.
Ash & Blood Principle
Strong conflict creates more story. Personal hostility destroys it.

CHAPTER VI — Community Courtesy & LFRP Markers

CHAPTER VI
Community Courtesy & LFRP Markers
Discovery Tools Should Not Become Information Tools

LFRP markers exist to help players find interaction. Once interaction has been found, the marker has normally completed its purpose.

10
LFRP Marker Protocol

06.01
Turn off LFRP when roleplay begins
As a general courtesy, disable your LFRP marker once you have found an active roleplay scene.
06.02
Do not use markers to reveal an active scene
Leaving markers active during private, tense or sensitive scenes can unintentionally expose player locations and create metagame information.
06.03
Honor requests to disable a marker
During an active scene, an LFRP marker must be turned off when another participant asks for it to be disabled.
06.04
Group-finding is a valid exception
A group actively assembling players for a PvE journey or open social activity may keep LFRP markers enabled while it is still seeking participants.
11
Everyday Courtesy

06.05
Do not intentionally disrupt nearby roleplay
Avoid unnecessary OOC noise, repetitive spam, deliberate immersion-breaking behavior or actions intended only to interfere with someone else's scene.
06.06
Give players reasonable time to respond
Text roleplay takes time. Do not deliberately rush another player through ordinary conversation or use their typing time against them.
06.07
Respect AFK and technical interruptions
A brief, clearly marked OOC absence or crash should not be treated as an IC opportunity.
COURTESY
What LFRP is for
LFRP is a discovery aid for players who are looking for interaction. It is not intended to function as a permanent location beacon once roleplay is underway.

CHAPTER VII — Zero-Tolerance Community Conduct

CHAPTER VII
Zero-Tolerance Community Conduct
Some Behavior Is Incompatible With the Community

The following conduct may justify immediate administrative action. Book VII contains the detailed consent and sensitive-content framework; this chapter establishes the community-wide baseline.

12
Community Prohibitions

07.01
PROHIBITED
Harassment or stalking
Repeated unwanted contact, cross-platform pursuit, intimidation, coordinated targeting or continuing personal contact after someone has asked you to stop.
07.02
PROHIBITED
Doxxing or threats to expose private information
Do not reveal, threaten to reveal or distribute another person's private identifying information without permission.
07.03
PROHIBITED
Real-world hate speech or discrimination
Real-world slurs, hate speech or harassment targeting race, ethnicity, religion, nationality, sex, gender, sexuality or identity are prohibited.
07.04
PROHIBITED
Minors in graphic or sexual content
Graphic or sexual roleplay, depictions or references involving minors are prohibited.
07.05
PROHIBITED
Sexual content involving animals
Roleplay depicting, encouraging or describing sexual acts involving animals or beasts is prohibited.
07.06
PROHIBITED
Mockery of serious real-world trauma
OOC jokes, mockery or trivialization of rape, sexual assault, self-harm or comparable real-world trauma are prohibited.
07.07
PROHIBITED
Glorification of real-world extremist atrocities
Do not use the community to glorify extremist ideologies, real-world atrocities or graphic historical tragedies.
07.08
PROHIBITED
Moderation evasion
Do not use alternate accounts, third parties or other methods to bypass an active restriction, suspension or removal.
07.09
PROHIBITED
Staff impersonation
Do not falsely present yourself as staff, fabricate staff instructions or claim administrative authority you do not have.
07.10
PROHIBITED
Coordinated harassment or dogpiling
Do not organize others to isolate, pressure, mass-message, mass-report or repeatedly target another community member.
ZERO TOLERANCE
Harassment is never roleplay
Roleplay cannot be used as a shield for conduct aimed at the player. Legitimate character conflict and targeted personal harassment are not the same thing.
CROSS-REFERENCE
Sensitive-content rules continue in Book VII
This chapter states the community baseline. Consent sheets, restricted themes, withdrawal of consent, permanent harm and other sensitive-content procedures are governed by Book VII.

CHAPTER VIII — Reporting Violations

CHAPTER VIII
Reporting Violations
Clear Evidence Produces Better Decisions

Reports exist to protect the community, not to win disagreements. Submit them through the official process, keep them factual and preserve enough context for staff to understand what occurred.

13
How to Report

08.01
Use the official Discord ticket system
Rule reports must be submitted through the designated ticket process so they can be documented and reviewed by the appropriate staff members.
08.02
Do not DM staff unless instructed
Unsolicited direct messages about reports may be redirected or ignored. Use the ticket system unless a staff member specifically asks you to contact them elsewhere.
08.03
Submit one complete report
Duplicate tickets, mass reports and public campaigns do not strengthen a case and may delay review.
08.04
Be factual and concise
Explain what happened in chronological order without insults, speculation or exaggerated claims.
08.05
Include relevant evidence
Provide screenshots, recordings, logs, timestamps and names whenever available. Preserve enough surrounding context to show what happened.
08.06
Separate witnessed facts from hearsay
Clearly distinguish what you personally observed from information another person told you.
08.07
Do not manipulate evidence
Fabricating evidence, selectively editing context or deliberately withholding critical information is a serious violation.
08.08
Keep active investigations private
Do not publicly argue the case, pressure staff, rally supporters or attempt to influence the outcome while a report is under review.
14
What a Useful Report Contains

What happened
A short, chronological description of the incident.
Who was involved
Names of the players or characters directly involved.
When it happened
Approximate date and time, plus location or scene if relevant.
Evidence
Screenshots, recordings, logs and any context needed to understand them.
IMPORTANT
Opening a ticket does not guarantee punishment
Every report is reviewed individually. Staff may determine that no violation occurred, that evidence is insufficient or that a different response is appropriate.
WARNING
False or retaliatory reports
Knowingly submitting false information, fabricated evidence or intentionally misleading context, or using reports to harass another player, may itself result in disciplinary action.

CHAPTER IX — Rule Interpretation & Handbook Scope

CHAPTER IX
Rule Interpretation & Handbook Scope
How Book I Connects to the Rest of the Ruleset

Book I establishes the shared behavior expected from everyone. More specific rules in later books apply in addition to these standards.

15
How Rules Are Read

09.01
The spirit and wording both matter
Players are expected to follow the written rule and its clear purpose. A technical loophole does not override the intended standard.
09.02
Specific rules take priority in their subject area
When another book contains a more specific rule for the situation, follow that book together with the general conduct standards in Book I.
09.03
No handbook can list every abuse
Conduct that clearly undermines fair roleplay, community safety or the intended function of a system may still require staff review even if the exact method is not named word-for-word.
09.04
Follow direct staff instructions
When staff gives a lawful moderation instruction during an incident, follow it first and raise disagreements through the proper review or appeal process afterward.
09.05
Do not evade a restriction or ruling
An active restriction remains in effect until it expires or is formally changed through the appropriate process.
16
Where Older Rules Now Live

CHARACTERS
Book II
Character integrity, emotes, physical roleplay, powergaming and storytelling standards.
CONFLICT
Book III
Combat escalation, PvP conduct, raiding and conflict etiquette.
BUILDING
Book IV
Architecture, building limits, clans and follower management.
THIEVERY
Book V
Thievery, disguise and related deception systems.
CREATION
Book VI
Character creation, starting status, lore fit, progression and believable concepts.
BOUNDARIES
Book VII
Consent, player boundaries, restricted themes and sensitive content.
ADMIN
Book VIII
Administrative process, sanctions, appeals and enforcement procedure.
HANDBOOK STRUCTURE
Why this matters
Older versions of the rules placed emotes, combat, character creation, consent and administrative procedures inside one large community document. Those rules are not being discarded. They are separated into the dedicated books above so each subject can be explained once, clearly and without duplication.
Quick Reference
Book I in practice
  • Write clearly and stay immersive.
  • Separate IC from OOC.
  • Protect scene continuity.
  • Respect other players.
  • Act in good faith.
  • Report problems properly.
When unsure
  • Do not exploit ambiguity.
  • Choose the fairer interpretation.
  • Check the relevant specialist book.
  • Use a staff ticket if clarification is still needed.
Ash & Blood Principle
Every scar tells a story. Every oath has a price. The rules exist so those stories can be told together.