ROLEPLAY GUIDES

1.1 What is Roleplay (RP)?

Roleplay is the art of embodying a fictional character in a narrative or interactive setting, while respecting rules established by a server or community. In a universe like Dead Space RP, this means living through the eyes of a crew member of the USG Horizon, while respecting the lore and the specific social interactions of that environment.

Some examples of why we do RP:

• Immersion: To dive into a universe and live a unique story.
• Collaborative storytelling: You co-create narratives with other players.
• Personal development: Playing a role helps improve your creativity and social skills.

1.2 Difference between Narrative RP, Passive RP, and Active RP

Narrative RP:
Telling a story through rich actions and dialogues, often long and detailed. Ideal for background scenes like philosophical discussions or flashbacks.

Passive RP:
Portraying simple, realistic moments of life.
Example: An engineer performing maintenance on equipment, or a miner eating a meal.
This type of RP is encouraged because it strengthens immersion and allows you to better understand other players' characters.

Active RP:
Fast-paced, intense actions, such as altercations or crises. While spectacular, it should not dominate, to maintain balance with Passive RP.

Example of Passive/Active balance:

• Passive: You repair a console while chatting with a colleague about rising tensions between the CEC and the Unitologists.
• Active: An alarm triggers a short circuit; you must react quickly to save the situation while interacting with other players.

1.3 Basic Terminology

Terms related to RP behaviour

Prop kill
Definition: Unrealistic or abusive use of props/objects in-game.
Avoid: Carrying a massive steel beam alone with no equipment or RP explanation.
Correct: Call a team to help or use appropriate tools.

Metagaming
Definition: Using out-of-character (OOC) information in an in-character (IC) scene.
Avoid: Learning via Discord that a Unitologist is plotting in a room and instantly sending security there.
Correct: Wait for your character to receive this info through an RP scene.

Powergaming
Definition: Forcing an action or outcome without letting the other player respond.
Avoid: "I punch you and knock you out instantly."
Correct: "I try to punch you in the jaw to disorient you."

Fairplay
Definition: Playing fairly, even if it doesn't benefit your character.
Example: Accepting that your character is injured or in trouble if the scene justifies it.

Consistency
Definition: Your actions must be realistic for the game universe and respect the lore.
Example: A maintenance engineer doesn't have the skills to defuse a complex bomb without a logical explanation.

Character Kill (CK)
Definition: Permanent death of a character after a significant RP scene.
Rule: Always discuss CK with admins and involved players beforehand.

Random Death Match (RDM)
Definition: Killing a character without valid RP reason.
Avoid: Shooting a colleague after a minor RP disagreement.

Player Kill (PK)
Definition: Temporary or non-permanent death of a character. PK may be lifted if context allows.

2.1 Respect for the Universe and Lore

All RP must remain consistent with the Dead Space universe.

• The timeline, factions (CEC, Unitology, EarthGov, etc.), and technologies must be respected.
• Introducing elements from other universes (Star Wars, Halo, Marvel, etc.) is prohibited.

2.2 Respect for Players and Characters

• Treat other players with respect, whether IC (in-character) or OOC (out-of-character).
• Avoid toxic behaviour OOC — conflicts between characters must remain in the RP context.
• Never mix IC and OOC to target someone personally.

2.3 Communication and Language

• IC: Use the vocabulary appropriate for your character's background (a miner won't use the same jargon as a CEC engineer).
• OOC: Keep communications clear and avoid spamming in voice or text chat.
• English is the main language for RP on the server unless a scene justifies another language.

2.4 RP Initiatives and Consent

• Before starting a major or sensitive RP scene (torture, CK, hostage-taking, etc.), obtain the consent of the involved players and admins.
• Respect "fade to black" if certain RP scenes are too explicit or uncomfortable.

2.5 Weapons and Combat RP

• Always give the other player time to react to your actions.
• Use /me or /it to describe attacks and consequences when possible.
• Firearms should be used logically — running around shooting without reason breaks immersion.
• Ammunition and weapon availability must follow the server's scarcity rules.

2.6 Injuries and Medical RP

• Injuries must be logical based on the situation.
• Healing should not be instantaneous unless justified (advanced med-gel, stasis-assisted surgery, etc.).
• Characters should carry visible scars or consequences from major injuries.

2.7 Faction-Specific Rules

