CROSSROADS    Rules      Consequence Rules

CONSEQUENCE RULES

CONSEQUENCE RULES

---

All rules are subject to change, however will be posted and documented in the discord until the website can be updated. Thank you for your consideration. ~Staff.

The best development comes from various types of failure. It doesn’t matter if the failing is a task gone wrong, missing your mark, or conflict with another character, the experience will end in a drawback for your character. These drawbacks are considered consequences which start a road towards further developing your character.
This page will guide you through not only PvP conflict but also any type of natural consequence your character may face. There are numerous ways you can flavor your roleplay and progress your character through consequences. This page will offer a set of rules and guidelines for IC consequences.

i. IC choices & IC consequences

It is recommended to think through each situation for the best way to proceed. Your character's actions will result in consequences. Whether good or bad, consequences that come from an IC choice are to be played out.

ii. Player Stories

Each consequence needs to appropriately match the error made by the character and applied so that story can continue for every player involved. Consequences should not be given with the goal of ending someone's story or being the winner. Players are here to create stories and appropriate consequences should drive meaningful story and progression.

It is important to remember that communication is paramount to any encounter with another player. The player is required to send a direct message communicating with the other party, especially if there will be consequences involved after a PvP encounter. You can use the command /channel player name in game or send a message in discord, if you have permission from the other player. Lack of clear communication will result in conflict, both in and out of character.

iii. Respect Consent

Crossroads uses consent sheets to represent what each character is and isn’t comfortable with roleplaying. Not all players are comfortable with certain heavy scenarios such as; torture, dismemberment, rape, and sexual assault. Any roleplay that is graphic or sexual in nature needs to be discussed out of character before the roleplay occurs and consent given for it to proceed.

FADE TO BLACK

Fade-To-Black (FTB) is when a victim requests to forgo the roleplay of the consequence allotted. All FTB requests are required to be honored by the aggressor and attempting to coerce or force a player to roleplay out certain scenarios will not be tolerated and will result in severe disciplinary action.

FADE TO BLACK CONSENT ABUSE

Players are not allowed to abuse consent rules or FTB to bypass consequences. The agreed upon consequences of a scene DO happen, whether or not the roleplay is played out. Anyone who abuses these rules will receive disciplinary action. If either party has questions or concerns about a scene, please open a moderation ticket with screenshots referencing your concerns.

iv. Consequence Options

There are numerous options for consequences and they do not have to always lead to a large, dramatic end to story. Below are a few possible options, but not a complete list:

CAPTIVE RP

In captive RP, there are responsibilities for both the captor and captive. The captor is required to provide RP for the captive. If 30 minutes go by without any RP from the captor, the captive is allowed to leave the scene. The captive is responsible for communicating to their captor when they are present and if they are unhappy with how the roleplay is developing. Clear communication is required from both parties as well as following the consent rules. Roleplay should be about advancing a story for both individuals involved.

LEFT FOR DEAD

Left for Dead (LFD) allows characters to disengage from the conflict without permanently ending a character's story. The winner of the conflict would believe that the other character is dead and is left behind. The downed character, not actually being dead, could then continue on with their story. They would also need to be careful with their actions given that the winning character thinks they are dead. It is important to remember that being LFD does not reduce the severity of the consequences inflicted upon your character should you come face to face with your attempted killer again.

THEFT

Another avenue is stealing from the character who was downed. In a PvP conflict, the winner could use theft as a consequence, stealing from the losing character. Please see the Tracking & Theft for further steps in this process.

v.PLayer Death

Permanent Death can be explored with significant conflicts that have grown to a critical point in the character’s story. Character death should be proceeded with caution and a last resort for conflict. A ticket is required to request the ability to potentially kill another player’s character. A well thought out reason, as well as proof of interactions with this character to lead up to this consequence, must be provided in the ticket. Not all requests will be approved.

DM EVENTS & DEATH

DMNPC’s killing a player character will not be permissible during a DM event without consent from both the player and DM. PVP kills are allowed as long as they are communicated with all parties, including the DM/staff present.

DEATH APPEAL

If your character’s death was accepted and the aggressor successful at killing your character, though you feel it was not justified, you are allowed to appeal the decision. A ticket is required with the submitted evidence for your claim and will be reviewed by staff.

DEATH AS CONSEQUENCE

Once your PK ticket has been approved and the roleplay has taken place, a ticket is required to be created with the following form. Remember, just because a PK ticket was approved, that does NOT mean the character is automatically killed. Each character has a chance at escaping death. The roleplay must happen and screenshots provided. Remember to stay in constant communication between the other players involved.

PK FORM

Character Death Form


Victim’s Name: (Character Name)

