B  v  stion

• "Put your hands up", "Don't move", "Follow me", expressed in a threatening manner, can all be interpreted as an initiation.
• Pointing a weapon, punching someone or hitting them with a melee weapon, tying someone up, restricting their movement (crowding around someone or locking the door behind them), or otherwise incapacitating them can all be seen as an initiation.
• Assisting or participating with someone else's initiation in any way, such as providing clear overwatch or restraining someone, will be considered as an initiation in it's own right. Anyone who wishes not to be associated with an initiation should immediately leave the scene of the initiation.
• Theft and vandalism are both initiations.
• Warning shots are not allowed and do not classify as an initiation.

4.4 - While initiations are broad and give the defending party the ability to defend themselves, the initiating party must provide a clear and unambiguous initiation in order to gain the right to use lethal force on the defending party. Clear and unambiguous initiations are initiations that include a demand and a consequence if that demand is not met within a reasonable amount of time.

• "Stop and give me your credits or I'll shoot!" is an example of a clear and unambiguous initiation. Both the initiating party and the defending party have rights to use lethal force.
• "Give me your credits!" is an example of an initiation that would give the defending party rights to use lethal force, but not the initiating party. There is no consequence.

4.5 - In the event that potentially lethal force is exchanged (a firefight or melee with the intent to kill), everyone associated with the initial initiation (classified as within VOIP range while within the Bastion and within line of sight outside the Bastion) will have 30 minutes of kill rights if the hostile exchange happens inside the walls and 1 hour if outside the walls. This timer is reset every time potentially lethal force is exchanged again. However, characters not associated with the initial initiation must be initiated upon in order to gain kill rights. After the 30 minute or 1 hour timer is up, re-initiation is required.

4.6 - If hostilities are initiated and no potentially lethal force has been exchanged between the initiating party and the defending party at the conclusion of a situation, all rights to use lethal force are reset. This means that if you are initiated on and you walk away without using your rights to lethal force, you lose those rights.

4.7 - Rights to lethal force does not give you explicit permission to use them at all times if it does not make in-character sense to do so.

4.8 - In the event that an initiation of a hostile action leads to you capturing and restraining another person, be it physically or through the threat of violence, that person has become your hostage. You must do everything in your power to keep them alive and in relatively good health, including protecting them from external; threats, feeding them, and leaving them with a realistic chance of survival when they are released, within the best of your ability.

4.9 - Hostages can only be executed in the following scenarios:

• Hostages do not comply with your demands after repeated requests, or they attempt escape.
• Hostages pose a direct and immediate threat to you or the rest of your initiating party - for example, if they pick up a weapon when not told to do so.
• Hostages do not value their life - for example, if they repeatedly talk back to you or insult you despite being told to stop.
• The hostages' allies refuse to negotiate, refuse to comply with (reasonable) demands, or openly retaliate on you or the initiating party.
• A pre-approved execution for the sake of RP and with the intent to permadeath. See 5.2 for details.

4.10 - A reasonable standard of RP must be upheld in all hostile situations. Do not perform quick, run-of-the-mill robberies that involve little to no interaction with your victim. This works both ways - as a victim, you must participate in the RP with the initiating party, and act with value for your life.

4.11 - Combat logging/respawning, or logging out/respawning to avoid the consequences of someone else's rights to lethal force on your character, is strictly prohibited. After a situation involving lethal force has ended, you must remain in-game for at least 20 minutes afterwards. This rule can be ignored if the players involved in a situation give you permission to log out beforehand.

4.12 - Baiting, or attempting to blatantly provoke another player into initiating on you, is strictly prohibited.

4.13 - The ISF FOB (SEC-0) cannot be entered or attacked by non-ISF characters except in direct retaliation to an initiation by the ISF against you or an ally.

5.1 - Permanent character death can be self-administered at any time, for any reason, or for no reason at all, by the character's owner in the Character CP.

• RPed out suicide, or suicide in a public area
• Deaths that are classified as No Value For Life
• Executions

There are two types of permanent kills that a player can request against another character - Proactive PKs and Reactive PKs.

5.3 - Proactive PKs are submitted and approved before a hostile situation that would end in the death of a character. These PKs are submitted in cases where it makes sense to kill another player's character for the sake of advancing the greater narrative of the community, and all other avenues of roleplay to solve a dispute have been exhausted.

• 5.3.1 - In order for staff to approve a Proactive PK application, a player must explain the current roleplay situation as well as their reasoning for requesting a PK. Additionally, they must submit ample video/screenshot evidence that enough roleplay history has been generated, as well as evidence that other avenues to resolve the conflict have been exhausted. PK applications are approved or denied based purely on staff discretion, based on the provided evidence.
• 5.3.2 - Upon approval of the Proactive PK application, a player must either capture and execute the approved character or kill the approved character in a firefight in order for the PK to be valid. Staff should be notified in the same application that the death of either themselves or the approved character has taken place.
• 5.3.3 - A Proactive PK works both ways. Upon approval of a Proactive PK application, the character that has been approved for PK also unwittingly gains PK rights on the character of the submitter of the PK application.

5.4 - Reactive PKs are submitted and approved after a hostile situation that has ended in the death of a character. These PKs are used usually in the case of a hostage that has gotten themselves killed due to their own actions, or in other niche scenarios in which a Reactive PK would make sense for the greater narrative of the community.

• 5.4.1 - Reactive PKs must be submitted within 2 hours of the time of the death of the character that they wish to PK in order to be considered.
• 5.4.2 - In order for staff to approve a Reactive PK application, a player must explain the roleplay situation that ended in the death of the character they wish to PK, as well as submit video evidence that the situation necessitates a PK. PK applications are approved or denied based purely on staff discretion, based on the provided evidence.
• 5.4.3 - Upon approval of the Reactive PK application, the approved character will be PKed immediately.

5.5 - PKs can be appealed up to one week after being PKed. The recipient of the PK must submit evidence that their character was wrongfully or prematurely PKed. PK appeals are approved or denied based purely on staff discretion, based on the provided evidence.