• CEC Personnel: Must follow corporate hierarchy and prioritise resource extraction and safety protocols.
• Security / EarthGov: Must respect chain of command and use force proportionally.
• Unitologists: Must operate discreetly or manipulatively; overt aggression is rarely their first move.
• Miners / Technicians: Focus on work-related tasks, but can get involved in larger events logically.

2.8 Environment Interaction

• Avoid "magical" solutions — use the tools, skills, and methods your character would logically have.
• Damaging the ship or colony without admin approval is forbidden.
• Keep in mind that in the Dead Space universe, repairs and supplies are limited.

3.1 Creating Your Character

When creating a character, you must ensure they are believable within the Dead Space universe and fit into the server's lore.

Steps to create your character:

1. Choose a role: Engineer, miner, security officer, medic, Unitologist, etc.
2. Define their background: Where were they born? What led them to work for the CEC or join the Unitologists?
3. Establish personality traits: Are they ambitious? Paranoid? Altruistic?
4. Determine skills and weaknesses: Keep it balanced. A character who is good at everything quickly becomes uninteresting.
5. Appearance and style: Keep it consistent with the universe — industrial clothing, EVA suits, work uniforms, etc.

3.2 Avoiding Common Character Creation Mistakes

• The "Lone Wolf" problem: If your character avoids interaction, you'll miss out on RP opportunities.
• Overpowered backgrounds: "I'm a super soldier with advanced training in everything" is unrealistic for most roles.
• Modern pop culture references: No "Marvel fanboys" or "anime obsessives" unless they are justified in-universe (and kept subtle).

3.3 Character Development in RP

Your character should evolve based on events that happen on the server.

• If they witness a necromorph attack, they might develop paranoia or PTSD.
• If they're promoted, they might take on more responsibilities or become more authoritarian.
• Relationships matter — friendships, rivalries, and alliances shape personality over time.

3.4 Backstory Integration

Don't dump your entire backstory at once. Reveal details naturally in conversations and actions.

Example: Instead of saying "I was in the colony disaster of Titan Station" immediately, let it come up in a moment of stress when your character is explaining why they hate confined spaces.

3.5 Playing Weaknesses Realistically

Flaws make characters more interesting.

• A nervous security officer might hesitate to fire.
• An engineer might be brilliant at fixing machinery but bad at social interaction.

4.1 CEC (Concordance Extraction Corporation)

The CEC is a massive mining and resource extraction corporation. On the server, CEC personnel form the backbone of daily operations.

RP Guidelines:

• Follow strict corporate protocols and safety procedures.
• Prioritize resource extraction and the functioning of the ship/station.
• Maintain professionalism, even under stress — corporate image is important.
• Report any suspicious activity to Security, but avoid acting like a security officer unless it's part of your job.

RP Opportunities:

• Maintenance and repairs.
• Cargo and logistics management.
• Research and engineering projects.
• Corporate politics and internal disputes.

4.2 Security / EarthGov Forces

Security maintains order and enforces laws aboard the vessel or colony. EarthGov presence means strict authority and oversight.

RP Guidelines:

• Respect the chain of command — orders flow from superiors down.
• Use force only when justified and proportional.
• Conduct regular patrols and inspections.
• Interact with civilians calmly; intimidation without reason is discouraged.

RP Opportunities:

• Criminal investigations.
• Guarding important assets or personnel.
• Negotiations with factions like the Unitologists.
• Crisis response during necromorph events.

4.3 Unitologists

Unitology is a religious movement centered on the belief that the Markers are divine artifacts. On the server, Unitologists often operate secretly or under the guise of normal crew members.

RP Guidelines:

• Avoid public, aggressive recruitment — operate subtly.
• Gather information and influence others through conversation and persuasion.
• Support your fellow Unitologists in secret meetings or coded communications.
• In crisis situations, interpret events as "signs" from the Marker.

RP Opportunities:

• Covert planning and sabotage.
• Infiltrating CEC ranks or other factions.
• Religious debates with non-believers.
• Organizing secret gatherings.

4.4 Miners and Technicians

The labour force that keeps operations running. They are often overworked, underpaid, and exposed to dangerous conditions.

RP Guidelines:

• Stay focused on your tasks, but allow for downtime interactions with colleagues.
• Voice concerns about working conditions or safety hazards.
• Create bonds with other workers; unity matters in dangerous jobs.

RP Opportunities:

• Team-based mining expeditions.
• Discovering anomalies during work.
• Workplace disputes or strikes.
• Repairing essential ship/station systems.

