Friday, November 20, 2009

Commandeering (part 2)


In part 1, I covered the essentials of Commandeering and FoF Tuning mechanics, the various states Of Ownership (Owned, Abandoned) and Tuning (Controlled, Neutralized, Challenged), and delved into some specifics about Ship Commandeering, which the main use most players would have for this feature.

This entry is about understanding how Tuning contests are resolved, complete with some examples of the typical targets for Commandeering. If you haven't read part 1 of Commandeering, now may be a good time, and likewise you may want to have a glance at the FoF Tuners article, or at least keep it handy in case things get too hairy.


Anatomy of a target.

  • Tuning Strength Modifier (TSM): It modifies the base NTC (to compute ETC), boosts Passive Tuning Recharge (if available) and increases the output of FoF Tuner modules.
    Defaults to x1.00, can be increased by skills, sovereignty benefits, special rigs and upgrades, etc.
    TSM suffers from no stacking penalties of various sources applying to the same object.
All potential targets for Commandeering share a base set of attributes, many of which are subject to TSM.
  • Nominal Tuning Charge (NTC): Expressed in Tuning signal points (Ts), it is defined by the item type and can't be modified. NTC is used as base score to compute the ETC below and sets the threshold that must be reached to Challenge or gain Control over an object.

  • Effective Tuning Capacity (ETC): Basically the NTC plus applicable Tuning Strength Modifiers, this is the maximum charge the object can hold while Controlled — default value is equal to NTC.
    Formula: ETC=NTC*TSM

  • Base Passive Tuning Recharge (bPTR): Expressed as n% of the NTC,  with n defined by item type, it is used as base value to compute the PTR below.

  • Passive Tuning Recharge Rate (PTRr or PTR): expressed in % of the object ETC or in absolute Ts/cycle, it indicates how much an object will self-recharge per PTR cycle while between 0.0 Ts and ETC.
    Its value in absolute Tuning Charge output is indirectly modified by Tuning Strength modifiers as they increase the object ETC (constant percentile of a larger quantity), and directly as they increase the % value (higher fraction at constant quantity).
    PTR may be activated or inhibited by the Sovereignty/Ownership/Control status of the object.  
    Formula: PTRr(ETC%)=bPTR*(ETC/NTC)*TSM (or bPTR*TSM^2)
    Formula: PTR(Ts/cycle)=bPTR*ETC*TSM (or bPTR*NTC*TSM^2)

  • Passive Tuning Recharge Cycle (PTRc): expressed in seconds, it is set by the item type and can't be modified.
    PTRc is used to resolve the Control state of an object, in addition to the potential change in Tuning charge from PTR.
    [Note: since PTR(r) is a per-cycle value, PTRc directly affects its Ts/sec output, which is calculated thus: PTR/PTRc=PTR/s]
PTR boost is applied at the beginning of each cycle, while the Control state check of an object and the effect of FoF Tuners apply at the end of their respective cycles. This means if an object reaches its NTC (or is brought to 0.00 Ts) within its cycle, the Control state change will kick in right before the beginning of the next PTR cycle, possibly canceling (or enabling) Passive Tuning Recharge for the new cycle.


Control state changes.


The Control states of an object reflect which (if any) entity currently is in position to use it, and possibly Own it.
There are three possible Control states (Controlled, Neutralized, Challenged), and three potential contest types allowing to transition between Control states.



As can be seen above, it is possible to transition between any two Control states both ways, except between Challenged and Controlled.
Moving from a Challenged state to a Controlled one can be done through a single transition/contest,  but a move from a Controlled state to a Challenged one will require a first transition to a Neutralized state, then another from Neutralized to Challenged.

