V9:Immunity

Developer Note: The current V9 Rules can be found here.

The V9 Wiki is currently obsolete. The Project Phoenix Google Doc is the main source of V9 rules going forward.
We will eventually rebuild the wiki as a comprehensive rules reference, but now is not that time.

Thank you for your interest in the project! Join the Discord for more information!

- The Project Phoenix (V9) Development Team

This page is part of the V9 Development Project.

• These rules represent a proposed ruleset for the Amtgard LARP. All references to the organization are used from that perspective, and do not represent current organizational policy or procedures. Amtgard is a trademark of Amtgard International.
• This wiki is the detailed, comprehensive form of the ruleset. You can find the condensed Quick-Play rules here. These are currently still a work in progress.
• To view the current official Amtgard rules, please see the Amtgard V8 Rulebook.
  

---

Immunity

Immunity allows the bearer to protect themselves from the thing the player is immune to.

• When a player would be affected by something they are immune to, they may immediately declare "Immune!" or the name of the effect making them immune (i.e. "Missile Block!"). If they do, they are unaffected. If they do not, or choose not to, they will be affected as normal.
  • Players may not use immunity against their own abilities or strikes.
  • Immunity to a specific ability will protect against all effects from that ability.
  • Immunity to an immediate effect, such as Armor Destroying, will only protect against that singular effect.
  • Immunity to a State will protect against all text in an effect that includes that state.
    • Example 1: A player that is immune to Insubstantial protects themselves from Banish. They would ignore both the Insubstantial state and the forced movement, since they are both part of the status effect that includes Insubstantial.
    • Example 2: A player who is immune to Stopped protects themselves from Pinning Arrow. They would only ignore the status effect that includes Stopped, but not the immediate effects that include damage, weapon destroying, and armor breaking.
    
    
• DECLARATION TIMING
  • The exact timing window for an immunity declaration should be judged in good faith on a case-by-case basis depending on the chaos of battle and the awareness of the would-be immune player. For example, if a player is focused on a melee exchange and they do not notice they have been struck by an attack from a 3rd party that they are immune to, they should be given the chance to declare their immunity once they have been made aware of it.
  • If a player would be affected by multiple things faster than they can mentally register and react to, they only need to declare the immunity once to cover all the relevant effects. For example, if a player that is Immune to Stopped is struck by four Entangles back-to-back, they can just declare "Immune to Stopped" once and it will cover all the Entangles. They do not need to declare four times.
  • In all cases, attackers should give their opponents a fair grace period to declare their immunities. Likewise, players with immunities themselves should do their best to make their declarations in a timely manner. All parties should avoid exploiting this moment for gameplay advantage.
  
  

V8 Transition Note: Immunities are now optional. You are no longer forced to be immune to friendly effects!