5.1 What is an Event in RP?

An event is a scripted or improvised situation designed to break the routine and create unique interactions. On a Dead Space server, events can range from small technical problems to full-scale necromorph outbreaks.

Event Types:

• Minor events: Power failures, missing equipment, disputes between factions.
• Medium events: Cargo bay accident, reactor instability, medical emergency.
• Major events: Necromorph infestation, major sabotage, full evacuation.

5.2 Player Responsibilities During Events

• Follow the tone and pacing of the scene.
• Avoid "breaking" the event with unrealistic actions.
• Let the event develop naturally — not every situation needs an instant solution.

5.3 Necromorph Outbreak Protocols

When necromorphs appear, panic is normal — but there are RP rules to keep scenes fun and believable.

General Guidelines:

• Necromorphs are extremely dangerous. Even trained security should be cautious.
• Civilian characters should prioritize hiding or fleeing, not fighting head-on.
• If your character is infected or fatally wounded, coordinate with staff to play out the scene logically (CK, PK, or medical intervention).
• Use the ship's or station's design for creative scenes — blocked corridors, ventilation shafts, locked blast doors.

Example RP Flow:

1. Alarms sound; the ship enters emergency lockdown.
2. Security attempts to cordon off infected areas.
3. Engineers reroute power to critical systems.
4. Civilians evacuate to safe zones.
5. The outbreak either gets contained or forces evacuation.

5.4 Sabotage and Covert Operations

These are player-driven events where stealth and planning are essential.

Key RP Points:

• Don't sabotage without an IC reason.
• Give other players a chance to notice or respond.
• Avoid instant "big destruction" — build tension over time.

5.5 Medical and Rescue Events

Medical RP is an opportunity for detailed, immersive storytelling.

• Use believable injury descriptions and treatments.
• Include time for diagnosis, surgery, or recovery.
• Rescue operations should involve teamwork and coordination.

5.6 Admin-Run vs Player-Run Events

• Admin-run: Often large-scale, impacting the whole server.
• Player-run: Smaller, more personal stories between a few characters.
• Both are valuable and can be combined for depth.

6.1 Passive vs Active

• Passive: Calm moments (dialogue, exploration, daily tasks). Builds immersion and reveals character depth.
• Active: High tension (combat, alarms, sabotage). Advances story and forces quick decisions.

6.2 Why Passive Matters

• Deepens character psychology and reveals backstory.
• Builds authentic crew life (maintenance, meals, casual talks).
• Strengthens relationships, alliances, or rivalries that affect later actions.

6.3 Why Active Matters

• Pushes the story forward through danger or crisis.
• Strengthens teamwork under stress (repairs, security, evacuation).
• Creates suspense and motivation with high stakes.

6.4 Balancing the Two

• Alternate naturally: quiet moments after chaos, tension built from calm.
• Plant seeds in passive scenes (e.g., data anomaly) that bloom into active events (system failure).
• Keep transitions smooth to maintain immersion.

6.5 Example Flow

• Passive: Crew meeting in archives about Aegis VII findings.
• Transition: A character notices anomalies in planetary data.
• Active: Emergency alarm sounds, attack begins, crew must act quickly.

7.1 Importance of Relationships

Characters don't exist in isolation. Their connections with others shape their development, influence decisions, and generate drama. Building relationships also makes RP more immersive and long-lasting.

Examples:

• A miner constantly arguing with security about safety rules.
• A Unitologist trying to recruit or subtly manipulate a colleague.
• A medic growing attached to patients after repeated rescues.

7.2 Types of Relationships

• Friendships: Provide trust, support, and shared goals. They give reasons to act selflessly.
• Rivalries: Fuel conflict and tension. Rivalries should stay IC and never bleed into OOC.
• Professional ties: Work hierarchies (CEC chain of command, Security ranks) add realism.
• Romantic ties: Allowed if handled maturely and with consent. Avoid making romance the only focus.

7.3 Interaction Techniques

• Use dialogue to reveal character flaws, fears, or ambitions.
• Show consistency: a paranoid engineer will remain suspicious, even in casual conversations.
• Body language and behavior matter: short responses, hesitation, or nervous habits enrich RP.

7.4 Conflict RP

• Conflict is essential for drama but should remain respectful.
• Always give the other player options to respond.
• Don't force outcomes — conflict should create RP, not shut it down.
• A disagreement can escalate into sabotage, betrayal, or grudging respect.