Victim’s Discord: (Actual Discord ID. Example#1234)

Killer’s Name: (Character Name)

Killer’s Discord: (Actual Discord ID. Example#1234)

Type of PD: (Permanent Death Kill)

Detailed explanation: (What happened and why)

Relevant screenshots: (Screenshots of last emotes before killing blow)

vi. PK RULES

We encourage players to be creative with their consequences and to seek PK as a last resort. We are all writers contributing to a large story and if the antagonist is killed at the beginning, the story would eventually run dry. Beyond that there is a greater story at play to consider when making your decision. We ask that the choice to PK is not taken lightly and that other options are considered before a PK is chosen so that stories can continue to grow and form! Below are five PK rules that aid building a fulfilling story for all parties.

SCENE LOCK

Once PvP starts the scene is locked. This means anyone who wanders upon the scene does not see what is happening because the battle would have already been completed. The 4 Emote Rule is for when combat has concluded. There are 4 rounds of emotes before the scene is unlocked. At this time, players can interact with the scene. The players that were involved in the combat, are still subject to consequences agreed upon.

The scene lock of the 4 Emote Rule should be utilized to inflict consequences or relocate the downed character to a new location. A secondary location can be used as a temporary imprisonment away from the scene of the crime until consequences have been agreed upon and decided.

CONSENT

Defendant’s consent overrules all below PK rules. If a player would prefer to reroll through a PK and communicates this effectively to their aggressor, the PK will be approved. A ticket is required to log the PK.

Additionally, no one should be pressured into providing this consent. If you feel like you are being pressured, please open up a ticket with moderation staff.

VOLUNTARY DEATH

The defender can give their consent to voluntarily PK their character forgoing the PK request process. If the player would prefer to reroll through the PK and communicates this effectively to their aggressor, the PK will be approved. A ticket is required to be opened to log the PK.

MUTUAL ESCALATION

Mutual Escalation is when both parties are antagonizing each other. This is what drives a great story, having a foe and combating one another. However, certain escalations would not give enough reason to end a character's life. For example, if a character vandalizes your home and your character decides to go and send a threatening letter. To get a PK request approved, there needs to be proof of mutual escalation that shows the circumstances enough to end the other character’s life, ergo finishing their story.

NO VALUE OF LIFE

When a character acts recklessly and is roleplayed in a way that does not make sense for the situation they are in, this is called No Value of Life (NVL). An example of this is when a character is in a situation of extreme danger and the player roleplays the character as if they do not care. A monstrous creature who walks into a well populated town without trying to sneak around or when a character is getting beaten/tortured and not showing any sort of fear or pain are both examples of NVL. It is crucial to play your character as accurately as can be for the situation they find themselves in.
If a character shows NVL, a PK ticket can be created for review by the staff team. In the ticket, you may ping moderators immediately in this situation in order to get a quick response.

EXTREME CIRCUMSTANCE

There are circumstances that are deemed extreme where requesting a PK is acceptable without mutual escalation. These situations are incredibly vulgar and so vile that an appropriate response is PK. An example would be if your character was tortured and home utterly destroyed leaving their life ruined. A moderation ticket is required with proof of the extreme circumstances to be reviewed by staff.

Remember that proof needs to be shown by the aggressor seeking out the PK. If you are in a roleplay that involves antagonism, it is a good habit to take screenshots of information you may need at a later time. Even if you are not considering PK at this time, having the screenshot saved and ready is worth the time. Staff will not approve a PK without screenshots providing the appropriate amount of proof for Consent, Mutual Escalation, No Value of Life, or Extreme Circumstances. Screenshots are also needed for any OOC communications regarding Consent or Voluntary Death.

vii. NON-CONSENSUAL SEXUAL INTERACTIONS AS A CONSEQUENCE OF PVP

Non-consensual sexual consequences as a result of a PVP down are strictly prohibited at Crossroads. It is not a viable consequence to give to any player inside Combat scenarios and should not be attempted. If you or someone you know have experienced Non-Consensual Sexual Interactions as a Consequence of combat, you may open a ticket to express this violation of our consequences policy.

viii. NON-CONSENSUAL SEXUAL INTERACTIONS OUTSIDE OF COMBAT

While we at Crossroads do not prohibit situations such as Non-Consensual Sexual Interactions altogether, we also know that these topics can be both triggering behind the screen and portrayed in particularly out-of-the-box ways. Consent is the pillar of any consequence, even outside of PVP downs – and we strive to make that abundantly plain and without question.
Before enacting Non-Consensual Sexual Interactions, any and all parties involved, whether they be a witness or a participant in the act, must give prior consent. This consent can be revoked at any time before or during the act. If there is an unwilling witness who does not give consent to seeing the scene unfold, the scene must be moved away from them without question. If the Defending party requests that the scene be “FTB’d” (Faded to Black), it must be followed and no further roleplay of the interaction can occur. The Afflicting party must abide by the comfortability and consent of the Defending party. We at Crossroads stress again that consent can be revoked at any time before or during the act, and the scene must be retconned.
Parties that choose to engage in non-consensual sexual interactions in RP cannot subject secondary parties to that element of narrative without consent. This includes reporting to city guards or otherwise talking about Non-Con interactions in a manner that would result in hunts for the perpetrator, or otherwise subject non-participants to the graphic content that took place during the roleplay.

ix. SKIRMISH CONSEQUENCES

Skirmish consequences are the result of a fight involving Unfavorable Odds, with the winners outnumbering the victims by a ratio of 3:1 or higher. Those are small, ICly insignificant, consequences, they are not long lasting nor leave a large impact on the downed individual, physically and/or mentally. These consequences are meant to enhance the roleplaying experience without causing significant harm to characters at overwhelming odds.
Examples of Skirmish Consequences include, but are not limited to:

Cuts & Bruises (Lesser Wounds)

Interrogation

Petty Theft (See Skirmish: Theft)

Minor Curse

Intimidation

Threatening further action

Lock of Hair

Concussion

x. SKIRMISH CONSEQUENCES: THEFT

Skirmish Consequences are small, insignificant consequences enacted against a downed player in a PVP scenario. Skirmish Consequences regarding Theft is the thieving of materials, currency, or non-magical items that are not Theft As A Consequence. For instance, you may only take 15 Currency as opposed to 30. You may only enact this consequence as opposed to another, and cannot stack consequences with this option.