From a Neutralized state, the current Defender/Owner of the object (if any) may regain Control through a single transition/contest, while a Contender must first tune up the target to its NTC once to Challenge it (which resets the target's tuning charge to 25% NTC), then up again to change its state from Challenged to Controlled for the Challenger's benefit.

Here's the breakdown of transitions:
  • Controlled => Neutralized: reduce the target's tuning charge to -0.00 Ts (any party but Controller)

  • Neutralized => Controlled: tune up the target to NTC (Defender/Owner only)

  • Neutralized => Challenged: tune up the target to NTC (current Contender only) — resets the charge to 25% NTC in favor of the new Challenger.

  • Challenged => Neutralized: reduce the target's tuning charge to -0.00 Ts (any party but Challenger)

  • Challenged => Controlled: tune up the target to NTC (Challenger only)
From a practical standpoint, Commandeering a currently foreign-Controlled target requires to feed it roughly 3-4 times its NTC worth of FoF Tuning signal of your frequency (not accounting for PTR, and assuming no active interference from other parties): 1x to 2x NTC to Neutralize it (depending on applicable TSM), then 1x NTC to Challenge it, and finally 0.75x NTC to win the challenge and takeover Control.

For the Defender of an object under attack, successfully tuning the object up to its NTC once while still Controlled or Neutralized will be enough  to regain full Control over it. Once the object is Challenged however, the Defender (if Ownership hasn't been lost already) will first have to change its state back to Neutralized before attempting to re-claim it, typically without the help of PTR (disabled by the Challenged Control state).

Commandeering Targets.

[Editor's note: NTC for many structures are expressed in xDreadnoughts NTC as an indicator. Those are provisional numbers meant to give a rough feel of relative NTCs, and are very much still in the air at this stage.]


Ships

  • Vulnerable:

    • Defender FoF Frequency: always.
    • Attacker FoF Frequency: anywhere, while Structure≤95%, Shields<15%, Armor<15%;

  • State changes: Ownership inherited from Controller, with provisions (see The fine Print).

    • Abandoned: after 3min without a pilot.
    • Challenged: disables modules and jump drive (if any).

  • NTC: Based on ship class, variation between classes roughly proportional to Capacitor size.

    • ETC: NTC*TSM

  • PTR: always on, except while in a Challenged or Abandoned state, set to the current ship Defender FoF frequency.

    • PTRr: 3 to 15% ETC/cycle, based on ship class, further modified by TSM.
    • PTRc: Frigs, Dessie, Cruiser (T1, T2, Fc): 20s. BC, BS (T1,T2, Fc): 30s. T3 Cruisers: 30s. Freighters (T1/T2): 45s. Capitals: 60s. Supercaps: 90s.
    • -PTR: While Abandoned, -0.1% NTC/cycle.

  • TSM: affect ETC and PTR.

    • FoF Tuning skill: +5% per level.
    • Sovereignty: all sovereignty TSM apply.
    • Rigs: yes, tbd.


    POS control Towers

    • Vulnerable:

      • POS Defender FoF Frequency: always but while Reinforced.
      • Neutralization: while Shields<50%, post-Reinforced mode. Requires to be Planetary Defender or for the Planet to be Abandoned.
      • Commandeering: While Structure≤95%, Shields<50%, Armor<15%, post-Reinforced mode. Requires to be Planetary Defender, or Solar Defender (if the Planet is Abandoned). If both Planet and Solar are Abandoned, Commandeering is FFA. 
      • NPC space: Requires the POS Defender to be a valid War Target of the Attackers to lift sovereignty immunities. Rest is similar to 0.0 POS.


    • State changes: Ownership inherited from Controller, with provisions.

      •  Controlled: Enables Strategic Modules (subject to sov requisistes).
      • Abandoned: triggered on entering Challenged Control state.
      • Challenged: disables (Offlines) Strategic Modules (if any).


    • NTC: ≈ 10x Dreadnought NTC.

      • ETC: NTC*TSM

    • PTR: always on, except while in a Challenged/Reinforced state, set to the current POS Defender FoF frequency.

      • PTRr: 1% to 3% ETC/cycle, based on Tower Type, further modified by TSM.
      • PTRc: 300s.

    • TSM: affect ETC and PTR.

      • Sovereignty: requires Planetary Sovereignty to enable Sovereignty TSM from other tiers.
      • Tuning Array: +20% TSM


      POS Modules

      • Vulnerable:

        • POS Defender FoF Frequency: always but while Reinforced.
        • Neutralization: while Modules Shields<50%, Armor<50%, or anytime while the POS tower is Abandoned, offline or destroyed.
        • Commandeering: While Modules Shields<50%, Armor<50%, post-Reinforced mode.
          If the POS tower is destroyed, offline or Abandoned, Commandeering is FFA. 
        • NPC space: Requires the POS Defender to be a valid War Target of the Attackers to lift sovereignty immunities. Rest is similar to 0.0 POS.


      • State changes: Ownership inherited from POS control tower.

        •  Controlled: Allows to use/access/take the module and its contents, as if rightfully Owned.
        •  Owned: Allows to use/access/take the module and its contents, while not Controlled by a third-party.
        • Challenged: disables (Offline) if the module is of a Strategic type (tied to Sovereignty), or simply denies use/access/take to everyone.

      • NTC: ≈ 1-8x Dreadnought NTC (depends on type).

        • ETC: NTC*TSM

      • PTR: status inherited from control tower if present. Disabled if tower is offline, Abandoned or Destroyed, or if the module itself is offline or incapacitated.

        • PTRr: 1% to 5% ETC/cycle, based on module Type, further modified by TSM.
        • PTRc: 100s.

      • TSM: affect ETC and PTR.

        • Sovereignty: requires Planetary Sovereignty to enable Sovereignty TSM from other tiers.
        • Tuning Array: +20% TSM


      Stargates

      • Vulnerable:

        • Neutralization: always. A Stargate doesn't require to be damaged for any party to Neutralize it.
        • Commandeering: Requires the sister gate on the other side of the jump to be either  Neutralized (and fed the same  FoF Frequency) or positively charged (for the same FoF frequency) for Tuning Up to work on the target Stargate, unless one is the Owner of the target Stargate, in which case the sister gate being in any state but Controlled by a third-party is enough.
          A Stargate doesn't require to be damaged for any party to Commandeer it.
        • NPC space: Requires the Stargate Owner to be a valid War Target of the Attackers to lift sovereignty immunities. Rest is similar to 0.0.

      • State changes: Ownership inherited from Solar/Constellar Sovereign, with provisions.

        • Controlled: Builds Occupancy requirements, also enables TacticalDataStreams for the Controller, and modifies the Stargate PTR.
        • Neutralized: Disables SearchlightEffect for the Defender.
        • Challenged: Denies all Occupancy/Ownership benefits to the Owner.

      • NTC: ≈ 10x Dreadnought NTC.

        • ETC: NTC*TSM

      • PTR: requires  Solar sovereignty to benefit the Stargate Controller, or Constellation Sovereignty  (if the Solar is Abandoned) — PTR depends on Ownership. PTR is also disabled while the Stargate is Challenged, and halved while it is Controlled by another Faction than the DCC Defender.

        • PTRr: 1% ETC/cycle, based on Tower Type, further modified by TSM.
        • PTRc: 90s.

      • TSM: affect ETC and PTR.

        • Sovereignty: System Sovereignty is required to receive other Sovereignty TSM, or Constellation Sovereignty with Neighborhood rules active if the System is Abandoned.

      Dungeon Control Centers (Planetary/Solar)

      • Vulnerable:

        • Neutralization: while Occupancy requisites are met, barring Sovereignty immunities.
          A DCC doesn't require to be damaged for any party to Neutralize it.
        • Commandeering: while Occupancy requisites are met, barring Sovereignty immunities.
          A DCC doesn't require to be damaged for any party to Commandeer it.
        • NPC space: Requires the Dungeon Defender to be a valid Factional War Target of the Attackers. Rest is similar to 0.0.


      • State changes: Ownership is decided by Controller of the Dungeon Control Center.

        • Controlled: Grants DCC and Dungeon Ownership, with attached benefits.
        • Owned: Grants Planetary or Solar sovereignty, respectively. 
          Planetary Ownership reduces Occupancy requirements to Neutralize or Commandeer the local Outpost  while the DCC is Controlled by its Owner, and grants an exclusive to the DCC Owner on Commandeering the Oupost while the DCC remains Controlled or Neutralized.
          Ownership allows to access/take/manage the DCC, and may also tame local NPC drones (with sufficient sovereignty benefits).
        • Neutralized: Planetary DCC, while Neutralized, open their respective Outpost to Neutralization by attackers (barring Capital Sovereignty Immunity). Neutralizing a  DCC also disables SearchlightEffect for its Defender.
        • Challenged: Lifts DCC, Dungeon and Planetary or Solar Ownership/Sovereignty and attached benefits, switching the respective Ownership/Sovereignty to Abandoned.
        • Abandoned: Allows any party to vie for sovereignty on equal Occupancy footing.
          An Abandoned Planetary DCC opens the local outpost to Neutralization/Commandeering by any party that meets Occupancy requirements minus Planetary Sovereignty.


      • NTC: ≈ 10x/20x Dreadnought NTC (Planetary/Solar).

        • ETC: NTC*TSM

      • PTR: PTR is active while the DCC is Owned plus Controlled or Neutralized,  and disabled while the DCC is Challenged or Abandoned.

        • PTRr: 2% (Planetary), 1% (Solar)  ETC/cycle, modified by TSM.
        • PTRc: 300s.

      • TSM: affect ETC and PTR.

        • Sovereignty: requires Dungeon Ownership to enable Sovereignty TSM from other tiers.

      Dungeon Mass Drivers (Planetary/Solar)

      • Vulnerable:

        • Neutralization: while Occupancy requisites are met, barring Sovereignty immunities.
          A DMD doesn't require to be damaged for any party to Neutralize it.
        • Commandeering: while Occupancy requisites are met, barring Sovereignty immunities.
          A DMD doesn't require to be damaged for any party to Commandeer it.
        • NPC space: Requires the Dungeon Defender to be a valid Factional War Target of the Attackers. Rest is similar to 0.0.


      • State changes: Ownership inherited from Dungeon Control Center.

        •  Controlled: Allows to use the DMD as if rightfully Owned but at the expense of its Tuning charge (based on mass) if not the Owner (subject to ship class restrictions based on possible Sovereignty Immunities). Also renders the attached Defensive structures susceptible to Commandeering by the Controller if not also the Owner.
        • Owned: Allows to use the DMD at all times at no cost and without restrictions, may also tame local NPC drones (with sufficient sovereignty benefits), and allows to Tune Up or Neutralize attached Defensive structures.
        • Challenged: disables TacticalDataStreams, and prevents manual control of the attached Defensive structures by the Defender (but not their FoF Tuning).

      • NTC: ≈ 5x/10x Dreadnought NTC (Planetary/Solar).

        • ETC: NTC*TSM

      • PTR: status partly inherited from Dungeon Control Center. PTR is disabled while the DMD is Challenged, or Abandoned (as a result of the DCC being lost), and halved while the DMD is Controlled by another Faction than the DCC Defender.

        • PTRr: 2% (Planetary), 1% (Solar)  ETC/cycle, further modified by TSM.
        • PTRc: 300s.

      • TSM: affect ETC and PTR.

        • Sovereignty: requires Dungeon Ownership to enable Sovereignty TSM from other tiers.


      Dungeon Defensive Structures

      • Vulnerable:

        • Neutralization: By any  faction while Modules Shields<50%, Armor<50%, or while the structure itself is Abandoned, or the DMD/DCC it's attached to is Abandoned (or destroyed).
          By the Dungeon Defender at any time, while charged positively for a foreign Faction FoF frequency. 
        • Commandeering: By the Controller of their DMD/DCC — a Commandeered DSS will revert to Neutralized if the state of the DMD it's attached to changes to Neutralized, Challenged or Abandoned.
          DDS don't require to be damaged for any party to Commandeer them.
        • NPC space: Requires the Dungeon Defender to be a valid Factional War Target of the Attackers. Rest is similar to 0.0, except DDS can't be stolen.


      • State changes: Ownership inherited from Dungeon Control Center.

        • Controlled: Allows to use/access/take the DDS as if rightfully Owned, burning the DCC fuel reserves all the while. If the DSS Controller is not the Dungeon Defender, it will only attack in self-defense unless manually operated by a Pilot. 
        • Owned: Allows to use the DDS in automatic mode, or manually operated by a  Pilot, while the DDS is Controlled (or Neutralized) by its Owner.
        • Challenged: disables TacticalDataStreams, and prevents manual control of the DDS  by the Defender (but not their FoF Tuning). The DDS will still operate in automatic mode for the Owner benefit while Challenged, however.
        • Abandoned: Can only happen as a result of the DCC being lost and brings the structure offline. The DCC can then be Neutralized and Commandeered by any party, and subsequently unanchored, or re-onlined for the new Dungen Defender's benefit.


      • NTC: ≈ 1-8x Dreadnought NTC (depends on type).

        • ETC: NTC*TSM

      • PTR: status partly inherited from Dungeon Control Center. DDS' PTR is disabled while their DMD is Challenged, or Abandoned (as a result of the DCC being lost), and halved while the DMD is Controlled by another Faction than the DCC Defender.

        • PTRr: 1% to 5% ETC/cycle, based on module Type, further modified by TSM.
        • PTRc: 100s.

      • TSM: affect ETC and PTR.

        • Sovereignty: requires Dungeon Ownership to enable Sovereignty TSM from other tiers.


      Misc.Anchorables

      Include: Anchorable Bubbles, Secure Cans, Freighter Cans, Construction and Upgrade Platforms
      • Vulnerable:

        • Neutralization: By any  party while Structure≤95%, Shields<15%, Armor<15%.
          By the current Controller/Owner at any time, or by anyone while Abandoned, both regardless of damaged state. 
        • Commandeering: By any  party while Structure≤95%, Shields<15%, Armor<15%.
          By the current Controller/Owner at any time, or by anyone while Abandoned, both regardless of damaged state. 
        • NPC space: Is a Criminal Act unless the object Defender is a valid (Factional )War Target , falls under Kill Rights, or belongs to the same Corp/Faction as the FoF Tuning frequency applied. Legality is generally the same as for ships Commandeering.


      • State changes: Ownership set by Control state.

        • Controlled: Grants Ownership to the Controller, unless the last Owner was a Corporation belonging to the Faction that Commandeered the Anchorable, in which case Ownership is left intact. 
        • Owned: Allows to Neutralize a foreign FoF Tuning, or Tune Up the object at all times.
        • Challenged: Lifts Ownership under the same rules as Control does grant it (see above) resulting either in conservation of Ownership or Abandonment of the object.
        • Abandoned: Allows anyone to Neutralize or Commandeer the object.

      • NTC: ≈ varies wildly (depends on type).

        • ETC: NTC*TSM

      • PTR: Special — Misc.Anchorables can't benefit from PTR, but indefinitely conserve their tuning, Ownership and Control state unless Abandoned.

        • PTRc: 100s.
        • -PTR: While Abandoned, -0.1% NTC/cycle, exempt from TSM modifiers.

      • TSM: affect ETC.

        • Sovereignty: any Sovereignty TSM that applies to ships applies to Misc.Anchorables belonging to that Faction.

      ***

      I left out Outposts from this one, because: it's already an insane wall'o'text  and me fingers hurt ; Outposts call for diagramms (you got one today already, and I hate making those) ; I am the starving.
      So this will be for Part 3, with other stuff I may have forgot/left out.


      No comments:

      Post a Comment