7.5 Cooperation RP

• Collaboration also creates strong RP opportunities.
• Joint missions (mining ops, security patrols, medical rescues) bring characters together.
• Shared successes or failures can strengthen bonds or deepen tensions.
• Even rivals may cooperate when survival is at stake.

8.1 The Nature of Improvised RP

No matter how much you plan, RP often takes unexpected turns. A character might make a surprising decision, or an event may spiral out of control. Improvised RP keeps the world alive and unpredictable, but it requires adaptability and respect for others.

8.2 Player Reactions

• Stay in character even when surprised — don't break immersion with OOC frustration.
• Use unexpected moments to enrich your character rather than resist them.

Example: If your character is falsely accused, use it to develop paranoia, mistrust, or determination to clear their name.

8.3 Admin and Event Team Role

• Admins may introduce sudden twists (sabotage, system failures, or necromorph outbreaks).
• Accept these as opportunities, not obstacles.
• If something feels unfair, resolve it OOC after the scene rather than interrupt RP.

8.4 Turning Surprises into Storytelling

Unexpected events create memorable stories.

• A minor error in maintenance could trigger a chain reaction leading to a full emergency.
• A Unitologist recruit might reveal their allegiance in a crisis, shocking the crew.
• A random encounter in a corridor can evolve into a long-lasting rivalry or alliance.

8.5 Tips for Adaptability

• Listen actively: build off what others bring to the scene.
• Avoid blocking RP: don't shut down another player's idea outright — find ways to incorporate it.
• Be flexible with your character's arc: allow them to grow from failure as much as from success.

9.1 Building a Long-Term Arc

Your character should evolve across weeks of RP, shaped by successes, failures, and relationships. A long-term arc makes RP feel alive and gives weight to daily interactions.

Examples of arcs:

• An overconfident security officer slowly becomes more cautious after repeated near-death experiences.
• A miner who distrusts Unitologists eventually joins them after months of persuasion.
• A medic who starts as an optimist grows jaded by repeated trauma cases.

9.2 Consistency Over Time

Stay consistent with past events. Characters should remember injuries, conflicts, and promises. If they forget everything each session, immersion is broken.

Tip: Keep a small log of key events that shaped your character (injuries, betrayals, promotions, etc.).

9.3 The Role of Conflict and Drama

Long-term arcs thrive on conflict. Rivalries, faction tension, or internal doubts give you material for weeks of RP.

• Don't aim for constant victory; defeats and setbacks create depth.

Example: A character betrayed by a colleague might act more paranoid, affecting every interaction.

9.4 Relationships in Long-Term Arcs

Evolving relationships are central to storytelling. Friendships can turn into rivalries, romances into tragedies, or colleagues into bitter enemies. These shifts should feel gradual and natural, not forced.

9.5 Closure and Endings

Not every arc needs a happy ending.

• A character may die (CK) at the peak of their story, leaving a strong memory.
• Others may retire, transfer, or leave the colony/ship logically.
• Endings provide space for new characters and fresh stories.

10.1 Purpose of /me

The /me command describes your character's actions, expressions, or tone beyond dialogue. It enriches immersion by showing what can't be conveyed through words alone.

Examples:

• /me wipes the sweat from his forehead while checking the reactor console.
• /me lowers her voice, glancing nervously at the corridor behind her.

10.2 Purpose of /it

The /it command is used to describe environmental details or effects visible to everyone. It helps create atmosphere and sets the scene.

Examples:

• /it The lights flicker as the sound of grinding metal echoes through the corridor.
• /it A faint smell of burnt flesh lingers in the medbay.

10.3 Best Practices

• Keep descriptions clear and concise — avoid writing entire paragraphs in a single emote.
• Don't control another player's character in your /me or /it. (Bad example: /me punches John and breaks his nose instantly.) Instead, allow interaction: /me swings a fist toward John's face.
• Use them to enhance immersion, not to "win" a situation.

10.4 Why They Matter in Dead Space RP

The Dead Space atmosphere thrives on details: fear, tension, and paranoia. Using /me and /it effectively lets players experience the claustrophobic, decaying environment as if they were truly there.

Example Flow:

• /me tightens his grip on the plasma cutter, breathing heavily.
• /it The hallway beyond is silent, except for the faint scratching of something in the vents.
• Dialogue and action flow naturally from there.