1. Game Conceptslink

1.1. Generallink

These rules are compatible with cards from the game android: netrunner by Fantasy Flight Games. android: netrunner is a game about the cyber-struggle between massive Corporations and subversive hackers known as Runners.

1. 1.1.1.linkThe game is played between two players. One player takes the role of the Corp (Corporation) and the other takes the role of the Runner. This rules document will frequently refer to a player interchangeably with their game role.
2. 1.1.2.linkEach player needs a legal deck, an identity card for their role, and any extra cards used from outside their deck. They also need a supply of tokens as described in section 1.9. The constraints that define the legality of a deck are defined in section 1.4, and the cases where cards outside the deck and identity can be used are defined in section 1.5.
3. 1.1.3.linkAll numbers used in the game are integers. Unless otherwise stated, a given value can be positive, negative, or zero.

1.2. Golden Ruleslink

1. 1.2.1.linkIf the text of a card directly contradicts these rules, the text of the card takes precedence.
2. 1.2.2.linkIf a rule or ability directs something to happen, but another effect states that it cannot happen, the "cannot" ability takes precedence.
   1. a.linkIf a "cannot" effect prohibits all of the effects of another ability, that ability cannot be triggered.
   2. b.linkIf a "cannot" effect prohibits only part of another ability, that ability can be triggered, but the prohibited steps of resolving that ability are not carried out.
      1. Example: During a run, Lockdown's subroutine resolves, preventing the Runner from drawing cards for the remainder of the turn. The Runner has a Diesel and a Process Automation in their grip. For the remainder of this turn, they cannot play Diesel as its entire ability is prohibited, but they can play Process Automation. Even though cards cannot be drawn through Process Automation, the Runner can play it to gain 2[c].
3. 1.2.3.linkIf an instruction includes the words "if able," it can only be carried out fully or not at all. If any part of the instruction is not possible to carry out, the entire instruction is ignored.
4. 1.2.4.linkIf an instruction does not include the words "if able," as much of that instruction as possible is carried out. Any parts of the instruction that are not possible to carry out are ignored.
5. 1.2.5.linkA player can only take an action or use an ability if its effect has the potential to change the game state. This potential is assessed strictly by what the action or ability can be expected to accomplish, without regard to the consequences of paying any costs to initiate that action or ability and without regard to any other abilities that may meet their conditions in the process of initiating or resolving that action or ability.
   1. Example: The Runner is playing Armand "Geist" Walker and has Forger installed. The Runner can only trash Forger and trigger Geist's ability when they are about to take a tag (which Forger could avoid) or while they have a tag (which Forger could remove). Using Forger at any other time has no potential to change the game state.

1.3. Symbolslink

1. 1.3.1.linkSeveral non-English symbols appear on cards and in this rules document. This section serves as a basic guide to those symbols.
2. 1.3.2.linkWhen this document is presented in a format without images, plaintext replacements are used. These replacements are listed along with the symbols themselves for reference.
3. 1.3.3.linkThe symbol [c] (plaintext: [c]) stands for "credit". It always appears with a numeral, such as 1[c], which means "one credit," or 3[c], which means "three credits." See section 1.10 for rules about credits.
4. 1.3.4.linkThe symbol [click] (plaintext: [click]) stands for "click". Multiple clicks can be represented either by multiple symbols, such as [click][click], or by a numeral and symbol, such as 2[click], both meaning "two clicks." See section 1.11 for rules about clicks.
5. 1.3.5.linkThe symbol [recurring] (plaintext: [recurring]) stands for recurring credit. It always appears with a numeral, such as 1[recurring], which means "one recurring credit," or 3[recurring], which means "three recurring credits." See section 1.10.5 for rules about recurring credits.
6. 1.3.6.linkThe symbol [link] (plaintext: [link]) stands for "link". It is always used with a quantity, such as 1[link], which means "1 link." See section 10.7 for rules about link.
7. 1.3.7.linkThe symbol [MU] (plaintext: [MU]) stands for "memory unit". It always appears with a quantity, such as 2[MU], which means "2 memory units." See section 1.20 for rules about memory.
8. 1.3.8.linkThe symbol [sub] (plaintext: [sub]) stands for "subroutine". Each symbol marks a single subroutine on a piece of ice. See section 9.8 for information about subroutines.
9. 1.3.9.linkThe symbol [trash] (plaintext: [trash]) stands for "trash this card". It is used as a self-referential cost in card text, such as "[trash]: Draw 2 cards," which means "Trash this card to draw 2 cards." See section 1.16 for rules about costs, and section 1.19 for rules about trashing cards.
10. 1.3.10.linkThe symbol [interrupt] (plaintext: [interrupt]) stands for "interrupt timing". It is used to designate abilities that resolve immediately before other abilities. See section 9.9 for rules about interrupt abilities.

1.4. Deck Constructionlink

1. 1.4.1.linkEach player's deck is associated with a single identity card that determines the faction, minimum deck size, and influence limit of that deck. The identity card may also stipulate other variances from the standard deckbuilding rules.
   1. a.linkThe identities The Catalyst and The Syndicate from the System Gateway Starter Pack are intended for use only with the decks included in that pack. They are not legal for play under the full deck construction rules.
2. 1.4.2.linkEach deck must meet all requirements in this section to be legal for play.
3. 1.4.3.linkThe deck must contain at least as many cards as the minimum deck size indicated on the corresponding identity.
   1. a.linkIdentity cards, extra cards that begin the game outside the deck, and player aid cards are not part of the deck and are not counted towards the size of the deck.
   2. b.linkThere is no maximum deck size.
4. 1.4.4.linkDecks cannot contain identity cards, player aid cards, cards from the wrong side (Corp cards in a Runner deck or vice-versa), or out-of-faction cards that lack influence costs.
5. 1.4.5.linkNeutral cards and cards that belong to a faction other than the corresponding identity's faction are all considered out-of-faction. The total influence cost of out-of-faction cards in the deck must not exceed the influence limit of that identity.
   1. a.linkThe total influence cost of out-of-faction cards is counted by copy and not by name.
      1. Example: Including a single copy of Diesel in a non-Shaper deck adds 2 to the total influence in that deck, while including two copies of Diesel in a non-Shaper deck adds 4 to the total influence in that deck.
6. 1.4.6.linkA Corp deck must contain agendas totalling a certain number of agenda points, as determined by the total number of cards in the deck.
   1. a.linkA deck with 40 to 44 cards must contain 18 or 19 agenda points.
   2. b.linkA deck with 45 to 49 cards must contain 20 or 21 agenda points.
   3. c.linkA deck with 50 to 54 cards must contain 22 or 23 agenda points.
   4. d.linkA deck with more than 54 cards must contain 22 or 23 agenda points, plus an additional 2 agenda points for every full 5 cards in the deck over 50.
      1. Example: A 66 card deck requires 6 additional agenda points, since it includes 3 sets of 5 cards beyond 50. This gives a final requirement of either 28 or 29 agenda points.
7. 1.4.7.linkThe deck cannot contain more than 3 copies of any single card, by name. Some cards stipulate alternative copy limits in their card text.
8. 1.4.8.linkTournament play may impose other restrictions or requirements on the legal configurations of identities and decks.

1.5. Extra Cardslink

1. 1.5.1.linkSome abilities allow for the use of additional cards from outside the deck.
2. 1.5.2.linkOne Corp identity, Jinteki Biotech: Life Imagined, has the ability, "Before taking your first turn, you may switch this card with any copy of Jinteki Biotech." There are 3 versions of this identity, which have different abilities on their reverse side.
   1. a.linkA player playing Jinteki Biotech as their identity may bring any number of copies of that identity along with their deck. After completing game setup, that player may choose any copy they own to be their active identity for the duration of the game. All other copies are placed outside the game.
3. 1.5.3.linkOne Runner identity, Adam: Compulsive Hacker, has the ability, "You start the game with 3 different directive cards installed (these cards are not considered part of your deck)."
   1. a.linkA player playing Adam as their identity must bring at least 3 differently named cards with the directive subtype along with their deck. The player may bring any number of directive cards over the required 3.
   2. b.linkAfter players reveal their identities, the player playing Adam selects exactly 3 of their provided directive cards. Those cards begin the game installed in the play area. All other directives the player brought this way remain outside the game.
   3. c.linkA player playing Adam can also include directives cards in their deck. The cards chosen to be installed at the beginning of the game do not impact the deck's influence requirements or the maximum allowed number of copies of those cards.
   4. d.linkOnce the game has begun, the cards installed this way are treated exactly as any other installed cards. Abilities that move these cards to other zones function normally, including shuffling them into the stack.
4. 1.5.4.linkTwo cards, Rebirth and DJ Fenris, make use of identity cards other than the one selected by the player during deck construction.
   1. a.linkA player may bring any number of additional Runner identity cards along with their deck. These cards are kept in a pile outside the game. The Runner may look at these cards at any time.
   2. b.linkWhen an ability refers to an identity other than the Runner's current identity, it refers to the cards provided this way. If an identity card leaves the play area, it must be returned to the pile outside the game.
   3. c.linkIn a tournament, all identities brought to the game this way must be legal for players to use as their actual identity in that tournament.
   4. d.linkOne Runner identity, Hoshiko Shiro, is double-sided (see section 3.1). If the Runner switches their identity with Hoshiko, it enters play with the front side faceup. If the Runner switches Hoshiko with another identity, the new identity enters play faceup regardless of Hoshiko's current status.

1.6. Starting the Gamelink

1. 1.6.1.linkThe players decide who will play as the Corp and who will play as the Runner. Each player places an appropriate identity card for the side they are to play faceup in the play area, then supplies a corresponding deck, placing it facedown in the play area, and any appropriate extra cards.
   1. a.linkSome identity cards have abilities that affect setup. Even though cards are not active until the game begins, these identities still alter setup at the appropriate step as indicated by their text.
   2. b.linkSome identities are double-sided (see section 3.1). If a player is playing a double-sided identity, it begins the game with the front side faceup.
2. 1.6.2.linkIf a player's identity has an ability that affects setup or the start of the game, and that ability does not directly correspond to a setup step outlined in this section of the rules, that player makes any necessary decisions and changes for their identity's special setup or start of game abilities at this time. If both players have setup or start of game abilities at this time, the Corp resolves theirs first.
3. 1.6.3.linkThe players create the bank by gathering all types of tokens described in section 1.9.
4. 1.6.4.linkEach player takes five credits from the bank, placing the credits in their credit pool.
5. 1.6.5.linkEach player shuffles their deck.
6. 1.6.6.linkEach player draws 5 cards from the top of their deck to form their starting hand.
   1. a.linkAfter drawing starting hands, the Corp may choose to take a mulligan; then, the Runner may choose to take a mulligan. To take a mulligan, the player shuffles their starting hand back into their deck, then draws a new starting hand. They must keep the second hand as their starting hand.
7. 1.6.7.linkThe game begins and the Corp takes their first turn.
   1. a.linkIf the Corp's identity has an ability with instructions for "before taking your first turn," the Corp resolves that ability immediately before taking their first turn, and thus before the game starts.

1.7. Ending the Gamelink

1. 1.7.1.linkThe game ends when a player meets one of their win conditions.
   1. a.linkIf both players would simultaneously satisfy their win conditions, the game ends in a draw.
2. 1.7.2.linkEach player has two possible win conditions available.
   1. a.linkEither player can win by collecting agenda points in their score area (usually done by scoring or stealing agendas; see section 1.17). A player with a score of 7 or more wins the game.
   2. b.linkThe Corp wins if the Runner is flatlined. The Runner is flatlined immediately if they suffer more damage than they have cards in their grip. The Runner is also flatlined if, at the beginning of their discard phase, their maximum hand size is less than 0. See section 10.4 for more information about damage.
   3. c.linkThe Runner wins if the Corp is required to draw a card from R&D but cannot because R&D is empty.

1.8. Cardslink

1. 1.8.1.linkThere are six types of Corp cards: agendas, assets, ice, identities, operations, and upgrades. All cards except the identity card are shuffled into the Corp's deck at the beginning of the game.
2. 1.8.2.linkThere are five types of Runner cards: events, hardware, identities, programs, and resources. All cards except the identity card are shuffled into the Runner's deck at the beginning of the game.
3. 1.8.3.linkCards that are active are able to affect the game through their abilities.
   1. a.linkRunner cards that are installed and faceup in the play area, Corp cards that are installed and rezzed, events and operations in the play area, agendas in the Corp's score area, and both players' identities are active.
   2. b.linkUnless otherwise stated, Runner cards become active as part of the process of playing or installing them.
   3. c.linkUnless otherwise stated, Corp cards other than operations are installed unrezzed, and thus inactive, into the play area. Assets, ice, and upgrades become active when they are rezzed; agendas become active when they are scored. Operations become active as part of the process of playing them.
   4. d.linkIdentity cards become active when the game begins.
4. 1.8.4.linkCards that are inactive are unable to affect the game or have most of their abilities used.
   1. a.linkCards are inactive in R&D, HQ, Archives, the heap, the grip, the stack, the Runner's score area, while set aside, and while removed from the game. Facedown cards in the play area are also inactive.
   2. b.linkInactive cards in most zones retain their printed characteristics (name, card type, faction, cost, subtypes, influence, etc). Facedown installed Runner cards have no characteristics.
5. 1.8.5.linkFor a player to draw 1 or more cards is to take that many cards from the top of their deck and put them into their hand. Section 8.4 provides more details about drawing cards.
6. 1.8.6.linkMost abilities are active if and only if the card they appear on is active. Section 9.1.8 details the cases where abilities on inactive cards are still active.
7. 1.8.7.linkAbilities can convert cards from one type into another type, or even from a card into a counter. Rules 10.1.3 and 10.1.4 explain the details of card conversion.

1.9. Counters and Tokenslink

1. 1.9.1.linkCounters and tokens are game pieces (or equivalent) that track various resources, effects, and statuses of players and their cards.
   1. a.linkThe terms "counter" and "token" are interchangeable.
2. 1.9.2.linkThe bank is the supply of counters not yet in play. Counters in the bank are available to both players to take and use as dictated by the game rules and card abilities. Players do not control counters in the bank and cannot spend them. The bank is an unlimited supply; running out of game pieces to track a type of counter does not prohibit a player from gaining counters of that type or placing them on cards.
   1. a.linkIf an instruction directs players to place counters on a card without designating where those counters come from, take those counters from the bank.
   2. b.linkA condition or restriction that looks for counters being placed on a card can be met by either counters from the bank or counters moved from another location.
3. 1.9.3.linkSome abilities can convert a card into a counter. A counter put into play in this way is tracked with the card acting as a game piece. See rule 10.1.4.
4. 1.9.4.linkSome abilities can cause a player or card to have or be "considered to have" 1 or more counters or additional counters without placing or giving those counters. A counter considered to exist in this way conveys all the same information and effects as a counter of the specified type would, except that it cannot be moved or removed from the card or player it belongs to, nor can it be spent to pay a cost.
5. 1.9.5.linkThere are ten types of counters: credit counters, click counters, tag counters, bad publicity counters, core damage counters, advancement counters, virus counters, power counters, agenda counters, and condition counters.
   1. a.linkCredit counters are used to track the number of credits each player has in their credit pool; they can also be placed on cards. Rules for credits, the credit pool, and other related concepts are in section 1.10.
   2. b.linkClick counters are a gameplay aid used to track the clicks the active player has spent or has left to spend during their turn. Rules for clicks are in section 1.11.
   3. c.linkTag counters are used to represent tags on the Runner. Rules for tags are given in section 10.5.
   4. d.linkBad publicity counters represent bad publicity the Corp has earned. Rules for bad publicity are in section 10.6.
   5. e.linkCore damage counters are a gameplay aid used to track core damage the Runner has suffered. Each point of core damage the Runner suffers forces them to take a core damage counter. See section 10.4.
   6. f.linkAdvancement counters are a counter used primarily on installed agendas to track the Corp's progress toward being able to score them.
   7. g.linkVirus counters are a generic counter, used primarily by virus programs, that can be removed by the Corp purging them. See section 10.1.2.
   8. h.linkPower counters are a generic counter used by a variety of cards. They have no special rules.
   9. i.linkAgenda counters are a generic counter used primarily on scored agendas. They have no special rules.
   10. j.linkCondition counters are counters that have rules text. Their abilities are active as long as they are hosted on a card.

1.10. Creditslink

Each of the Runner's credits represents enough money to upgrade some basic parts for their console, have a meal at a decent restaurant, or buy a ticket and some concessions for a night at the sensies. Each of the Corp's credits represents enough money to manufacture a run of computer parts, buy out a decent restaurant, or film a low-budget sensie.

1. 1.10.1.linkA credit ([c]) is the basic unit of currency. Players spend their credits to pay for various costs, card abilities, traces, etc. Credit counters most commonly represent 1[c] each, but can represent larger denominations if clearly marked.
2. 1.10.2.linkEach player has a credit pool where they keep a supply of credit counters matching the credits they have available to spend. The number of credits in a player's credit pool is open information.
3. 1.10.3.linkCredits enter and leave a player's credit pool as that player gains, loses, or spends credits.
   1. a.linkA player gains credits whenever credits enter their credit pool from any location.
   2. b.linkIf a player is required to lose credits, that player is forced to move the specified number of credits from their credit pool to the bank. Players cannot lose credits from cards.
      1. Example: If a subroutine on DNA Tracker resolves, the Runner must lose 2[c] from their credit pool, or 1[c] if that is all they have. If the Runner's credit pool is empty, the effect does nothing.
   3. c.linkTo spend or pay credits, a player puts the specified number of credits back into the bank. By default, the credits must come from the player's credit pool. Abilities can also allow players to spend credits hosted on their cards under certain conditions. If any such abilities apply, the player chooses how to divide the credits they are spending from among the allowed locations. The terms "spend" and "pay" are synonymous.
      1. Example: The Runner may use the credit from Cyberfeeder to pay for Atman's first ability.
      2. Example: The Runner may use credits from Ghost Runner when secretly spending credits to resolve a Psi ability (such as The Future Perfect).
      3. Example: The Runner must use credits from Ghost Runner if this is the only way for them to pay 3[c] when resolving the "when encountered" ability on Tollbooth.
4. 1.10.4.linkAbilities can place credits on cards, as discussed in section 1.13. Credits on a player's card are not in that player's credit pool; the player can only interact with those credits as instructed by card abilities.
   1. a.linkIf a player is instructed to take credits from a card, they remove that many credits from that card and gain those credits.
   2. b.linkIf an ability specifies how a player is allowed to spend credits from a card, they can be spent from that card as if they were in the player's credit pool for the specified actions or abilities.
   3. c.linkIf an ability specifies a time period during which a player is allowed to spend credits from a card, they can be spent from that card as if they were in the player's credit pool for any purpose (other than losing credits) as long as the specified time period is active or the specified duration has not expired.
   4. d.linkSpending credits from a card is considered "using" the card that allowed those credits to be spent. See section 9.1.6.
5. 1.10.5.linkRecurring Credits
   1. a.linkRecurring Credits ([recurring]) place credits on a card repeatedly. The text "N[recurring]" means "When this card becomes active, place N credits on it. Before abilities meet their trigger conditions for your turn beginning, if there are fewer than N credits on this card, place credits on it until there are N credits on it."
   2. b.linkRecurring credits are first placed on a card as soon as it becomes active. This occurs at step 8.5.15e of installing the card if it is installed active, step 8.6.6c of playing an event or operation, or as soon as the card is turned faceup or scored, as applicable.
   3. c.linkRecurring credits are refilled during step 5.6.1c of the Corp's turn and step 5.7.1c of the Runner's turn, before other abilities that apply at the start of the turn resolve.
   4. d.linkRecurring credits do not accumulate. They are refilled only up to the indicated number.
      1. Example: The Runner installs Spinal Modem, which has 2[recurring]. 2 credits are placed on Spinal Modem now. The Runner spends 1 of those credits later in their turn. At the beginning of the Runner's next turn, the credits on Spinal Modem should be replenished up to 2[c], so 1 more credit is placed on it.

1.11. Clickslink

Working a job, making connections, and especially jacking in—everything you do takes time, and it always goes by faster than you think. A click represents an abstract amount of time spent on a particular activity, either several hours all at once or scattered across the day.

1. 1.11.1.linkA click ([click]) is the basic unit of activity. Players spend their clicks to perform actions and trigger abilities. Each click counter represents 1 click.
2. 1.11.2.linkAs the first step of a player's turn, they gain an allotted number of clicks to spend during the action phase of that turn. See section 5 for details about the procedures of player turns.
   1. a.linkThe Corp receives 3[click] on each of their turns.
   2. b.linkThe Runner receives 4[click] on each of their turns.
3. 1.11.3.linkPlayers can gain, lose, or spend clicks.
   1. a.linkA player gains clicks whenever the number of clicks they have is increased.
   2. b.linkIf a player loses or spends clicks, the number of clicks they have is reduced by that amount. The terms "lose" and "spend" are not synonymous for the purposes of meeting conditions and restrictions of card abilities.
   3. c.linkPaid abilities that begin with [click] are actions and have special timing rules (see section 5.2). Aside from taking actions, there are no special restrictions to how or when a player can spend their clicks during their turn.
4. 1.11.4.linkSome cards have the subtype priority and the text, "Play only as your first [click]." A player can only play a priority card using the basic action to play an event or operation, and only if they have not spent any other clicks that turn. Losing clicks does not affect a player's ability to play a priority card.

1.12. Objectslink

1. 1.12.1.linkAn object is an occurrence of a card or counter existing in a particular zone. When a card or counter moves from one zone to another, it becomes a new object.
2. 1.12.2.linkRestrictions and effects on a card or counter only apply for as long as that card or counter remains the same object. Cards and counters have no memory of the objects they were in the past.
   1. Example: The Corp uses the first ability on Vaporframe Fabricator, which specifies that it can only be used once per turn, and trashes Vaporframe Fabricator during the installation process. Then the Corp plays Restore, reinstalling the same copy of Vaporframe Fabricator from Archives. Even though it is the same physical card, the reinstalled Vaporframe Fabricator is a new object, and its "once per turn" ability is available to be used this turn.
   1. a.linkAn ability that moves cards can identify the new objects that those cards become and continue to act on them.
      1. Example: The Corp plays Priority Construction, installing a piece of ice from HQ. That ice is now a new object in the play area, but Priority Construction's second instruction can still find it and place advancement counters on it.
3. 1.12.3.linkA card that moves from its location to a hidden or secret location becomes a new object, even if the new location is in the same zone.
   1. Example: The Corp scores Accelerated Beta Test, looks at the top 3 cards of R&D, and installs and rezzes a piece of ice from among them. As a chain reaction, the Corp then uses The Foundry: Refining the Process to search R&D, with the result that the other cards currently being looked at by Accelerated Beta Test are shuffled along with the rest of R&D. Since the cards were moved to an unknown location in R&D, Accelerated Beta Test can no longer act on them, so those cards can no longer be looked at and will not be installed or trashed.
   2. Example: The top card of R&D in the current game state is an object. So is the 2nd card from the top of R&D, the 3rd card, and so on. If the Corp plays Precognition and rearranges the top 5 cards of R&D, the Runner will not know which cards correspond to which objects in the previous order, so the cards become new objects under their new order.
4. 1.12.4.linkA card or counter that moves to a known location in the same zone is still the same object.
   1. Example: The Runner has chosen a piece of ice with Femme Fatale, and the Corp uses Thimblerig's ability to move that ice to another location. But the ice has not left the play area, so it is still the same object and the Runner can still use Femme Fatale's ability to bypass it.
5. 1.12.5.linkA card that is turned faceup or facedown is still the same object.
   1. Example: The Corp uses Vaporframe Fabricator, installing a piece of ice at no cost, and then plays Divert Power to derez Vaporframe Fabricator and rez their newly-installed ice at a discount. The Corp can rez Vaporframe Fabricator again, but since it is still the same object, its "once per turn" ability cannot be used again this turn.
6. 1.12.6.linkWhen a card or counter becomes a new object, its previous object ceases to exist, but can still be remembered by rules or abilities that refer to past game states.
   1. Example: The Runner plays Bravado. During the run, a piece of ice that the Runner has already passed is trashed. When the run ends, Bravado's ability must determine how many pieces of ice the Runner passed during that run. It does this by reviewing the game history and counting each distinct ice object that the Runner passed. Even though the object corresponding to the trashed ice no longer exists in the present game state, Bravado can still count it.
   2. Example: The Runner trashes the top card of R&D while accessing it. The object corresponding to that card in its location on top of R&D ceases to exist, but still counts against the number of cards the Runner can access from R&D during this breach.

1.13. Host, Hosted and Hostinglink

1. 1.13.1.linkWhenever an object is "placed" or "loaded" onto a card, a host relationship is created between those two objects. The object placed on top of a card is hosted on that card. The card onto which the other object is placed is the host.
   1. a.linkOnly cards in score areas and the play area can host objects.
2. 1.13.2.linkThe state of being hosted is distinct, but not exclusive from, the state of being installed. If an ability instructs a player to host a card from an inactive state without reference to installing it, the hosted card remains inactive.
3. 1.13.3.linkAn object can only be hosted on a single card at any given time.
4. 1.13.4.linkA card can host any number of other objects, except where explicitly restricted by a card ability.
5. 1.13.5.linkAny card in an eligible location can act as a host, but a host relationship can only be created or permitted by a card ability.
   1. a.linkIf a card has an ability describing the types and/or numbers of cards it can host, but it does not have an ability that directly hosts cards onto itself, then the card is permitted as an eligible installation destination for the types of cards listed, up to the number specified. A host card is chosen as an installation destination during step 8.5.15b of the installation process.
      1. Example: Off-Campus Apartment has the ability, "Off-Campus Apartment can host any number of connections." This means that whenever the Runner installs a connection card, they can choose to install that card into the play area hosted on Off-Campus Apartment or as normal directly into the play area.
   2. b.linkIf a card has an ability describing cards it can host, but also one or more abilities that can create host relationships onto itself, then it only allows cards to become hosted on it through those abilities. A card cannot be installed directly onto the card through an unrelated install effect.
      1. Example: Glenn Station reads, "Glenn Station can host a single card", but also has a paid ability that hosts a card on itself. Therefore, Glenn Station only lets the Corp host cards through that paid ability, not through an install action.
   3. c.linkIf a card has an ability stipulating that it can only be installed hosted onto another card, then during the installation process a player that wishes to install that card must choose a valid destination matching the description provided. If no such destination exists before the installation process begins, the card cannot be installed.
      1. Example: Egret states, "Install only on a rezzed piece of ice." The Runner can only install Egret if there is an installed, rezzed piece of ice available before the installation process begins; otherwise, it is illegal for the Runner to install Egret.
   4. d.linkSome operations and events convert themselves into condition counters and install themselves hosted onto other cards. An operation or event can never be installed through an install effect; it can only become an installed counter through its conversion ability. See rule 10.1.4.
6. 1.13.6.linkCards can be hosted faceup or facedown.
   1. a.linkUnless otherwise specified, a card that is hosted while it is being installed is hosted onto the destination card in the same faceup or facedown status it would normally be installed in.
   2. b.linkUnless otherwise specified, a card that is hosted without being installed is hosted faceup.
   3. c.linkLike other facedown installed cards, installed cards hosted facedown are distinct. The order in which they were installed (or turned facedown) is open information.
   4. d.linkCards hosted facedown without being installed must be kept in distinct groups according to their host. Cards within such a group are not ordered and can be freely arranged by their controller.
7. 1.13.7.linkOnce a card is installed, hosted or not, a player cannot change that card's hosted status unless a card ability explicitly directs it to be hosted onto a new card.
8. 1.13.8.linkHost relationships are not transitive. If card A is hosted on card B, and card B is hosted on card C, card A is not considered to be hosted on card C.
   1. Example: If the Runner installs a Leprechaun hosted on a Dhegdheer, programs hosted on Leprechaun do not have their install costs reduced because they are hosted on Leprechaun and not on Dhegdheer.
9. 1.13.9.linkIf an ability on a card refers to a "hosted" card or counter, that ability only references objects hosted on that card.
10. 1.13.10.linkHosted objects can be removed or spent from their host without affecting the host.
11. 1.13.11.linkIf a host card changes zones, all objects hosted on that card (and all objects hosted on those objects, and so on) are trashed during the next checkpoint. This cannot be prevented. See section 10.3 for details on checkpoints.
12. 1.13.12.linkCondition counters are the only type of counter that can host other objects. Hosting on condition counters follows the same rules as hosting on cards.

1.14. Ownership and Controllink

1. 1.14.1.linkThe owner of a card is the player who provided that card at the start of the game as their identity, part of their deck, or an extra card along with their deck.
   1. a.linkA card that is converted into a counter retains its owner.
   2. b.linkNo player owns counters that are not converted cards.
2. 1.14.2.linkThe controller of an object is the player responsible for that object.
   1. a.linkThe controller of a card in the play area is the player who installed or placed it there.
   2. b.linkThe Corp controls each agenda in the Corp's score area. The Runner controls each agenda in the Runner's score area.
   3. c.linkCards in other zones are controlled by their owner.
   4. d.linkEach player controls the credits in their credit pool.
   5. e.linkThe Corp controls each bad publicity counter. The Runner controls each tag counter. However, see rule 10.5.5 and rule 10.6.3 regarding paying costs that involve tags and bad publicity, respectively.
   6. f.linkThe controller of a counter hosted on a card is the player who controls the host card.
   7. g.linkClick counters and core damage counters are gameplay aids only and have no controller.
3. 1.14.3.linkA player can only pay costs using objects they control.
4. 1.14.4.linkThe controller of an ability is the player responsible for that ability. By default, this is the player who controls the ability's source. See also section 9.1.3. A player can only use abilities they control.
   1. a.linkUnless specifically stated otherwise, abilities on agendas are controlled by the Corp, even for agendas in the Runner's score area.
   2. b.linkSome abilities state that they can only be used by a specific player. The specified player controls each such ability, even if they do not control its source.
5. 1.14.5.linkUnless otherwise noted, the controller of an ability carries out its effects and makes any choices required. If a player is specified to perform all or part of an effect, the specified player carries out that part of the effect and makes any choices required instead.
   1. Example: Rototurret's first subroutine reads, "Trash 1 installed program." Since Rototurret is a Corp card, the Corp chooses which installed program to trash. Conversely, Bulwark's first subroutine reads, "The Runner trashes 1 installed program." Since the Runner is specified to be carrying out this effect, they choose which of their installed programs to trash.
   1. a.linkSome trigger conditions care about effects performed by a particular player. These conditions are only met when that player is the one to carry out the relevant effect.
      1. Example: The Corp has a rezzed Hostile Infrastructure. Apocalypse does not specify who trashes the cards, so the Runner is responsible for the trashing and Hostile Infrastructure meets its trigger condition.
      2. Example: Alice Merchant states that "the Corp must trash 1 card from HQ", so the Corp carries out this effect even though Alice Merchant is a Runner card, and therefore Hostile Infrastructure does not meet its trigger condition.

1.15. Targetslink

1. 1.15.1.linkMany abilities require players to choose 1 or more objects or subroutines to affect. Each object and subroutine chosen for an ability is a target of that ability.
   1. Example: Top Hat reads in part, "you may choose 1 of the top 5 cards of R&D and access it." The target of this instruction is the card in R&D the Runner chooses.
   2. Example: One of the subroutines on Colossus reads in part, "Trash 1 installed program and 1 installed resource." The targets of this subroutine are the two cards that will be trashed.
   3. Example: Trick of Light reads, "Choose 1 installed card you can advance. Move up to 2 advancement counters from 1 other card to the chosen card." The targets of this operation are the advancement counters to be moved and the destination card. If 2 tokens are chosen, they must be hosted on the same card.
   4. Example: The Runner is encountering a barrier and uses Cleaver to break subroutines. The targets of Cleaver's' interface ability are the 1 or 2 subroutines that it will break.
   1. a.linkCards found during a search are not considered targets of the instruction that performs the search. Players do not need to announce what card(s) they expect to find before the search actually takes place. See section 8.7 for rules about searching.
   2. b.linkOnly objects and subroutines are announced as targets. If an instruction directs a player to choose (or "name") a number, a card type, a subtype, a card name, a server, or one of a specified set of effects, that choice is not made until the instruction resolves.
2. 1.15.2.linkImmediately before an instruction becomes imminent, the player resolving that instruction must first choose the targets required by that instruction. For each time the instruction requires a player to choose 1 or more objects and/or subroutines, that player announces appropriate targets. Once players are finished announcing targets for an instruction, the instruction becomes imminent, and players have the opportunity to modify the effects of that instruction with interrupt abilities before it resolves. See section 9.9.
   1. a.linkWhen a player announces a card as a target, they indicate clearly which card is being chosen without changing its facedown/faceup status or location.
   2. b.linkThe player resolving the instruction can only choose targets that are valid for that instruction. A target is valid for an instruction if it meets any specified requirements of that instruction or can otherwise be acted upon by that instruction.
   3. c.linkUnless an instruction explicitly specifies the zone from which an object must be selected as a target, only counters in the play area and installed cards are valid targets for that instruction.
      1. Example: The Corp resolves a subroutine that says "[sub] The Runner trashes 1 program." The Runner must trash 1 of their installed programs and may not trash a program from their grip or stack.
   4. d.linkSome effects allow a player to choose multiple cards as targets for a single announcement. Section 9.12.2 contains rules about resolving effects involving sets of cards.
   5. e.linkA player may announce the targets for an instruction in any order, but each object or subroutine can only be chosen as a target once for each announcement. If there are not enough valid targets available, then that player chooses as many distinct targets as possible and the remaining targets are not announced.
      1. Example: The Runner accesses an Aggressive Secretary with three advancement counters on it. The Runner only has two installed programs, so the Corp chooses both of those programs for Aggressive Secretary. After the programs have been chosen, they are both trashed simultaneously.
   6. f.linkTargets cannot be chosen for an instruction at any other time. Even if the game state changes due to interrupt abilities while the instruction is imminent, unannounced targets remain unchosen.
3. 1.15.3.linkAt the time an instruction resolves, if any of its targets either have become invalid or were not announced, as much of that ability resolves as possible without acting on the unannounced or invalid targets, following rules 1.2.3 and 1.2.4 of the Golden Rules. A target can be invalid because the chosen object or subroutine no longer exists or because the target no longer meets other requirements specified by the targeting ability.
4. 1.15.4.linkAfter the resolution of an instruction that chose a particular target, subsequent instructions of the same ability can continue to act on that target without needing to select it again, even if the ability moves the target or changes its properties. See also section 1.12.2.
   1. Example: Howler's ability targets a card in HQ. Its first instruction installs that card, and its second instruction creates a delayed conditional ability that refers to that card in the play area. The latter ability can find and act on the card as long as it is still installed.

1.16. Costslink

1. 1.16.1.linkIn order to use an ability or apply an effect, a player may be required to pay a cost. A cost can take the form of any card, counter, or other item a player must spend; an effect a player must resolve; or other type of requirement a player must meet. If a player cannot pay the full cost of an action or ability all at once with cards and counters they control, they cannot use the effect associated with that cost.
   1. a.linkThe act of paying a cost cannot be modified or cancelled by optional interrupt abilities.
      1. Example: The Runner can trash Clone Chip to trigger its paid ability, but cannot use LLDS Energy Regulator to prevent Clone Chip from being trashed this way.
   2. b.linkIf a static ability or a mandatory conditional ability interrupt would prevent the steps of paying a cost from being carried out if they were performed as an effect, that cost cannot be paid.
      1. Example: The Runner cannot pay the additional cost to steal Obokata Protocol while Guru Davinder is installed, because the Runner could not currently take 4 damage if instructed to: Guru Davinder's first ability would prevent the damage.
      2. Example: The Runner is playing as Jesminder Sareen and encounters Funhouse, without any other tag-related effects resolving earlier in the run. Since Jesminder's ability would prevent taking 1 tag, the Runner cannot take 1 tag to pay the nested cost in Funhouse's ability. Funhouse will end the run.
   3. c.linkIf triggering an ability or resolving an effect is subject to both costs and other restrictions, the cost cannot be paid unless all such restrictions are met, and cannot be paid in a way that would result in any restriction no longer being met.
      1. Example: The Runner controls Zer0 and Clan Vengeance, and wants to accumulate more power counters on Clan Vengeance. Zer0's ability has the restriction "Use this ability only once per turn." If the Runner has already used the ability this turn, they cannot suffer additional net damage by attempting (even unsuccessfully) to use the ability again.
      2. Example: The Corp installs Azef Protocol in the root of a server with a rezzed SanSan City Grid and advances Azef Protocol twice. Since SanSan City Grid reduces Azef Protocol's advancement requirement to 2, the Corp now meets the restriction necessary to score Azef Protocol, but must also pay its additional cost to score. The Corp cannot trash the SanSan City Grid to pay this cost, because paying the cost this way would return Azef Protocol's advancement requirement to 3, and the restriction to score it would no longer be met.
   4. d.linkA cost of 0 can still be paid by a player, even though no items are paid. Costs of 0 are not paid automatically. A player pays a cost of 0 by explicitly announcing they are paying it.
      1. Example: The Runner accesses a Beanstalk Royalties from R&D and announces that they are using the ability of Freedom Khumalo: Crypto-Anarchist to trash the Beanstalk Royalties. Even though the Runner does not remove any virus counters from any cards, they have still paid the cost.
2. 1.16.2.linkThe actual contents of a cost can be dependent on the game state. Abilities can modify their own costs, modify costs of a certain type or that meet certain criteria, or include costs that need to be calculated.
   1. a.linkIf a quantity in a cost is subject to effects modifying its value, determine the final value of that quantity by taking its default value, applying each effect that increases the cost, and then applying each effect that lowers the cost. Finally, if the value determined by this process is less than 0, set the value to 0.
   2. b.linkSome abilities calculate a quantity using phrases like "for each", "for every", or "plus". Any time such a calculation appears in a cost, the result of that calculation is determined at the time the cost is to be paid. The result is taken as an aggregate, so that paying the cost is a single instance of whatever was paid. Note that additional costs (section 1.16.11) are not aggregated with other costs. See also Section 9.12.2 for rules about calculated quantities that appear in other contexts.
      1. Example: The Runner approaches a server protected by 3 advanced pieces of ice and with a rezzed Cayambe Grid in its root. They pay the nested cost in Cayambe Grid's ability. This cost is 1 payment of 6[c], not 3 payments of 2[c], so this only meets the trigger condition for 1 instance of GameNET's ability.
   3. c.linkSome costs contain the variable X. Before a player pays such a cost, they choose and announce a positive integer or 0 to be the value for X. The chosen value must follow any applicable restrictions.
      1. Example: Psychographics is an operation with a play cost of X. It also has the ability, "X must be equal to or less than the number of tags the Runner has." If the Runner has 3 tags, the Corp can choose 0, 1, 2, or 3 as the value for X when they play Psychographics.
   4. d.linkIf an ability needs to know the value of a cost in a context where that cost is not being paid, treat any X that appears in that cost as 0.
3. 1.16.3.linkAfter a player pays a cost, a checkpoint occurs. See section 10.3.
4. 1.16.4.linkThere are six main types of costs: install costs (found mainly on hardware, programs, and resources, and incurred when installing ice), play costs (found on operations and events), rez costs (found on assets, upgrades, and ice), paid ability trigger costs, additional costs, and nested costs.
   1. a.linkInstall costs, rez costs, and play costs are all costs that are inherent properties of cards. These costs are automatically applied to any ability that performs the corresponding effects (installing, rezzing, or playing) unless that ability stipulates otherwise. See also section 2.3 (for more about these costs as they appear on cards) and section 8.5.11, rule 8.1.2d and section 8.6.2 (for more about paying costs to install, rez, and play cards).
   2. b.linkThe presence of an install cost, rez cost, or play cost does not change the optional or mandatory status of an ability. If an effect directs a player to install, rez, or play a card, they must pay the associated cost if able. If they cannot, the card is not installed, rezzed, or played.
   3. c.linkIf an effect directs a player to install, rez, or play a card, but doing so has an additional cost, the player is not forced to pay the additional cost. If they decline to do so, they do not pay the install, rez, or play cost either, and the card is not installed, rezzed, or played.
   4. d.linkWhen a player takes an action that plays or installs one or more cards and has no other effects, the play cost or install cost of each of those cards is considered to have been spent to take that action, even though other steps take place between initiating the action and paying that cost.
      1. Example: The Corp has Jeeves Model Bioroids rezzed, and uses the basic action "[Click]: Play an operation." to play Blue Level Clearance. Both the click spent for the cost of the basic action and the click spent for Blue Level Clearance's additional cost count as clicks spent to take the "[Click]: Play an operation." action.
5. 1.16.5.linkSome abilities direct a player to ignore certain costs when performing particular effects.
   1. a.linkIf a player is directed to ignore 1 or more of the 6 main types of costs, the specified costs are removed from the total cost that must be paid. Any other costs (usually additional costs) that are not specified to be ignored still apply normally.
   2. b.linkIf a player is directed to ignore "credit costs", any credits to be paid from any type of cost are removed from the total cost. Any costs that do not consist of credits still apply normally.
   3. c.linkIf a player is directed to ignore "all costs", all elements of the relevant cost are removed, including additional costs, so that the total cost becomes 0.
6. 1.16.6.linkThe install cost of a card must be paid to install that card.
   1. a.linkThe install cost of a program, resource, or piece of hardware is listed on the card itself.
   2. b.linkThe install cost of a piece of ice is a number of credits equal to the number of pieces of ice already protecting the server that ice will be installed protecting.
   3. c.linkThere is no cost to install an asset, upgrade, or agenda.
7. 1.16.7.linkThe play cost of an operation or event must be paid to play that card. It is listed on the card itself.
8. 1.16.8.linkThe rez cost of an asset, upgrade, or piece of ice must be paid in order to rez that card. It is listed on the card itself.
9. 1.16.9.linkThe trigger cost of each paid ability is the first part of that ability's text. It is followed by a colon (:) and then the ability's effect. See section 9.5 for more details on paid abilities.
10. 1.16.10.linkAn additional cost adds something to the regular cost of initiating a particular game effect. A player must pay all additional costs along with any regular costs in order to initiate an effect.
    1. a.linkIf a player would be forced to carry out a game effect, but doing so has an additional cost, that player may decline to pay the additional cost, even if they are able to pay it, thus preventing that effect from occurring.
       1. Example: The Runner accesses Obokata Protocol. Normally the Runner must steal agendas that they access, but because Obokata Protocol has an additional cost to steal, the Runner can decline to suffer the net damage and not steal the agenda.
    2. b.linkA player must pay all additional costs simultaneously with the cost that is being added to, even if multiple cards or abilities are adding separate additional costs. A player cannot pay the original cost or any of the additional costs individually. If they cannot pay for all of the costs at once, then they do not pay any of the costs and the corresponding effects cannot occur.
       1. Example: The Runner accesses Obokata Protocol while Ben Musashi and Predictive Algorithm are both active. The Runner must be able to pay 2 credits and suffer 6 net damage all at once in order to steal the Obokata Protocol, even though each of the three costs are from different card abilities. After all costs have been paid, abilities that meet their trigger conditions from the paying of any of those costs, such as I've Had Worse or Order of Sol, can then resolve as applicable.
    3. c.linkIf an additional cost is required for an effect that does not normally require paying any cost, the additional cost is paid and a checkpoint is resolved before performing the usual procedure to carry out that effect. See also rule 10.3.4.
       1. Example: The Corp is playing Ob Superheavy Logistics and initiates scoring Azef Protocol, which has an additional cost to score of "trash one of your other installed cards." If the Corp trashes a rezzed card, meeting the trigger condition for Ob's ability, this ability will resolve following the checkpoint associated with paying the cost. This happens before Azef Protocol is added to the Corp's score area or any trigger conditions related to scoring an agenda are met.
11. 1.16.11.linkA nested cost is a cost appearing within an ability's instructions that must be paid while the ability is resolving in order for some or all of the rest of the effects of that ability to resolve.
    1. a.linkNested costs are usually written in the format "[player] may [cost] to [instructions]" or "[player] may [cost]. If [you/they] do, [instructions]." If the indicated player pays the indicated cost, the indicated instructions are resolved. Otherwise, that part of the ability is not resolved.
    2. b.linkNested costs can also be written in the format "[instructions] unless [player] [cost]" or "[player] may [cost]. If [you/they] do not, [instructions]." If the indicated player pays the indicated cost, the indicated instructions are not resolved. Otherwise, that instruction is resolved.
       1. Example: A subroutine reading "End the run unless the Runner pays 1[c]." contains a nested cost. If the Runner chooses to pay 1[c], the subroutine will not end the run.
    3. c.linkAn ability that reads "If [you/they] do" or "If [you/they] do not" without a preceding "may" does not indicate a nested cost.
    4. d.linkSome abilities use the word "otherwise" to indicate that different instructions should be resolved depending on whether a nested cost was paid or not. In an ability with a nested cost of a form described in rule 1.16.11a, treat "otherwise" as an "if [you/they] do not" clause attached to the same cost. Conversely, in an ability with a nested cost of a form described in rule 1.16.11b, treat "otherwise" as an "if [you/they] do" clause attached to the same cost. Note that "otherwise" can also appear in the context of other types of conditions, and does not by itself indicate a nested cost.

1.17. Score, Scoring and Stealinglink

1. 1.17.1.linkThe sum of all agenda points on agendas in a player's score area is that player's score.
   1. a.linkThe threat level is equal to the greatest score of any player. The "Threat N" ability flag makes use of the threat level (rule 9.3.6f).
      1. Example: If the Runner's score is 4 agenda points, and the Corp's score is 3 agenda points, the threat level is 4.
2. 1.17.2.linkIf at any time a player's score is greater than or equal to 7, they win the game at the next checkpoint. See section 1.7 regarding winning the game, and section 10.3 for details about checkpoints.
3. 1.17.3.linkPlayers add agendas to their score areas by scoring or stealing them. The Corp can score an agenda to their score area as an option during certain paid ability windows on their turn. The Runner can steal an agenda to their score area while accessing it.
   1. a.linkThe advancement requirement of an agenda restricts when the Corp can score it. The Corp can only score an agenda that has advancement counters on it greater than or equal to its advancement requirement. See section 1.18.
   2. b.linkThe Corp is not required to score an agenda immediately upon satisfying its advancement requirement.
   3. c.linkScoring an agenda does not cost [click] and is not an action.
   4. d.linkThe Runner cannot decline to steal an agenda they access, unless there is an additional cost to steal that agenda and the Runner cannot or does not wish to pay it. Section 7 details accessing, and section 1.16.10 details additional costs.
   5. e.linkIf an effect directly adds an agenda to a score area or otherwise moves an agenda from any zone to a score area, that agenda is not considered scored or stolen.
   6. f.linkIf an effect causes another card to be added to a score area "as an agenda", the newly converted agenda is not considered scored or stolen. See rule 10.1.3.
4. 1.17.4.linkAgendas are always added to the score area faceup, regardless of their previous faceup/facedown status.
5. 1.17.5.linkIf an installed agenda is scored or stolen, it becomes uninstalled. Any advancement counters on the scored or stolen agenda are returned to the bank. See rule 1.13.11.
6. 1.17.6.linkSome agendas and other cards have abilities with a trigger condition related to an agenda being scored. These abilities become pending after the Corp moves the agenda from its current zone to their score area.
7. 1.17.7.linkSome agendas and other cards have abilities with a trigger condition related to an agenda being stolen. These abilities become pending after the Runner moves the agenda from its current zone to their score area.
8. 1.17.8.linkIf an ability meets its trigger condition from an agenda being scored or stolen, the agenda's last known number of advancement counters before being scored or stolen is used for any references to the number of advancement counters in the effects of that ability.

1.18. Advancing Cardslink

1. 1.18.1.linkTo advance a card is to place an advancement counter from the bank on it. The Corp typically advances cards with a basic action during their action phase, but card abilities can also advance cards.
2. 1.18.2.linkResolving an instruction that directly places an advancement counter onto a card is not the same as advancing a card. Likewise, resolving an instruction that moves an advancement counter from one card to another is not the same as advancing a card.
   1. Example: The Corp plays Mushin-no-Shin, choosing to install an Oaktown Renovation. Because the three advancement counters were placed on the card directly, the Corp does not gain any credits from the ability on Oaktown Renovation.
3. 1.18.3.linkThe Corp can only advance certain installed cards. Agendas can always be advanced. If a card other than an agenda says that it "can be advanced" or that "you can advance" that card, the card can be advanced even while it is unrezzed. There is no limit to the number of times a card can be advanced.
4. 1.18.4.linkAn "advanced card" is a card with 1 or more advancement counters hosted on it.

1.19. Trashinglink

1. 1.19.1.linkTrashing is the act of moving an object to its owner's discard pile.
2. 1.19.2.linkDuring access, the Runner has the opportunity to pay the trash cost of the accessed card to trash it. See section 7.1.5.
3. 1.19.3.linkA trashed card is not considered to have been discarded, and vice versa. Cards that prevent a card from being trashed cannot prevent a card from being discarded.
4. 1.19.4.linkThe symbol [trash] represents trashing the object it appears on. It is used as a cost for certain abilities.
   1. Example: Fall Guy's last ability reads "[trash]: Gain 2[c]." The cost to trigger this ability is to trash Fall Guy.
   1. a.link"A [trash] ability" refers to a paid ability that includes [trash] in its trigger cost.
   2. b.linkSome paid abilities have multiple options for their trigger cost, separated by "or". A player triggering such an ability only "used a [trash] ability" if the actual cost that was paid includes [trash].

1.20. Memorylink

1. 1.20.1.linkA memory unit (MU) is a space available to the Runner to install programs. Memory units always appear with a quantity, such as 2[MU], which means "2 memory units."
2. 1.20.2.linkThe Runner's memory limit is the total number of memory units the Runner has. If the Runner's identity card does not specify a starting memory limit, their starting memory limit is 4[MU]. Card abilities that indicate +[MU] apply that increase to the Runner's memory limit.
   1. Example: The Runner has Astrolabe installed, which has the ability "+1[MU]". The Runner can therefore have up to 5[MU] worth of programs installed.
3. 1.20.3.linkPrograms have a memory cost that is continually applied against the memory limit. section 3.9.3 details how the Runner's installed programs are constrained by the memory limit.

1.21. Card Visibilitylink

1. 1.21.1.linkCards in the play area and other public zones are either faceup or facedown. Faceup cards are freely visible to all players. Facedown cards are oriented so that the face containing the card's information is not visible.
   1. a.linkCards in hidden or secret zones (see section 4.1) are neither faceup nor facedown.
   2. b.linkSome effects host multiple cards on an object at the same time or set aside multiple cards at the same time. Facedown cards that enter a zone at the same time by the same effect are treated as a group. See section 1.13.6 and rule 4.8.7, respectively.
2. 1.21.2.linkWhen a player looks at a card, they are allowed to see the front face of the card even if the front face would not normally be visible to them. A player should look at that card without showing it to the other player if it is not normally visible to that player.
   1. a.linkA player may look at facedown cards they control at any time.
3. 1.21.3.linkTo reveal a card is to show its front face to all players, then return it to its previous state.
4. 1.21.4.linkSome abilities instruct the Runner to expose one or more cards. To expose a card is to reveal it, except that only installed, unrezzed cards can be exposed.
5. 1.21.5.linkEffects that instruct a player to look at, reveal, expose, or access a card are not the same, even if they would be performed similarly at times. See section 7 for more information on accessing.
6. 1.21.6.linkIf a resolving ability directs one or both players to look at or reveal a card or set of cards, each such card remains visible to the relevant player(s) until the entire ability is finished resolving or the card moves to a different location.
7. 1.21.7.linkThe ability "While the Runner is accessing this [type] in R&D, they must reveal it." is a static ability that applies for the entire duration of the access. This is also the case for cards with the older wording, "If [this card] is accessed from R&D, the Runner must reveal it."

2. Parts of a Cardlink

2.1. Namelink

1. 2.1.1.linkThe identifier of a card is its name, alternatively referred to as its title. It is written along the top of the card for identities, agendas, ice, operations, events, and resources, or immediately below the art box in the case of assets, upgrades, hardware, and programs.
2. 2.1.2.linkIdentities have a subtitle written immediately below the main title line. Their full name is the combination of their main title and subtitle.
3. 2.1.3.linkWhen a card refers to its own name, it is a self-reference. See rule 10.1.5.
4. 2.1.4.linkWhen a card refers to "copies of" cards with a particular name, it refers to any card with that name.
5. 2.1.5.linkIf a player is directed to choose or search for cards "with different names", each card chosen or found by the search must have a different English name from every other card chosen or found. See also section 8.7.

2.2. Unique Symbollink

1. 2.2.1.linkSome cards are unique, and have a unique symbol (◆) before their name to designate this. See rule 10.1.1.

2.3. Play Cost, Install Cost, or Rez Costlink

1. 2.3.1.linkThe play, install, or rez cost of a card is a number that appears in the top-left corner of most card types. Play and install costs appear within a large circular icon, while rez costs appear within a small octagonal icon.
2. 2.3.2.linkPlay, install, and rez costs on cards are all paid in credits. section 8 details how cards are played, installed, and rezzed.
3. 2.3.3.linkEvents and operations have a play cost.
4. 2.3.4.linkHardware, programs, and resources have an install cost.
   1. a.linkIce also has an install cost, but it does not appear on the card. The install cost of ice is determined by the configuration of other installed ice rather than being intrinsic to the card. See section 1.16.6.
5. 2.3.5.linkAssets, ice, and upgrades have a rez cost.

2.4. Advancement Requirementlink

1. 2.4.1.linkThe advancement requirement appears only on agendas. It is a number in the top-right corner of the card, within a small circle.
2. 2.4.2.linkSection 1.17 details how agendas are scored and the purpose of the advancement requirement.

2.5. Agenda Pointslink

1. 2.5.1.linkThe agenda point value appears only on agendas. It is the number in the center-left of the card, on top of a graphic depicting three pillars.
2. 2.5.2.linkThe agenda points in a player's score area contribute toward that player winning the game. See section 1.7.

2.6. Trash Costlink

1. 2.6.1.linkAssets, upgrades, and some ice and operations have trash costs. A trash cost is a number appearing in the lower-right corner of the card within a [trash] symbol.
2. 2.6.2.linkSection 7.1.5 details how the Runner can trash a card they access by paying its trash cost.

2.7. Strengthlink

1. 2.7.1.linkStrength is a number appearing on ice and on icebreaker programs. It appears on the bottom-left corner of the card within a large semicircle.
2. 2.7.2.linkNon-icebreaker programs have a dash ([dash]) in the bottom-left corner instead of a strength value.
3. 2.7.3.linkSection 3.9.5 discusses the interaction between ice strength and icebreaker strength.

2.8. Memory Costlink

1. 2.8.1.linkMemory Cost is a number appearing only on programs. It appears to the right of the install cost, within an [MU] symbol.
2. 2.8.2.linkSection 1.20 discusses the topic of memory, and section 3.9.3 details how programs interact with the Runner's memory limit based on their memory cost.

2.9. Base Linklink

1. 2.9.1.linkBase link is a number appearing in the top-left of Runner identity cards.
2. 2.9.2.linkThe Runner's base link contributes to their link value. section 10.7 defines how the Runner's link value is calculated, and section 10.8 explains how it contributes to contesting trace attempts.

2.10. Starting Memory Limitlink

1. 2.10.1.linkStarting memory limit is a number appearing near the top-left of Runner identity cards, within the [MU] symbol.
2. 2.10.2.linkThe Runner's memory limit is checked against the total memory cost of programs they have installed. This value is calculated by applying any active modifiers to the Runner's starting memory limit. See section 1.20.

2.11. Minimum Deck Sizelink

1. 2.11.1.linkMinimum deck size is a number shown as the uppermost of two small boxes in the lower-left of Corp identities and the lower-right of Runner identities.
2. 2.11.2.linkSection 1.4 details the rules for building a deck, including the requirement to adhere to the minimum deck size of the deck's associated identity.

2.12. Influence Limitlink

1. 2.12.1.linkThe influence limit is a number shown as the lowermost of two small boxes in the lower-left of Corp identities and the lower-right of Runner identities.
2. 2.12.2.linkSection 1.4 details the rules for building a deck, including the requirement that out-of-faction cards in the deck adhere to the influence limit of the associated identity.

2.13. Faction Affiliationlink

1. 2.13.1.linkCards are divided into ten factions: four Corp factions, three Runner factions, and three Runner mini-factions. Factions and influence restrict deckbuilding options, allowing each faction to have distinct play differences from one another.
   1. a.linkThe Corp factions are Haas-Bioroid, Jinteki, NBN, and the Weyland Consortium.
   2. b.linkThe major Runner factions are Anarch, Criminal, and Shaper.
   3. c.linkThe Runner mini-factions are Adam, Apex, and Sunny Lebeau.
2. 2.13.2.linkA card's faction can be identified by the color of its background, as well as a faction logo in one of its four corners. This logo also appears as a watermark behind the text box. If a card has a white background and no logo, it is neutral.
3. 2.13.3.linkEach identity is associated with one faction. section 1.4 details how factions affect deckbuilding.

2.14. Influence Costlink

1. 2.14.1.linkA card's influence cost, or influence value, is represented in a bar with 5 circular slots near the bottom of most cards. The influence cost is the number of slots that are filled with a blue circle, and can range from 0 to 5.
2. 2.14.2.linkSome cards cannot be played out of faction, and therefore do not have an influence value, which is different from an influence cost of "0". These cards do not have the influence bar at all.
3. 2.14.3.linkSome Corp cards have the subtype alliance and text defining adjustments to their influence costs. The ability adjusting the influence cost of an alliance card applies only when determining the legality of an already constructed deck and does not have any effect during gameplay. The ability references other cards included in the deck to determine whether the card should apply its printed influence cost or 0 against the deck's influence limit.
4. 2.14.4.linkSection 1.4 details how a card's influence cost (or lack thereof) affects deckbuilding.

2.15. Card Typelink

1. 2.15.1.linkA card's types appear as a line of text across the center of non-ice cards above the text box. For ice, they run along the left side of the text box, rotated 90° from the rest of the text.
2. 2.15.2.linkEach card has one card type, which can be identity, agenda, asset, ice, operation, upgrade, event, hardware, program, or resource. It is written in bold at the beginning of the type line.
3. 2.15.3.linkWhile inactive, a card is still considered a card of the type printed on it, with the exception of facedown installed Runner cards. See section 8.1.4.
4. 2.15.4.linkAbilities can change a card from its printed type to an agenda. See rule 10.1.3.
5. 2.15.5.linkCounters never have card types.

2.16. Subtypeslink

1. 2.16.1.linkCards may have one or more subtypes, which are written following the primary type. Subtypes are card descriptors that can be referenced by card abilities. Cards that share a subtype often share a distinct characteristic or ability.
   1. a.linkThe subtypes region, console, and icebreaker have special rules, discussed in sections 3.6.5, 3.8.5 and 3.9.5 respectively. Other subtypes have no intrinsic rules meaning.
2. 2.16.2.linkIn card text, subtypes are always referenced in bold text. If a word or phrase that is also a subtype appears in a card's text but is not in bold text, that word or phrase does not reference the subtype.
3. 2.16.3.linkSome abilities reference cards by a lack of subtype, such as "non-virus". These abilities can only affect cards that do not have the specified subtype, regardless of any other subtypes the cards do have.
4. 2.16.4.linkA card has all of its subtypes at all times, even while inactive, with the exception of facedown installed Runner cards. See section 8.1.4.
5. 2.16.5.linkAbilities can add or remove subtypes. The number of times a card has, gains, and loses each subtype is tracked as a running total, but the result is binary: if the total number of instances of the subtype exceeds the number of times it is removed, the card has that subtype. Otherwise, it does not.
   1. Example: The Runner plays Tinkering on a Lycan hosting 1 advancement counter. Lycan has two instances of sentry, one printed and one from Tinkering, and has lost one instance of sentry from its own ability. Thus it is still a sentry.
6. 2.16.6.linkIf an effect requires a player to choose a subtype, that player must choose a single subtype that has been printed on at least one card. If a player is required to choose a subtype belonging to a specific card type, they must choose a subtype that has been printed on at least one card with that type.
7. 2.16.7.linkBelow is a list of all subtypes.
   1. a.linkThe identity subtypes are Bioroid, Clone, Corp, Cyborg, Digital, Division, G-mod, Megacorp, Natural, Police Department, Stealth, and Subsidiary.
   2. b.linkThe agenda subtypes are Ambush, Assassination, Expansion, Expendable, Initiative, NEXT, Psi, Public, Research, Security, Sensie, and Source.
   3. c.linkThe asset subtypes are Academic, Advertisement, Alliance, Ambush, Beanstalk, Bioroid, Cast, Character, Clone, Corporation, Enforcer, Executive, Facility, Government, Hostile, Illicit, Industrial, Political, Psi, Region, Research, Ritzy, Seedy, and Transaction.
   4. d.linkThe ice subtypes are AP, Advertisement, Ambush, Barrier, Bioroid, Code Gate, Deep Net, Deflector, Destroyer, Expendable, Grail, Harmonic, Illicit, Morph, Mythic, NEXT, Observer, Psi, Sentry, Tracer, and Trap.
   5. e.linkThe operation subtypes are Alliance, Black Ops, Condition, Current, Double, Gray Ops, Illicit, Lockdown, Mandate, Psi, Reprisal, Terminal, Transaction, and Triple.
   6. f.linkThe upgrade subtypes are Academic, Advertisement, Alliance, Ambush, Beanstalk, Bioroid, Character, Clone, Enforcer, Executive, Expendable, Facility, Hostile, Off-site, Orgcrime, Psi, Region, Ritzy, Seedy, Security Protocol, Sysop, and Unorthodox.
   7. g.linkThe event subtypes are Condition, Current, Double, Job, Mod, Orgcrime, Priority, Run, Sabotage, Stealth, and Terminal.
   8. h.linkThe hardware subtypes are Chip, Companion, Console, Consumer-grade, Cybernetic, Gear, Link, Mod, Stealth, Vehicle, and Weapon.
   9. i.linkThe program subtypes are AI, Caïssa, Cloud, Daemon, Decoder, Deep Net, Deva, Fracter, Icebreaker, Killer, Stealth, Trojan, Virus, and Weapon.
   10. j.linkThe resource subtypes are Clan, Clone, Companion, Connection, Directive, Genetics, Government, Job, Link, Location, Remote, Ritzy, Sabotage, Seedy, Source, Stealth, and Virtual.

2.17. Text Boxlink

1. 2.17.1.linkThe text box is the central area on a card containing any abilities the card has. Abilities usually only apply when the card they appear on is active. Section 9.1.8 details exceptions.
2. 2.17.2.linkMany cards have italicised text written after their game text. This is flavor text, and has no effect on the game or the function of the card, nor can other abilities reference or interact with it.
3. 2.17.3.linkSome cards have italicised text in parenthesis. This is reminder text, and has no effect on the game or the function of the card, nor can other abilities reference or interact with it directly. Reminder text simply summarizes a rule that may apply to that card text.

3. Card Typeslink

3.1. Identitieslink

1. 3.1.1.linkEach player starts the game with a single identity active in the play area. See section 1.6.
   1. a.linkSome identities are double-sided. Only the front side of a double-sided identity will have values for its minimum deck size and influence limit. Only the side of a double-sided identity that is currently faceup is active at any given time.
   2. b.linkIdentities are not installed.
2. 3.1.2.linkOnly identity cards have minimum deck sizes and influence limits. These values do not apply during the game; instead, they determine deckbuilding constraints for decks associated with that identity. See section 1.4.
3. 3.1.3.linkOnly Runner identities have a base link. This value is used in calculating the Runner's link value. See section 10.7.
4. 3.1.4.linkThe Corp's identity card is used to mark the location of HQ. See section 4.3.8.

3.2. Agendaslink

Agendas represent valuable pieces of Corporate data. When the Corp advances and scores agendas, it represents completion of critical Corporate projects. When the Runner steals agendas, it represents their acquisition of secret Corporate data.

1. 3.2.1.linkThe Corp may install agendas only in the roots of remote servers. There can be only one agenda or one asset installed in the root of any given remote server at a time. See section 4.6.8.
2. 3.2.2.linkOnly agendas have advancement requirements and agenda points. See section 1.17.
   1. a.linkAn agenda's advancement requirement is the minimum number of advancement counters that must be on that agenda for the Corp to score it.
   2. b.linkThe agenda points on an agenda contribute to a player's score while the agenda is in their score area.
3. 3.2.3.linkAgendas cannot be rezzed and are inactive while installed. Agendas are active in the Corp's score area. Agendas are inactive in the Runner's score area unless the agenda's card text specifies otherwise. See section 4.5.
   1. a.linkSome agendas may be installed faceup or turned faceup through card abilities. Faceup agendas are neither rezzed nor unrezzed. If an agenda's printed text directs the Corp to install it faceup, that agenda's abilities are active while it is installed.
   2. b.linkSome agendas modify the requirements for stealing or scoring them. These abilities are always active, according to any restrictions or requirements specified. See section 9.1.8.
4. 3.2.4.linkAgendas can always be advanced. See section 1.18.

3.3. Assetslink

Assets represent various resources and connections at the Corp's disposal.

1. 3.3.1.linkThe Corp may install assets only in the roots of remote servers. There can be only one agenda or one asset installed in the root of any given remote server at a time. See section 4.6.8.
2. 3.3.2.linkAssets are among the card types that have rez costs. They are installed unrezzed and remain inactive until the Corp rezzes them by paying their rez costs during a paid ability window. See section 8.1.
3. 3.3.3.linkAssets are among the card types that have trash costs. If the Runner accesses an asset, they may pay the trash cost to trash that asset. See section 7.1.5.
4. 3.3.4.linkOne asset, Lady Liberty, has the subtype region and the text "Limit 1 region per server." See section 3.6.5 for rules governing region cards.

3.4. Icelink

Ice are sophisticated security systems that protect Corporate servers through a variety of means. "Ice" has been suggested to stand for a variety of expressions, but is most commonly expanded as "Intrusion Countermeasures Electronics".

1. 3.4.1.link"Ice" and "piece of ice" are synonymous.
2. 3.4.2.linkIce are the only type of card installed protecting servers. Ice are not installed in the roots of servers. See section 4.6.9.
   1. a.linkIce protecting a server are laid out horizontally in front of that server, with the outermost piece of ice furthest from the server.
   2. b.linkWhen the Corp installs a piece of ice, they must install it in the outermost position protecting a server. See section 8.5.
3. 3.4.3.linkIce are among the card types that have rez costs. They are installed unrezzed and remain inactive until the Corp rezzes them by paying their rez costs. See section 8.1.
   1. a.linkUnlike assets and upgrades, ice can normally only be rezzed while being approached during a run. See section 6.4.
4. 3.4.4.linkIce are among the card types that have strength. An ice's strength determines which icebreakers are allowed to interface with it. See section 3.9.5.
   1. a.linkIf an ability modifies the strength of a piece of ice for the remainder of a run, and that ability resolves during an encounter outside of a run, the modification instead lasts for the remainder of that encounter.
      1. Example: The Runner accesses and encounters an Archangel in HQ with Gang Sign. If the Runner uses Devil Charm to lower the strength of the Archangel. That strength reduction would normally last for the remainder of the current run, but since no run is in progress, it instead lasts for the remainder of the encounter.
5. 3.4.5.linkSome ice have trash costs. If the Runner accesses an ice with a trash cost, they may pay the trash cost to trash that ice. See section 7.1.5.
   1. a.linkUnlike assets, upgrades, and agendas, ice are not normally accessed while installed. Encountering a piece of ice does not entail accessing that ice and does not give the Runner an opportunity to pay its trash cost.
6. 3.4.6.linkIce are the only Corp cards with install costs. The install cost of a piece of ice is not a printed value but instead a calculated value based on the number of other ice already protecting the relevant server. See section 1.16.6.
7. 3.4.7.linkIce are the only cards with subroutines. See section 9.8.

3.5. Operationslink

1. 3.5.1.linkOperations are the only Corp cards that are played. Operations are never installed. Playing an operation causes its abilities to become active, and once those abilities are fully resolved the operation is trashed. See section 8.6.
   1. a.linkSome operations have the subtype condition. As part of their abilities, condition operations convert themselves into condition counters and install themselves. A condition operation cannot be installed by an install effect; it can only be installed through its own conversion ability. See rule 10.1.4.
   2. b.linkSome operations have the subtype current. As part of their abilities, current operations prevent themselves from being trashed until another current operation or event is played or the Runner steals an agenda. When one of these occurs, the active current is trashed during the next checkpoint. See section 10.3.
   3. c.linkSome operations have the subtype lockdown. As part of their abilities, lockdown operations prevent themselves from being trashed until the start of the Corp's next turn after the operation is played. Once the Corp's turn begins, this effect expires and the operation is trashed during the next checkpoint, before any conditional abilities marked pending at that time can be triggered. See section 10.3.
2. 3.5.2.linkOperations are the only Corp cards with play costs. An operation's play cost is the number of credits the Corp must spend to play the operation. See section 8.6.
3. 3.5.3.linkSome operations have trash costs. If the Runner accesses an operation with a trash cost, they may pay the trash cost to trash that operation. See section 7.1.5.

3.6. Upgradeslink

1. 3.6.1.linkThe Corp may install upgrades in the root of any server. Upgrades are the only card type that can be installed in the root of a central server.
2. 3.6.2.linkThere is no limit to the number of upgrades that can be installed in the root of a single server.
3. 3.6.3.linkUpgrades are among the card types that have rez costs. They are installed unrezzed and remain inactive until the Corp rezzes them by paying their rez costs during a paid ability window. See section 8.1.
4. 3.6.4.linkUpgrades are among the card types that have trash costs. If the Runner accesses an upgrade, they may pay the trash cost to trash that upgrade. See section 7.1.5.
5. 3.6.5.linkRegions
   1. a.linkSome upgrades have the subtype region. All regions have the text "Limit 1 region per server."
   2. b.linkThe region limitation applies only to cards with the subtype region that are installed or in the process of being installed in the root of a server. It does not apply to cards in central servers, and it does not apply to ice.
   3. c.linkThe region limitation applies to all cards as specified in rule 3.6.5b, regardless of the active or inactive state of those cards.
   4. d.linkWhen the Corp installs a card with the subtype region into the root of a server that already has a region, they must trash the already-installed region. See section 8.5.
   5. e.linkThe Corp cannot swap a region card with a non-region card in another location if there is another region card already installed in the destination location.

3.7. Eventslink

1. 3.7.1.linkEvents are the only Runner cards that are played. Events are never installed. Playing an event causes its abilities to become active, and once those abilities are fully resolved the event is trashed. See section 8.6.
   1. a.linkOne event, On the Lam, has the subtype condition. As part of its abilities, it converts itself into a condition counter and installs itself. This event cannot be installed by an install effect; it can only be installed through its own conversion ability. See rule 10.1.4.
   2. b.linkSome events have the subtype current. As part of their abilities, current events prevent themselves from being trashed until another current operation or event is played or the Corp scores an agenda. When one of these occurs, the active current is trashed during the next checkpoint. See section 10.3.
2. 3.7.2.linkEvents are the only Runner cards with play costs. An event's play cost is the number of credits the Runner must spend to play the event. See section 8.6.

3.8. Hardwarelink

The Runner's hardware are the physical tools at their disposal: the computers, chips, and other machinery that make up their rig.

1. 3.8.1.link"Hardware" and "piece of hardware" are synonymous.
2. 3.8.2.linkThe Runner installs hardware into the play area.
3. 3.8.3.linkHardware are among the types of cards with install costs. The Runner installs a hardware faceup and active by paying its install cost. See section 8.5.
4. 3.8.4.linkThere is no limit to the number of hardware the Runner can have installed.
5. 3.8.5.linkConsoles
   1. a.linkSome hardware have the subtype console. All console have the text "Limit 1 console per player."
   2. b.linkIf a player ever controls more than one installed console, all but the most recently active console are trashed. Trashing cards this way cannot be prevented.
   3. c.linkThis limitation applies only to hardware with the subtype console.
   4. d.linkThis limitation applies only to active console. A player can have multiple copies of a console, and even different consoles, in their deck.

3.9. Programslink

Programs are digital tools at the Runner's disposal, primarily used as a means of intrusion.

1. 3.9.1.linkThe Runner installs programs into the play area.
2. 3.9.2.linkPrograms are among the types of cards with install costs. The Runner installs a program faceup and active by paying its install cost. See section 8.5.
3. 3.9.3.linkPrograms are the only card type that have a memory cost. A program's memory cost is the number of memory units that program requires while it is installed.
   1. a.linkInstalling a program does not permanently consume memory. The program claims its designated quantity of memory units until it becomes uninstalled, at which point those memory units become available for use by other programs.
   2. b.linkWhen the Runner installs a program that would increase the total memory cost of installed programs over their memory limit, they must trash one or more installed programs such that the total memory cost of installed programs including the new program will not exceed their memory limit. See section 8.5.
   3. c.linkIf the Runner's memory limit decreases below the total memory cost of installed programs, or if the total memory cost of installed programs increases above the memory limit for any reason other than installing another program, the Runner must trash one or more installed programs such that the total memory cost of the remaining programs does not exceed their memory limit. This occurs during the next checkpoint after the memory limit is exceeded. See section 10.3.
   4. d.linkA program's memory cost is not a cost. It cannot be increased, lowered, ignored, or otherwise modified by abilities that affect costs to install programs.
4. 3.9.4.linkPrograms are among the card types that have strength.
   1. a.linkPrograms with the subtype icebreaker have a printed numerical strength value. An icebreaker's strength determines which ice it is allowed to interface with. See section 3.9.5.
   2. b.linkPrograms without the subtype icebreaker do not have a strength value. A dash (–) is printed on non-icebreaker program cards in the place where strength is printed on icebreaker program cards.
5. 3.9.5.linkIcebreakers
   1. a.linkSome programs have the subtype icebreaker. Icebreaker programs have strength and abilities that interface with ice.
   2. b.linkPaid abilities on an icebreaker that modify that icebreaker's strength implicitly have a duration of "for the remainder of the current encounter".
      1. Example: Corroder has the ability "1[c]: +1 strength."" Since no duration is specified, this strength increase applies until the end of the current encounter.
   3. c.linkIf an icebreaker's paid ability specifies another duration for modifying its strength, that modification lasts until both the stated duration and the implicit encounter duration have expired.
      1. Example: Gordian Blade has the ability "1[c]: +1 strength for the remainder of this run." This ability applies until the end of the current run, whether it is triggered during an encounter or another step of the run. If the ability is triggered during an encounter that takes place outside of a run, the strength increase applies for the duration of that encounter.
   4. d.linkIf an icebreaker's paid ability modifies its strength outside of an encounter and does not specify another applicable duration, the modification expires during the next checkpoint.
      1. Example: If the Runner uses Corroder's ability to increase its strength outside of an encounter, it applies only until the next checkpoint.
   5. e.linkAll icebreakers have abilities that interface with ice, sometimes referred to as "interface abilities". These abilities are indicated by the "interface" flag preceding the ability's text.
   6. f.linkThe Runner can only use an interface ability during step 6.9.3b of an encounter, and can only choose the encountered piece of ice and its subroutines as targets for the ability's effects. See section 1.15 for more information about targeting.
   7. g.linkThe Runner can only use an interface ability on an icebreaker if the icebreaker has strength greater than or equal to the strength of the encountered ice.
   8. h.linkIf an interface ability specifies that it affects a particular subtype of ice, then that ability can only be used on a piece of ice that has the specified subtype. If an ability on an icebreaker does not specify a subtype of ice that it affects, that ability can be used on any piece of ice.

3.10. Resourceslink

Resources are a wide variety of connections and skills that aid the Runner.

1. 3.10.1.linkThe Runner installs resources into the play area.
2. 3.10.2.linkResources are among the types of cards with install costs. The Runner installs a resource faceup and active by paying its install cost. See section 8.5.
3. 3.10.3.linkThere is no limit to the number of resources the Runner can have installed.
4. 3.10.4.linkWhile the Runner is tagged, the Corp may spend [click] and 2[c] to trash an installed resource as a basic action. See section 10.5.

4. Game Zoneslink

4.1. Generallink

1. 4.1.1.linkA zone is a place in which cards and counters can exist during the game.
   1. a.linkThere are 8 zone types: deck, hand, discard pile, score area, play area, bank, set aside, and removed from the game.
   2. b.linkEach player has their own deck, hand, discard pile, and score area. All players share the play area, the bank, the set-aside zone, and the removed-from-game zone.
   3. c.linkEach card in the game exists in exactly 1 zone at a time.
2. 4.1.2.linkGame rules and card effects can move cards and counters between zones. See section 8.2 for rules on card movements.
   1. a.linkIf a facedown card or a card in a hidden zone would ever move to another zone as part of an effect that requires that card to have a specific attribute, that card must be revealed before being moved to the new zone. If the card is being installed, this rule only applies as indicated by section 8.5.13.
      1. Example: When resolving Clone Suffrage Movement, the Corp chooses a facedown Fast Break in Archives. The Corp must reveal the Fast Break before adding it to HQ, to demonstrate that it is indeed an operation, meeting Clone Suffrage Movement's requirement.
   2. b.linkWhen a card is moved from one zone to another, the move is instantaneous. The card is never in both zones at once, and it is never not in any zone at all.
3. 4.1.3.linkA card that is not in any zone is outside the game. Cards outside of the game are distinct from cards in the removed-from-game zone, and cannot affect the game. They can only be affected by abilities that explicitly bring in extra cards from outside the game. See section 1.5.
4. 4.1.4.linkA public zone is one where cards are freely visible to both players unless they are facedown. The play area, the bank, the set-aside zone, the removed-from-game zone, and both players' score areas and discard piles are public zones. See section 1.21 for rules on card visibility and section 8.1 for rules on the faceup and facedown status of a card.
5. 4.1.5.linkA hidden zone is one where cards are not visible to either player. Each player's deck is a hidden zone.
6. 4.1.6.linkA secret zone is one where cards are visible only to their controller. Each player's hand is a secret zone.
7. 4.1.7.linkA location is a specific position within a zone that an object can occupy. A destination is a location to which an object is to be moved.
   1. a.linkA card in a player's deck has a location identified by how many cards it is from the top of that deck.
   2. b.linkSome objects in the play area are in specific locations. See section 4.6.5.
   3. c.linkThe location of a hosted object is its host card.
   4. d.linkAll other objects are simply located in their zone and do not have a more specific location.

4.2. Decklink

1. 4.2.1.linkWhen the game begins, each player's deck presented during setup becomes their in-game draw deck.
2. 4.2.2.linkDecks must be kept facedown with their cards hidden from both players. Neither player may look at the cards in any deck without being explicitly directed to do so by a rule or card ability.
3. 4.2.3.linkDecks are ordered. The location of each card in a deck must be maintained except when a player is explicitly directed to manipulate the cards in a deck by a rule or card ability. See rule 4.1.7a.
   1. a.linkWhile searching a deck, a player is not required to maintain the order of the searched cards or indicate the previous location of any card found by the search. Note that the deck is always shuffled upon completion of the search, as required by rule 8.7.3.
4. 4.2.4.linkThe number of cards in a deck is open information. Any player may count the number of cards in a deck at any time.
5. 4.2.5.linkCards in a deck are inactive.
6. 4.2.6.linkEach player's deck has its own name as a means of differentiating between the two.
7. 4.2.7.linkR&D

   R&D stands for Research and Development. It represents upcoming projects and acquisitions the Corp will soon have at their disposal.

   1. a.linkR&D is the name for the Corp's deck. It is also one of the Corp's central servers. See section 4.6.7.
   2. b.linkIf the Corp must ever draw from R&D while it is empty, the Runner wins the game. See section 1.7.
8. 4.2.8.linkStack

   The stack represents the Runner's untapped potential: future plans, connections, and opportunities they have yet to discover.

   1. a.linkThe stack is the name for the Runner's deck.

4.3. Handlink

1. 4.3.1.linkA player's hand is the zone in which they hold the cards they have drawn from their deck. Cards can be added to a player's hand by other rules and card abilities as well. During setup, each player draws a starting hand. See section 1.6.
2. 4.3.2.linkA player's hand is kept secret from their opponent. A player may look at the cards in their own hand, but not at any of the cards in their opponent's hands.
3. 4.3.3.linkHands are not ordered. A player may freely arrange the cards in their hand in any order at any time.
4. 4.3.4.linkThe number of cards in a hand is open information to all players. Any player may count the number of cards in a hand at any time.
5. 4.3.5.linkCards in a hand are inactive.
6. 4.3.6.linkEach player has a maximum hand size, usually five. A player may have any number of cards in their hand at any given time, but during the discard phase of a player's turn they must discard cards from their hand until there are no more cards in their hand than their maximum hand size allows. See section 5.5.
7. 4.3.7.linkEach player's hand has its own name as a means of differentiating between the two.
8. 4.3.8.linkHQ

   HQ stands for Headquarters. It represents the projects, staff, technology, and other assets the Corp is authorized to deploy.

   1. a.linkHQ is the name for the Corp's hand. It is also one of the Corp's central servers. See section 4.6.7.
   2. b.linkThe Corp's identity card represents their HQ server for the purposes of gameplay. Ice protecting HQ is installed in front of the Corp's identity card and upgrades installed in the root of HQ are installed behind the Corp's identity card.
9. 4.3.9.linkGrip

   The grip represents the Runner's currently accessible thoughts, plans, knowledge, potential social connections, and other intangible information that can be leveraged.

   1. a.linkThe grip is the name for the Runner's hand.
   2. b.linkSuffering damage forces the Runner to discard cards from their grip at random, and suffering core damage also reduces the Runner's maximum hand size. The Runner flatlines and loses the game if they suffer more damage than they have cards in grip or must discard down to a hand size lower than zero. See section 10.4.

4.4. Discard Pilelink

1. 4.4.1.linkA player's discard pile is the zone in which they place cards that have been trashed or discarded. Discard piles start the game empty.
2. 4.4.2.linkDiscard piles are not ordered. A player may freely arrange the cards in their discard pile in any order at any time.
3. 4.4.3.linkThe number of cards in a discard pile is open information. Any player may count the number of cards in a discard pile at any time.
4. 4.4.4.linkCards in a discard pile are inactive.
5. 4.4.5.linkEach player's discard pile has its own name as a means of differentiating between the two.
6. 4.4.6.linkArchives

   Archives represents the Corp's internal record database of all scrapped, abandoned, or discontinued projects, contracts, assignments, and other endeavors.

   1. a.linkArchives is the name for the Corp's discard pile. It is also one of the Corp's central servers. See section 4.6.7.
   2. b.linkCards in Archives can be either faceup or facedown. If a Corp card is visible to the Runner when it is trashed or discarded, it is put in Archives faceup. If a Corp card is not visible to the Runner when it is trashed or discarded, then it is put in Archives facedown. Facedown cards in Archives should be oriented horizontally so that the Runner can easily see they are present.
   3. c.linkThe faceup cards in Archives are open information. Any player may look through the faceup cards in Archives at any time. The facedown cards in Archives are visible only to the Corp. The Corp may look through the facedown cards in Archives at any time, but the Runner cannot look at them.
7. 4.4.7.linkHeap

   The heap represents what the Runner has lost: their old jobs, favours burned, friends long gone, gear wrecked, and code erased.

   1. a.linkThe heap is the name for the Runner's discard pile.
   2. b.linkThe cards in the heap are open information. Any player may look through the cards in the heap at any time.

4.5. Score Arealink

The score areas represent major accomplishments for each player in service of their long-term ambitions. The Corp's score area contains all large-scale projects they have seen to completion. The Runner's score area is a memorial to all such initiatives they have successfully disrupted, exposed, or sold details of to the highest bidder.

1. 4.5.1.linkA player's score area is the zone in which they place agendas they have scored or stolen. Section 1.17 details scoring and stealing agendas. Score areas start the game empty.
2. 4.5.2.linkThe agendas in a score area are open information. A player may look through or count the agendas in a score area at any time.
3. 4.5.3.linkScore areas are not ordered. A player may freely arrange the agendas in their score area in any order at any time.
4. 4.5.4.linkAgendas in the Corp's score area are active. Agendas in the Runner's score area are inactive unless stated otherwise.

4.6. Play Arealink

1. 4.6.1.linkThe play area is the shared active zone into which cards are played or installed. The play area normally starts the game empty except for each of the player's identities.
   1. a.linksection 1.5 details cases where an ability may cause cards to start the game in the play area.
2. 4.6.2.linkThe number of cards in the play area and the location of each card in the play area is always open information.
3. 4.6.3.linkWhether or not a card itself and its attributes are open information while in the play area is determined by the card's status. Cards that are faceup are open information and can be examined by any player at any time. Cards that are facedown are secret information and can only be examined by the player who controls the card. See section 10.2.
4. 4.6.4.linkWhether or not a card is active while in the play area is determined by the card's status.
   1. a.linkIdentities start the game in the play area and are always active.
   2. b.linkGenerally, Corp agendas, assets, ice, and upgrades are installed into the play area unrezzed and thus inactive. They are active while rezzed. See section 8.5.
   3. c.linkGenerally, Runner hardware, programs, and resources are installed into the play area faceup and active. See section 8.5.
   4. d.linkSome Runner cards are installed facedown or turned facedown through card abilities. This is distinct from the status of rezzed/unrezzed that Corp cards can have. Facedown Runner cards are not active. See section 8.1.4.
   5. e.linkOperations and events are played into the play area faceup and are active for the duration of their resolution before being trashed. See section 8.6.
5. 4.6.5.linkSome objects in the play area are organized into specific orientations and/or locations.
   1. a.linkCorp cards are arranged into distinct servers. Agendas and assets are installed in the roots of remote servers, upgrades are installed in the roots of any servers, and pieces of ice are installed horizontally protecting servers. See section 4.6.6 and section 4.6.9.
   2. b.linkThe Corp's identity is used to indicate where in the play area HQ exists for the purposes of installing upgrades in the root of HQ and ice protecting HQ. See section 4.6.7.
   3. c.linkThe Runner's identity, hardware, programs, and resources do not have specific locations in the play area.
   4. d.linkThere is no specific location in the play area for operations or events. They are simply played into the play area, where they resolve before being trashed. See section 8.6.
   5. e.linkEach player has a credit pool, which is a location in the play area where credits they control are kept.
   6. f.linkCounters other than credits have no specific location in the play area. Tag counters are always controlled by the Runner, and bad publicity counters are always controlled by the Corp. Other types of counters are either nonfunctional gameplay aids or appear only in host relationships. See also section 1.9.
   7. g.linkSome cards can act as install locations for other cards while in the play area, such that cards of a specific type can be hosted directly onto them during the installation process. In this type of host relationship, both the host card and the hosted card are in the play area, but the host relationship can affect certain aspects of either the card or the installation process. See section 1.13.
   8. h.linkSome cards can host other cards without installing them. In this type of host relationship, both the host card and the hosted card are in the play area, but the hosted card is not installed and thus not active. See section 1.13.
6. 4.6.6.linkServers
   1. a.linkA server is a set of locations where the Corp installs their cards into the play area and against which the Runner can initiate runs. Whenever a Corp installs an agenda, asset, ice, or upgrade, they must choose a destination server for that card. See section 8.5.
   2. b.linkOnce a Corp card is installed, it cannot be moved from its server without explicit direction from a game rule or card effect.
   3. c.linkThe two types of servers are central servers and remote servers. See sections 4.6.7 and 4.6.8, respectively.
   4. d.linkAll servers can have ice installed protecting them. See section 4.6.9.
   5. e.linkAll servers have a root where cards can be installed. A central server's root can contain any number of upgrades, while a remote server's root can contain 1 asset or agenda and any number of upgrades. Assets and agendas cannot be installed in the root of a central server.
   6. f.linkAll cards installed in the root of a server are kept in the same orientation and location together. The order in which the cards are installed is open information, but the type of cards installed in the root of a remote server should not be derivable from their orientation or location.
   7. g.linkOnly 1 region upgrade can be installed in the root of a server at a time. See section 3.6.5.
   8. h.linkSome upgrades have restrictions limiting them to specific servers. See rule 8.5.12.
   9. i.linkSome cards refer to the server where they are located (or the central server corresponding to the zone where they are located) using the phrase "this server". If an ability is initiated by a trigger condition or cost involving the ability's source card moving from a server, its root, or protecting it to another server or to a location not associated with any server, treat "this server" as referring to the server associated with the previous location of the card throughout resolution of that ability. If an ability moves its source card while it is resolving, continue to interpret "this server" based on the card's previous location.
      1. Example: The Runner trashes a rezzed Warroid Tracker. This meets the trigger condition of Warroid Tracker's ability, but by the time a checkpoint is resolved and an instance of the ability would become pending, Warroid Tracker itself is no longer installed. The use of "this server" in the trigger condition still refers to the server from which Warroid Tracker was trashed, not to the server of Warroid Tracker's new location in Archives.
      2. Example: The Corp uses the ability granted by ZATO City Grid to trash Border Control and resolve its first subroutine. The phrase "this server" in that subroutine refers to the server from which the Border Control was trashed. However, Border Control is no longer protecting that server, so it is not included in the number of ice counted.
      3. Example: The Corp uses Nanisivik Grid to turn a facedown Border Control in Archives faceup and resolve its first subroutine. Border Control was not moved between servers, so "this server" in that subroutine refers to Archives.
   10. j.linkIf an ability on a card currently or previously located in a server, its root, or protecting it refers to "another server", this means any server except "this server" as interpreted by rule 4.6.6i. If a card's abilities involve choosing a server, "another server" in a linked ability means any server except the chosen server. If neither of the previous cases apply and a run is in progress, "another server" means any server except the attacked server.
   11. k.linkIf an ability on an object uses the phrase "this server", and that object is hosted on another object (see section 1.13), the server referred to is the server of the host object.
7. 4.6.7.linkCentral Servers
   1. a.linkThe Corp has three central servers at all times. Each central server corresponds to one of the Corp's zones: HQ corresponds to the Corp's hand, R&D corresponds to the Corp's deck, and Archives corresponds to the Corp's discard pile.
   2. b.linkThe Corp's identity is in the play area to indicate the location of HQ relative to other servers, but it is not in HQ, in the root of HQ, or protecting HQ. The cards in HQ are held in the Corp's hand. The upgrades installed in the root of HQ are placed in a vertical orientation near the Corp's identity. The ice installed protecting HQ are placed in a horizontal orientation in front of the Corp's identity outwards towards the Runner.
   3. c.linkThe Corp's deck is placed in the play area to indicate the location of R&D relative to other servers, but the cards in the deck are not installed. The cards in R&D are the cards in the deck. The upgrades installed in the root of R&D are placed in a vertical orientation near the deck. The ice installed protecting R&D are placed in a horizontal orientation in front of the deck outwards towards the Runner.
   4. d.linkThe Corp's discard pile is placed in the play area to indicate the location of Archives relative to other servers, but the cards in the discard pile are not installed. The cards in Archives are the cards in the discard pile. The upgrades installed in the root of Archives are placed in a vertical orientation near the discard pile. The ice installed protecting Archives are placed in a horizontal orientation in front of the discard pile outwards towards the Runner.
8. 4.6.8.linkRemote Servers
   1. a.linkA remote server is the only type of server that can contain an asset or agenda in its root.
   2. b.linkThe Corp starts the game with no remote servers. The Corp creates a new remote server by declaring it as the destination server for a card they are about to install. There is usually no limit to the number of remote servers the Corp can have at any given time.
   3. c.linkCards installed in the roots of separate remote servers are placed in a vertical orientation in a row extending away from the central servers to indicate the locations of the remote servers relative to other servers. The ice installed protecting each remote server are placed in a horizontal orientation in front of any cards in the root of that server, outwards towards the Runner.
   4. d.linkA remote server exists as long as there is at least one card in the root of or protecting it. A remote server can be made up of only ice protecting it, only cards installed in it, or a combination of both.
   5. e.linkDuring checkpoints, a remote server ceases to exist if there are no cards installed in its root and no cards installed protecting it. If a server ceases to exist during a run against it, then the run ends after any currently open paid ability window closes. Unless the run has already been declared either successful or unsuccessful, it is neither. See rule 8.5.8.
   6. f.linkSome abilities limit the number of remote servers. While such an ability is active, the Corp cannot create a new remote server if this would raise the total number of remote servers above the specified limit. During step 10.3.1e of each checkpoint, if there are more remote servers than an active limit allows, the Corp player chooses a number of servers equal to the limit. The checkpoint then trashes all cards in the root of and protecting each remote server that was not chosen.
      1. Example: The Corp's identity is Earth Station: SEA Headquarters, which has the ability "Limit 1 remote server." If any remote servers exist, the Corp cannot create a new remote server.
9. 4.6.9.linkProtecting a Server
   1. a.linkAn installed piece of ice is arranged in a horizontal position in front of the server it is protecting. Ice are ordered within the play area. The location of a piece of ice is defined by the server it is protecting and the number of other pieces of ice between it and the server.
   2. b.linkIf there is no other ice between the server and a piece of ice, that ice is the innermost piece of ice. If there is no ice farther from the server than a piece of ice, that ice is the outermost piece of ice. If there is only one piece of ice protecting a server, that ice is both the innermost and the outermost piece of ice.
   3. c.linkIf two pieces of ice protecting two different servers share the same number of ice between them and their respective servers, those pieces of ice are considered to be in the same position.
   4. d.linkWhen the Corp installs a piece of ice protecting a server, they must place it in the outermost position protecting that server. See section 8.5.
   5. e.linkIf the number of other ice between a piece of ice and the server changes, its position will change accordingly, moving either closer or farther from the server. If this occurs while that ice is being approached, encountered, or passed during a run, the Runner's position attacking the server changes in the same way.

4.7. Banklink

1. 4.7.1.linkThe bank is an inactive zone shared by both players. It holds an unlimited supply of counters for use during gameplay.
2. 4.7.2.linkCounters placed or loaded onto a card are taken from the bank unless otherwise specified. Counters gained by players are taken from the bank unless otherwise specified.
3. 4.7.3.linkCredits and other counters that are spent to pay costs return to the bank.
4. 4.7.4.linkCounters that are not in a legal location return to the bank during checkpoints. See section 10.3.
5. 4.7.5.linkCards are never located in the bank.

4.8. Set Asidelink

1. 4.8.1.linkThe set-aside zone is an inactive zone shared by both players. It is used as a temporary holding space for objects being affected by abilities.
2. 4.8.2.linkIf an object is "set aside", it is moved from its current zone to the set-aside zone.
3. 4.8.3.linkAn ability cannot see the set-aside zone unless it specifically sets objects aside or refers to set-aside objects. Outside of these cases, cards moved into another zone from the set-aside zone are treated as though they entered that zone directly from their location prior to being set aside.
   1. Example: The Runner is playing as Exile and plays Test Run, searching their heap for a program. Although the program is set aside before being installed, Exile's ability treats it as though it were installed directly from the heap, and so Exile will draw a card.
4. 4.8.4.linkCards found during a search are set aside facedown while the search completes (in particular, while any deck that was searched is shuffled). See section 8.7.
5. 4.8.5.linkSome paid abilities with a trigger cost that uninstalls or forfeits the ability's source card need to refer to or act on that card's hosted cards or counters. These abilities set aside the hosted cards or counters as the trigger cost is paid. See rule 9.5.5.
6. 4.8.6.linkCards set aside by a card ability are faceup unless the ability specifically instructs that they be set aside facedown.
7. 4.8.7.linkFacedown cards in the set-aside zone must be kept in distinct groups according to the effect that sets them aside. Cards within such a group are not ordered and can be freely arranged by their controller.
   1. Example: The Runner accesses the top card of R&D and does not steal or trash it. On the next turn, the Corp uses Daily Business Show to draw that card and 1 other card simultaneously, but must put 1 of the drawn cards on the bottom of R&D. While resolving the draw, the cards are set aside facedown, so the Corp can shuffle them. They do not have to tell the Runner whether the previously-accessed card ends up in HQ or on the bottom of R&D.

4.9. Remove from the Gamelink

1. 4.9.1.linkThe removed-from-game zone is an inactive zone shared by both players. It is used to take cards out of any player's control until the end of the game.
2. 4.9.2.linkIf a card is removed from the game, it is moved from its current zone to the removed-from-game zone.
3. 4.9.3.linkForfeiting an agenda removes it from the game. See rule 8.2.5.
4. 4.9.4.linkCards that have been removed from the game are inactive.
5. 4.9.5.linkA card that has been removed from the game cannot move out of the removed-from-game zone or otherwise be interacted with.
6. 4.9.6.linkCards that have been removed from the game are open information. Any player may look through or count the cards that have been removed from the game at any time.

5. Turnslink

5.1. Generallink

1. 5.1.1.linkA turn is a duration of time during which a player may take actions and is the first to receive priority to act during priority windows.
2. 5.1.2.linkThe Corp's turn consists of three phases. During the draw phase, the Corp draws the top card of R&D into HQ; during the action phase, the Corp spends [click]s to perform actions; during the discard phase, the Corp discards until the number of cards in HQ does not exceed their maximum hand size. Once the Corp's turn ends, the Runner's turn begins.
3. 5.1.3.linkThe Runner's turn consists of two phases. During the action phase, the Runner spends [click]s to perform actions; during the discard phase, the Runner discards until the number of cards in their grip does not exceed their maximum hand size. Once the Runner's turn ends, the Corp's turn begins.
4. 5.1.4.linkThe beginning and end of each player's turn are formalized as particular steps of the turn timing structures.
   1. a.linkTrigger conditions related to a turn beginning are not met as the turn timing structure opens. They are met at the timing step that indicates the formal beginning of the turn.
   2. b.linkTrigger conditions related to a turn or discard phase ending are met at the timing step that indicates the formal end of the turn. They are not met when the turn timing structure later closes. The end of the turn and the end of the discard phase are the same.
   3. c.linkSome effects can occur before the "turn begins" step or after the "turn ends" step of a turn. The player whose turn timing structure is in progress is still the active player, and effects that apply during their turn are still applicable, even though their turn has not yet formally begun or has already formally ended.
   4. d.linkOnce the game begins, it is always one or the other player's turn. There is no time "between turns".

5.2. Actionslink

1. 5.2.1.linkAn action is any paid ability where the cost begins with a [click] symbol.
   1. a.linkOther costs can contain [click] symbols without denoting an action.
      1. Example: The ability "[click]: Gain 1[c] and draw 1 card." on Professional Contacts is an action. The ability "Lose [click]: Break 1 subroutine on this ice. Only the Runner can use this ability." on Eli 1.0 is not an action and is used during a paid ability window.
2. 5.2.2.linkA player initiates an action by paying its cost in [click], as well as any other costs associated with that action, during their action window.
   1. a.linkOnce an action is initiated, it must be completed before the game can advance to the next step or open another action window. If the effects of an action initiate a timing structure, such as a run, players may use paid abilities, rez cards, and score agendas as dictated by the priority windows of that nested timing structure, but otherwise players cannot perform any of those voluntary effects while the action is resolving. See section 9.2 for more details about priority.
   2. b.linkIf a timing structure is initiated during the resolution of an action, that action is not complete until the new timing structure is complete and any further effects of the initiated action following the completion of the new timing structure are resolved.
      1. Example: The Runner takes the action "play an event", playing Stimhack. The action is not complete until the run initiated by Stimhack ends, the Runner suffers core damage, and Stimhack is trashed following its resolution.
   3. c.linkA conditional ability that meets its trigger condition due to a player taking an action resolves after the action's trigger cost is paid, before the effects of the action itself. See rule 9.1.2a.
   4. d.linkSome conditional abilities meet their trigger conditions due to an action "ending", "finishing", or "completing". These abilities resolve in the reaction window following step 5.6.2b or step 5.7.1f, for actions taken by the Corp and Runner, respectively.
3. 5.2.3.linkEach player has several basic actions they can always perform. The Corp's basic actions are listed in section 5.2.7, and the Runner's basic actions are listed in section 5.2.8.
   1. a.linkIf an ability has a trigger condition related to an effect being performed “with the basic action”, that trigger condition is met by any basic action that performs the indicated effect. If an ability imposes a cost on performing an effect “with the basic action”, that cost applies to any instance of the indicated effect that would occur as part of resolving a basic action.
4. 5.2.4.linkA player can only take an action if its effect has the potential to change the game state. See rule 1.2.5.
5. 5.2.5.linkA player can only take actions during the action phase of their turn. If an effect directs a player to take an action outside of that player's action phase, instead that player does nothing.
6. 5.2.6.linkSome cards refer to players taking "the same action" or "different actions".
   1. a.linkActions a player performs are the same if they are all the same basic action or if all of those actions were initiated by the same ability from the same card.
   2. b.linkActions a player performs are different if each of them is initiated from a different basic action or card ability. Instances of equivalent abilities on different cards are still different actions.
      1. Example: The Corp, playing MirrorMorph: Endless Iteration, plays Hedge Fund as the first action of their turn, then plays Lateral Growth. Even though two different cards were played, both times the Corp used the basic action to "Play 1 operation from HQ". Since their first two actions were the same, the Corp will not be able to trigger the ability on MirrorMorph this turn.
7. 5.2.7.linkCorp Actions
   1. a.linkThe following basic actions are always available to the Corp during their action phase, in addition to any actions provided by card abilities.
   2. b.link"[click]: Gain 1[c]."
   3. c.link"[click]: Draw 1 card."
   4. d.link"[click]: Install 1 agenda, asset, upgrade, or piece of ice from HQ." See section 8.5.
   5. e.link"[click]: Play 1 operation from HQ." See section 8.6.
   6. f.link"[click], 1[c]: Advance 1 installed card." See section 1.18.
   7. g.link"[click], 2[c]: Trash 1 resource. Take this action only if the Runner is tagged." See section 10.5.
   8. h.link"[click][click][click]: Purge virus counters." See section 10.1.2.
8. 5.2.8.linkRunner Actions
   1. a.linkThe following basic actions are always available to the Runner during their action phase, in addition to any actions provided by card abilities.
   2. b.link"[click]: Gain 1[c]."
   3. c.link"[click]: Draw 1 card."
   4. d.link"[click]: Install 1 program, resource, or piece of hardware from the grip." See section 8.5.
   5. e.link"[click]: Play 1 event from the grip." See section 8.6.
   6. f.link"[click]: Run any server." See section 6.
   7. g.link"[click], 2[c]: Remove 1 tag." See section 10.5.

5.3. Draw Phaselink

1. 5.3.1.linkThe draw phase is the first phase of the Corp's turn. It includes the formal beginning of the Corp's turn and the Corp's mandatory draw.
2. 5.3.2.linkThe mandatory draw is a card draw performed by the Corp. It is not an action and does not cost [click].
3. 5.3.3.linkThe Runner's turn does not have a draw phase.

5.4. Action Phaselink

1. 5.4.1.linkThe action phase is the first phase of the Runner's turn and the second phase of the Corp's turn. It is the only timing structure in which players can take actions, as discussed in section 5.2.
2. 5.4.2.linkDuring a player's action phase, they must continue to take actions until they have no more clicks or the phase is ended directly by a card ability. The player may take actions in any combination and order as long as they pay the appropriate costs. Once they have no remaining clicks, the action phase ends.
3. 5.4.3.linkA player's action phase can be forced to end by certain card abilities (e.g. via the ability on a terminal operation or event). When a player's action phase is forced to end, the following occurs:
   1. a.linkThe current step of the action phase ends, and all remaining steps are skipped.
   2. b.linkAny currently open priority windows close, their associated abilities lose their pending status, and the player with priority loses priority.
   3. c.linkAny currently resolving actions or abilities cease resolving and are considered complete.
   4. d.linkA checkpoint occurs, following which the game proceeds to the active player's discard phase.

5.5. Discard Phaselink

1. 5.5.1.linkThe discard phase is the last phase of each player's turn. It requires the active player to discard cards until their maximum hand size is satisfied and includes the formal end of that player's turn.
2. 5.5.2.link discarding is the act by which a player moves a card to their discard pile during their discard phase if they have exceeded their maximum hand size.
   1. a.linkCards discarded from HQ are always sent to Archives facedown, regardless of whether they have been previously accessed by the Runner.
   2. b.linkA discarded card is not considered to have been trashed, and vice versa.
3. 5.5.3.linkA player's maximum hand size is the maximum number of cards that player can keep in their hand during their discard phase.
   1. a.linkPlayers begin the game with a maximum hand size of five cards.
   2. b.linkEach point of core damage the Runner suffers permanently reduces their maximum hand size by 1 card. See section 10.4. Other abilities can modify a player's maximum hand size directly.
4. 5.5.4.linkIf an effect instructs a player to "skip your discard step", that player does not resolve the appropriate step of their turn (step 5.6.3a for the Corp, and step 5.7.2a for the Runner). They will not check their hand size or discard cards.

5.6. Steps of the Corp's Turnlink

1. 5.6.1.linkDuring the draw phase, the following steps occur in order:
   1. a.linkThe Corp gains their allotted clicks (default [click][click][click]).
   2. b.linkA paid ability window occurs, in which players may use paid abilities, the Corp may rez non-ice cards, and the Corp may score agendas. (P) (R) (S)
   3. c.linkThe Corp's recurring credits ([recurring]) refill.
   4. d.linkThe Corp's turn formally begins. Conditions related to the turn beginning are met.
   5. e.linkThe Corp performs their mandatory draw.
   6. f.linkThe Corp's draw phase is complete. Play proceeds to the Corp's action phase.
2. 5.6.2.linkDuring the Corp's action phase, the following steps occur in order:
   1. a.linkA paid ability window occurs, in which players may use paid abilities, the Corp may rez non-ice cards, and the Corp may score agendas. (P) (R) (S)
   2. b.linkIf the Corp has any unspent [click], the Corp takes an action. Otherwise, skip to (d).
   3. c.linkReturn to (a).
   4. d.linkThe Corp's action phase is complete. Play proceeds to the Corp's discard phase.
3. 5.6.3.linkDuring the Corp's discard phase, the following steps occur in order:
   1. a.linkThe Corp discards one card at a time from HQ until the number of cards in HQ is less than or equal to the Corp's maximum hand size.
   2. b.linkA paid ability window occurs, in which players may use paid abilities and the Corp may rez non-ice cards. (P) (R)
   3. c.linkIf the Corp has any unspent [click], the Corp loses those [click].
   4. d.linkThe Corp's turn formally ends. Conditions related to the turn or discard phase ending are met.
   5. e.linkThe Corp's discard phase and turn are complete. Play proceeds to the Runner's turn.

5.7. Steps of the Runner's Turnlink

1. 5.7.1.linkDuring the Runner's action phase, the following steps occur in order:
   1. a.linkThe Runner gains allotted clicks (default [click][click][click][click]).
   2. b.linkA paid ability window occurs, in which players may use paid abilities and the Corp may rez non-ice cards. (P) (R)
   3. c.linkThe Runner's recurring credits ([recurring]) refill.
   4. d.linkThe Runner's turn formally begins. Conditions related to the turn beginning are met.
   5. e.linkA paid ability window occurs, in which players may use paid abilities and the Corp may rez non-ice cards. (P) (R)
   6. f.linkIf the Runner has any unspent [click], the Runner takes an action. Otherwise, skip to (h).
   7. g.linkReturn to (e).
   8. h.linkThe Runner's action phase is complete. Play proceeds to the Runner's discard phase.
2. 5.7.2.linkDuring the Runner's discard phase, the following steps occur in order:
   1. a.linkThe Runner discards one card at a time from the grip until the number of cards in the grip is less than or equal to the Runner's maximum hand size.
   2. b.linkA paid ability window occurs, in which players may use paid abilities and the Corp may rez non-ice cards. (P) (R)
   3. c.linkIf the Runner has any unspent [click], the Runner loses those [click].
   4. d.linkThe Runner's turn formally ends. Conditions related to the turn or discard phase ending are met.
   5. e.linkThe Runner's discard phase and turn are complete. Play proceeds to the Corp's turn.

6. Runslink

6.1. Generallink

1. 6.1.1.linkA run is a Runner's attack on a server. There are 6 phases used in the procedure of carrying out a run, described in sections 6.3 through 6.8. A run always begins with the Initiation Phase. Section 6.9 contains the full set of steps carried out during each phase, and should be referred to in conjunction with the sections discussing the phases.
2. 6.1.2.linkThe attacked server is the server the Runner is attempting to reach, usually to breach that server.
   1. a.linkThe Runner announces the attacked server in the initiation phase of the run.
   2. b.linkCard abilities can sometimes change the attacked server during the run. This does not end the run, but it can affect whether or not certain card abilities or effects apply.
   3. c.linkIf an ability changes the Runner's position, the attacked server and the current timing step of the run could also change. See section 6.2.5.
   4. d.linkA few abilities change the attacked server directly, without referring to the Runner's position. These abilities do not change the current timing step of the run.
      1. Example: Sneakdoor Beta's ability changes the attacked server from Archives to HQ. The Runner does not need to encounter ice protecting HQ after resolving this ability.
3. 6.1.3.linkMany abilities modify the sequence of steps taken to resolve a run. Such abilities can direct players to skip steps or phases, replace steps with other effects, move directly from the current timing point to a new phase, or make other changes to the procedures explained in this section. Heed the Golden Rules in section 1.2.
   1. a.linkSome abilities direct the Runner to approach or encounter a piece of ice as part of moving them to that ice's position. See section 6.2.5.
   2. b.linkOne card, Code Replicator, directs the Runner to approach the piece of ice in their position without first moving them to a new position. This effect changes the current timing step of the run to step 6.9.2, the Approach Ice Phase.
   3. c.linkAn ability that directs the Runner to encounter a piece of ice without first moving the Runner's position does not change the current timing point of the run, the attacked server, or the Runner's position. The effect of such an ability is to resolve an Encounter Ice Phase independent of the current state of the run. See section 6.5.9.
   4. d.linkAny time the current timing step of the run is moved to a different phase of the run, except for an instruction to end the run (See rule 6.1.4, below), no more steps in the previously-active phase are carried out. If a paid ability window is open, players complete that window normally. Then the active phase is complete and a checkpoint occurs. Finally, the game proceeds to the new phase.
   5. e.linkIf a condition refers to encountering a piece of ice "after" an approach or passing a piece of ice "after" an encounter, then that condition is only met by the indicated phases or steps occurring in direct sequence according to the standard progression of the run.
      1. Example: The Runner uses Inversificator to break the subroutine on a Miraju that is protecting Archives. When the encounter ends, Miraju's ability creates a replacement effect so that the Runner moves to the outermost position of Archives instead of passing Miraju. Because the ice is not passed, Inversificator's ability does not meet its trigger condition. Later, the Runner encounters the same Miraju again and does not break its subroutine. When this encounter ends, the Runner passes Miraju. Even though the Runner has used Inversificator to fully break Miraju during an encounter earlier in the run, Inversificator's trigger condition is not met when the Runner passes Miraju because the Runner is not passing it after the relevant encounter.
4. 6.1.4.linkTo end the run is to halt the Runner's progress toward the server. When an effect ends the run, the current phase of the run ends without following any of its remaining steps, and before completing open priority windows. The game immediately moves from the current timing point to step 6.9.6, the Run Ends Phase.
5. 6.1.5.linkJacking out is the process by which a Runner voluntarily ends a run. Jacking out follows the usual process for ending the run as described in rule 6.1.4, but some card abilities function differently depending on whether or not the Runner chose to end the run by jacking out.
   1. a.linkThe Runner has the opportunity to jack out after passing a piece of ice.
   2. b.linkIf there is no ice protecting the server, the Runner has the opportunity to jack out before approaching the server.

6.2. Positionlink

1. 6.2.1.linkThe Runner's position during a run is a measure of their distance from the server. The Runner's possible positions correspond to the positions of ice protecting the attacked server.
   1. a.linkThe Runner does not have a position while they are not engaged in a run, nor do they maintain their position from one run to the next. After a run initiates, the Runner moves to the outermost position of the attacked server, if it has any.
2. 6.2.2.linkThe Runner progresses through the positions protecting a server (and corresponding ice) in order. They approach, encounter (if the ice is rezzed), and pass each piece of ice, then proceed to the next piece of ice moving inward, until they pass the innermost piece of ice or the run is ended.
   1. a.linkOnce the Runner leaves the position of the innermost piece of ice protecting a server, they no longer have a position. This occurs at step 6.9.4d of the Movement Phase. However, abilities can still move the Runner to a position later in that phase.
   2. b.linkDuring the Success Phase and the Run Ends Phase, the Runner has no position and can no longer move to a position.
      1. Example: The Corp uses Ganked! to force the Runner to encounter Cell Portal in the middle of breaching a server. Since the run is already successful, resolving Cell Portal's subroutine will have no meaningful effect except to derez Cell Portal.
3. 6.2.3.linkIce entering or leaving a position protecting the attacked server can affect the Runner's position.
   1. a.linkIf a piece of ice is added to or removed from the attacked server in a position outward from the Runner's current position, nothing happens. The Runner will normally not need to approach or encounter the new piece of ice to reach the server.
      1. Example: During a run on R&D, Architect's subroutines resolve and the Corp installs a new piece of ice in the outermost position protecting this server. The Runner does not approach that new piece of ice during this run because they have already passed that position.
   2. b.linkIf a piece of ice is added to the attacked server in a position inward from the Runner's current position, the Runner and each piece of ice outside of the new ice's position shift one space outward.
      1. Example: During a run on a remote server, Howler's subroutine resolves, and the Corp installs a new piece of ice in the next inward position protecting the server. The Runner will have to approach that new piece of ice later in this run because they have not passed that position.
   3. c.linkIf a piece of ice inward from the Runner's position is uninstalled or moved to another server, the Runner and each piece of ice outside of the departed ice's position shift one space inward. The Runner does not re-approach ice they have already passed.
4. 6.2.4.linkChanges to the piece of ice in the Runner's current position can affect the progression of the run, but they do so differently during the Approach Ice Phase than during the Encounter Ice Phase.
   1. a.linkIf a piece of ice is uninstalled or moved to another position (protecting this or another server) while it is being approached, the run moves to the Movement Phase, all outward ice moves one position inward, and the run continues. The Runner does not re-approach ice they have already passed.
      1. Example: The Runner has passed 1 piece of ice and is approaching the innermost piece of ice, which is a rezzed Himitsu-Bako. During the paid ability window of the approach, the Corp uses the ability on Himitsu-Bako to add it to HQ. The Runner passes this position and will approach the server next, while the other piece of ice protecting the server moves to the innermost position.
   2. b.linkIf a piece of ice is uninstalled or derezzed while it is being encountered, the run moves to the Movement Phase. All outward ice moves one position inward if the ice was uninstalled, and the run continues. The Runner does not re-approach ice they have already passed.
   3. c.linkIf a piece of ice currently being encountered moves to another position or is swapped with installed ice in another position, the Runner remains with the encountered ice and continues the run from that ice's new position.
      1. Example: The Runner encounters Bullfrog as the innermost piece of ice protecting a remote server. Bullfrog's subroutine resolves and it is moved to be the outermost piece of ice protecting Archives. The Runner is now running on Archives and continues the run from Bullfrog's new position.
   4. d.linkIf a piece of ice currently being approached is swapped with ice in another position, the Runner remains in their current position and is now approaching the new piece of ice occupying that position.
   5. e.linkIf a piece of ice is uninstalled, derezzed, moved, or swapped after it is passed, the Runner is not moved.
5. 6.2.5.linkDuring a run, abilities can move the Runner directly to a position.
   1. a.linkIf an ability instructs the Runner to move to a piece of ice in a different position, the Runner's position becomes the position corresponding to that ice, and the server that ice protects becomes the attacked server. The current timing step becomes step 6.9.2, the Approach Ice Phase, or step 6.9.3, the Encounter Ice Phase, according to whether the Runner was directed to approach or encounter the ice.
   2. b.linkIf an ability instructs the Runner to move to "the outermost position" of a server, that server becomes the attacked server. If there is any ice protecting that server, the Runner's position becomes the position of the outermost such piece of ice, and the current timing step becomes step 6.9.2, the Approach Ice Phase. If there is no ice, the Runner ceases to have a position, and the current timing step becomes step 6.9.4, the Movement Phase.
   3. c.linkIf an ability instructs the Runner to move to a position during the Success Phase, during the Run Ends Phase, or while there is no run in progress, instead the Runner does nothing. See rule 6.2.2b.
   4. d.linkIf an ability instructs the Runner to move to and approach a position they are already approaching, instead the Runner does nothing.

6.3. Initiationlink

1. 6.3.1.linkThe initiation phase sets the parameters for the run and begins the run.
2. 6.3.2.linkAt the start of the Initiation Phase, the Runner announces a server to be the attacked server.
   1. a.linkSome abilities state that the Runner "cannot run on" or "cannot initiate a run on" certain servers under certain conditions. These effects refer to the announcement of the attacked server in the Initiation Phase.
      1. Example: Off the Grid states in part, "The Runner cannot initiate a run on this server." This only prohibits the Runner from announcing this particular remote server as the attacked server at the beginning of the run. If an ability changes the attacked server while a run is in progress, Off the Grid does not interfere with that ability.
   2. b.linkSome abilities impose an additional cost to run, either generally or on a particular server. Any costs to run a server must be paid at the time that server is announced as the attacked server.
3. 6.3.3.linkAfter the attacked server is announced, the Runner receives credits equal to the number of bad publicity the Corp has. See section 10.6 for an explanation of bad publicity.
   1. a.linkCredits from bad publicity cannot be spent to pay costs to make the run, as they are received after the attacked server is announced.
   2. b.linkOnce they are received, credits from bad publicity are in the Runner's credit pool and behave just as any other credits. They can be spent, lost, placed on cards, and so on as normally allowed.
   3. c.linkDuring the Run Ends Phase, any credits from bad publicity remaining in the Runner's credit pool are lost.
4. 6.3.4.linkSome abilities look for particular conditions occurring "during a run" or are restricted to being used "during a run." For purposes of abilities, the run formally begins only after the attacked server is announced and any costs are paid.
   1. Example: The Runner initiates a run against a server with a rezzed Heinlein Grid while the Corp has Enhanced Login Protocol in play. They do not lose any credits to Heinlein Grid's ability, as the additional click Enhanced Login Protocol requires them to spend is spent to initiate the run, and is not spent during the run.
5. 6.3.5.linkWhen the Initiation Phase completes, the run moves either to the Approach Ice Phase (section 6.4) or the Movement Phase (section 6.6). If there is ice protecting the attacked server, the Runner's position becomes the outermost piece of ice, and the run proceeds to the Approach Ice Phase. If there is no ice protecting the server, then the run moves directly to the Movement Phase.

6.4. Approach Icelink

1. 6.4.1.linkThe approach ice phase gives the Corp the opportunity to rez the ice in the Runner's current position.
2. 6.4.2.linkFor purposes of meeting trigger conditions, the Runner approaching a piece of ice is equivalent to the Approach Ice Phase beginning at that ice's position. Abilities with this trigger condition are subject to rule 9.2.8f.
3. 6.4.3.linkThe paid ability window in step 6.9.2b of the Approach Ice Phase is the only time the Corp can normally rez ice. In this window, the Corp only gains the ability to rez the piece of ice being approached, not any other ice.
4. 6.4.4.linkWhen the Approach Ice Phase completes, the run moves either to the Encounter Ice Phase (section 6.5) or the Movement Phase (section 6.6). If the approached piece of ice is rezzed, the Runner encounters it next. If the approached piece of ice is unrezzed or if there is no longer ice installed in that position, then the run moves directly to the Movement Phase.

6.5. Encounter Icelink

1. 6.5.1.linkThe encounter ice phase gives the Runner the opportunity to interact with the ice in their current position, then requires the Corp to resolve unbroken subroutines on that ice.
2. 6.5.2.linkFor purposes of meeting trigger conditions, the Runner encountering a piece of ice is equivalent to the Encounter Ice Phase beginning at that ice's position. Abilities with this trigger condition are subject to rule 9.2.8f.
3. 6.5.3.linkAs each encounter begins, each subroutine on the encountered ice gains an "unbroken" status associated with that encounter. See section 9.8 for details.
4. 6.5.4.linkDuring the paid ability window in the Encounter Ice Phase (step 6.9.3b), the Runner can break subroutines on the ice. See rule 9.8.6.
5. 6.5.5.linkAfter the paid ability window in the Encounter Ice Phase closes, unbroken subroutines on the encountered ice resolve. See section 9.8.8.
6. 6.5.6.linkAt the end of the Encounter Ice Phase, the run continues to the Movement Phase, section 6.6.
7. 6.5.7.linkFully Break
   1. a.linkDuring each encounter, the Runner fully breaks the encountered ice the first time all subroutines on that ice are broken.
   2. b.linkWhenever the Runner fully breaks a piece of ice, if all its subroutines were broken using abilities on a single object, that object also fully breaks the ice.
   3. c.linkIf an encountered piece of ice has no subroutines, the Runner fully breaks it when step 6.9.3b of the encounter begins. No objects fully break the ice in this case.
   4. d.linkIf the encountered piece of ice gains subroutines after the Runner fully breaks it, the Runner's status of having fully broken the ice remains in place. Conditions that check whether the Runner fully broke the ice will still be met as normal. Breaking the new subroutines will not fully break the ice or meet related conditions again.
8. 6.5.8.linkBypass
   1. a.linkWhen an effect allows the Runner to bypass a piece of ice, the Encounter Ice Phase is aborted and the Runner immediately proceeds to pass that ice.
   2. b.linkMost bypass effects occur at the beginning of an encounter and result in steps 6.9.3b and 6.9.3c never occurring, meaning that subroutines on the encountered ice are neither broken nor resolved.
   3. c.linkA few bypass effects can be triggered later. If ice is bypassed in step 6.9.3b, subroutines may or may not have been broken, but step 6.9.3c never occurs so no subroutines resolve. Note that for ice with zero subroutines, the Runner has "broken all subroutines" if and only if step 6.9.3b was reached. See rule 9.12.2d.
      1. Example: The Runner plays Forked and encounters a Troll that they can bypass with Femme Fatale. The Runner pays 0[c] to bypass the Troll with Femme Fatale. Forked does not meet its trigger condition, and Troll is not trashed, because the opportunity to break subroutines was never reached.
9. 6.5.9.linkForced Encounters
   1. a.linkIf an ability directs the Runner to encounter a piece of ice without first changing their position, resolve an Encounter Ice Phase but do not change the Runner's position, if any. After the encounter, return to the effect that caused the encounter and proceed from there. This type of encounter outside the normal progression of a run is referred to as a forced encounter.
      1. Example: If Shiro causes Chrysalis to be accessed, resolve the encounter with Chrysalis and then return to resolving subroutines on Shiro.
   2. b.linkIf a forced encounter occurs during a run, an instruction to end the run during that encounter is applied to both the Encounter Ice Phase being resolved and the phase from which the additional encounter was initiated. If a forced encounter occurs outside of a run, an instruction to end the run simply closes the Encounter Ice Phase and returns the game to the effect that called for the encounter.
      1. Example: The Corp uses The Twins to force the Runner to encounter a piece of ice again when they pass it. If a subroutine directs the Corp to end the run during the extra encounter, both that encounter and the original Movement Phase are aborted, and the game proceeds to the Run Ends phase.
   3. c.linkAn instruction that creates a forced encounter is not finished resolving until the encounter is complete.
   4. d.linkDuring a forced encounter, if an ability moves the Runner or directs the Runner to approach a piece of ice, that movement resolves and changes the parameters of the underlying run normally, but does not end or interfere with the forced encounter.

6.6. Movementlink

1. 6.6.1.linkThe movement phase handles the progression of the run between pieces of ice and after the innermost piece of ice, up to the point when the Runner approaches the attacked server.
2. 6.6.2.linkIf the Movement Phase was reached from the Approach Ice Phase or the Encounter Ice Phase, the Runner passes the ice in their position.
3. 6.6.3.linkDuring each Movement Phase, the Runner has the opportunity to jack out. See section 6.1.5.
4. 6.6.4.linkIf the Runner declines to jack out, their position moves to the next inward position if there is one.
5. 6.6.5.linkIf the Runner moves to a new position, the run continues from the Movement Phase to the Approach Ice Phase, section 6.4. The Runner will approach the piece of ice in their new position.
6. 6.6.6.linkIf the Runner does not jack out or return to the Approach Ice Phase, they approach the server. This has no inherent effects, but is referred to by some card abilities. After the Runner approaches the server, the run continues to the Success Phase, section 6.7.

6.7. Successlink

1. 6.7.1.linkThe success phase declares the run successful and allows the Runner to breach the attacked server.
2. 6.7.2.linkA run during which the runner breaks through the Corp's defenses and reaches the server itself is declared a successful run. This label is frequently referred to by card abilities.
3. 6.7.3.linkDeclaring a run to be successful is not the same as the Success Phase beginning. Accordingly, abilities that have trigger conditions related to a successful run are not subject to rule 9.2.8f.
4. 6.7.4.linkMany abilities that initiate a run contain a conditional ability with the trigger condition "If successful". This means, "After the run created this way becomes successful".
   1. a.linkIf an effect that initiates a run specifies that that run must be made against a specific server or servers, any "If successful" abilities associated with that effect are tied to that server or servers. If the attacked server has changed since the run was initiated, and no longer is a server that could have been chosen for this run, the "If successful" abilities do not meet their trigger conditions.
      1. Example: The Runner plays Because I Can, which directs them to make a run on a remote server. If an effect moves the run to a central server, the "If successful" effect on Because I Can will not apply. However, if the run is moved instead to another remote server, the "If successful" effect is still applied, since Because I Can would have allowed a run on the second remote server to begin with.
   2. b.link"If successful" abilities frequently create lingering effects (see section 9.10) that modify the procedure for accessing cards or replace breaching the attacked server with another effect entirely. These effects apply to the breach permitted by the rules for this run (see rule 6.7.5), and they expire when the run is complete.
   3. c.linkIf an "If successful" effect gives the Runner an effect they can optionally carry out instead of breaching, that decision is made at the time the breach would begin, in step 6.9.5b.
      1. Example: The Runner plays Account Siphon while Ash 2X3ZB9CY is installed in the root of HQ, and the run is successful. The Runner can wait until after the trace from Ash 2X3ZB9CY completes before deciding to access cards normally or force the Corp to lose credits.
5. 6.7.5.linkWhen the Runner breaches the server, they follow the procedures detailed in section 7.

6.8. Run Ends Phaselink

1. 6.8.1.linkThe run ends phase formalizes the end of the run and prepares the game to return to the timing structure from which the run was initiated.
2. 6.8.2.linkAt the beginning of the Run Ends Phase, the game processes each priority window that was open when the run was ended. This is done according to the following procedure:
   1. a.linkIf a paid ability window was open when the run was ended, the window closes. No player can trigger further paid abilities or resolve other options the window would normally allow (such as rezzing cards).
      1. Example: The Corp spends a counter from a scored Nisei Mk II to end the run. Once this happens, the Runner does not have an opportunity to use their bad publicity credits from this run to pay for using Self-Modifying Code.
   2. b.linkIf the run was ended during a reaction window opened due to a phase beginning, the reaction window closes, as per rule 9.2.8f. No other pending abilities are resolved.
      1. Example: The Runner uses the ability on Security Nexus during a reaction window at the beginning of the Encounter Ice Phase. The trace is successful, so the ability ends the run. If Tollbooth's ability is also pending in this reaction window, it will not be resolved, since the encounter has ended.
   3. c.linkAny other open priority window is completed normally. If more than one priority window needs to be completed this way, they are resolved in the usual order described in section 9.1.2.
3. 6.8.3.linkDuring the Run Ends Phase, if the Runner has any credits from bad publicity remaining in their credit pool, the Runner loses those credits.
4. 6.8.4.linkAs part of the Run Ends Phase, the game determines whether the run should be declared an unsuccessful run. This is a label applied to runs in which the Runner failed to reach the server they attacked, and is referred to by card abilities. The run is declared unsuccessful if neither of the following conditions have been met:
   1. a.linkIf the run reached step 6.9.5, the Success Phase, it is not declared unsuccessful. This is the case regardless of whether the run was actually declared successful.
      1. Example: The Runner reaches a server with Crisium Grid rezzed. Crisium Grid's ability stops the run from being declared successful, but the run is not declared unsuccessful either.
   2. b.linkIf the attacked server has ceased to exist, the run is not declared unsuccessful. See rule 8.5.8.
5. 6.8.5.linkConditions related to a run ending are not met as soon as an "end the run" effect resolves or at the beginning of the Run Ends Phase. Instead, these conditions are met at step 6.9.6d, when the entire run timing structure is complete. Similarly, static abilities that apply during a run and durations that apply until the end of a run expire at step 6.9.6d.
   1. Example: The Runner plays The Noble Path to make a run in which they prevent all damage. During the run, the subroutine on Chum resolves, and then the Runner encounters Wall of Static and does not break its subroutine. When the "end the run" ability resolves, the encounter also ends, so the trigger condition on Chum's delayed conditional ability is met. The ability will resolve and fail to damage the Runner during the Run Ends Phase, because The Noble Path's effect still applies. Similarly, Georgia Emelyov's first ability meets its trigger condition at step 6.9.6c, which is still before the run is over, so the damage will be prevented.
   2. Example: The Runner plays The Noble Path to make a run in which they prevent all damage. The run is successful but the Runner takes a tag during the run. When the run ends, Dedicated Response Team's ability meets its trigger condition at the same time that The Noble Path's effect expires, so the Runner will suffer 2 meat damage.

6.9. Steps of a Runlink

1. 6.9.1.linkInitiation Phase
   1. a.linkThe Runner announces the attacked server.
   2. b.linkThe Runner gains 1[c] to spend during the run for each bad publicity the Corp has.
   3. c.linkThe run formally begins. Conditions related to the run beginning or initiating are met.
   4. d.linkThe Initiation Phase is complete. If the attacked server has at least one piece of ice protecting it, proceed to step 6.9.2, Approach Ice Phase, approaching the outermost piece of ice protecting the attacked server. If the attacked server is not protected by ice, proceed to step 6.9.4, Movement Phase.
2. 6.9.2.linkApproach Ice Phase
   1. a.linkThe approach begins. Conditions related to the Runner approaching this ice are met.
   2. b.linkA paid ability window occurs, in which players may use paid abilities and the Corp may rez non-ice cards. Additionally, the Corp can rez the approached piece of ice. (P) (R)
   3. c.linkThe Approach Ice Phase is complete. If the approached piece of ice is rezzed, continue to step 6.9.3, Encounter Ice Phase. Otherwise, proceed to step 6.9.4, Movement Phase.
3. 6.9.3.linkEncounter Ice Phase
   1. a.linkThe encounter begins. Conditions related to the Runner encountering this ice are met.
   2. b.linkA paid ability window occurs, in which players may only use paid abilities. Subroutines on the encountered ice can be broken during this window. (P)
   3. c.linkIf there are unbroken subroutines that have not yet resolved this encounter, the Corp resolves the next such subroutine in order. Otherwise, skip to (e).
   4. d.linkReturn to (c).
   5. e.linkThe Encounter Ice Phase is complete. Continue to step 6.9.4, Movement Phase.
4. 6.9.4.linkMovement Phase
   1. a.linkIf the Runner's position corresponds to a piece of ice, the Runner passes that ice. Conditions related to passing ice are met. If there are no positions more inward than the ice just passed, conditions related to passing all of the ice protecting a server are also met.
   2. b.linkA paid ability window occurs, in which players may only use paid abilities. (P)
   3. c.linkThe Runner may choose to jack out, proceeding to step 6.9.6, Run Ends Phase. If the Runner does not, continue to (d).
   4. d.linkThe Runner's position moves to the next position inward, if any.
   5. e.linkA paid ability window occurs, in which players may use paid abilities and the Corp may rez non-ice cards. (P) (R)
   6. f.linkIf the Runner moved to a new position, return to step 6.9.2, Approach Ice Phase, approaching the piece of ice in their new position. If not, continue to (g).
   7. g.linkThe Runner approaches the attacked server. Conditions related to the Runner approaching a server are met.
   8. h.linkThe Movement Phase is complete. Continue to step 6.9.5, Success Phase.
5. 6.9.5.linkSuccess Phase
   1. a.linkThe run is declared successful. Conditions related to a successful run are met.
   2. b.linkThe Runner breaches the attacked server.
   3. c.linkThe Success Phase is complete. Continue to step 6.9.6, Run Ends Phase.
6. 6.9.6.linkRun Ends Phase
   1. a.linkAny priority windows that were open when the run moved to this phase are completed or closed as described in section 6.8.2.
   2. b.linkThe Runner loses any unspent bad publicity credits.
   3. c.linkIf the Success Phase was not reached during this run and the attacked server still exists, the run becomes unsuccessful.
   4. d.linkThe Run Ends Phase and the run as a whole are both complete.

7. Accessing Cards and Breaching Serverslink

7.1. Accessing Cardslink

1. 7.1.1.linkAccessing is the process of the Corp showing one of their cards to the Runner for potential interaction.
2. 7.1.2.linkWhile the Runner is accessing a card, the Runner is allowed to look at that card, even if it would normally not be visible to them. While the Runner is accessing a card, the Corp is allowed to look at it as well, except when the card is being accessed from R&D.
3. 7.1.3.linkAn ability that meets its trigger condition when its source card is accessed is active even if the source card is inactive. See section 9.1.8.
4. 7.1.4.linkDuring each access, the Runner has 1 opportunity to use a mid-access ability. This occurs after the reaction window at the beginning of the access, and before the Runner steals an accessed agenda.
5. 7.1.5.linkThe Runner always has the ability "Access → Pay the trash cost of the accessed card: Trash it." This is the basic trash ability.
   1. a.linkAll assets and upgrades have trash costs, as do some ice and operations. If a card does not have a trash cost, the Runner cannot pay its trash cost, and therefore the Runner cannot use the basic trash ability during that access.
   2. b.linkThe Runner cannot trash or pay the trash cost of a card in the Corp's discard pile, either with the basic trash ability or with other mid-access abilities.
   3. c.linkOne card, Mumbad Virtual Tour, has the ability "If the Runner accesses this upgrade while it is installed, they must trash it, if able." When this ability applies, the Runner can use any mid-access ability they have available that trashes the card, but they cannot decline to use a mid-access ability or use one that would not trash the accessed card unless they are unable to pay the cost of any ability that would trash it.
   4. d.linkOne card, Neutralize All Threats, has the ability "The first time each turn you access a card with a trash cost, reveal it. You must trash that card by paying its trash cost, if able." When this ability applies, the Runner can only use the basic trash ability. They cannot decline to use a mid-access ability or use a mid-access ability available from a card unless they cannot pay the cost of the basic trash ability.
6. 7.1.6.linkIf, after resolving mid-access abilities, the Runner is still accessing an agenda, they must steal it.
   1. a.linkSome abilities can create additional costs to steal an agenda. The Runner can decline to pay such costs and not steal the agenda. See section 1.16.10.
7. 7.1.7.linkIf a card moves to another location while it is being accessed, the access ends immediately.
8. 7.1.8.linkIf a run is in progress, an instruction to end the run ends any access taking place. If an access is occurring outside of a run, an instruction to end the run has no effect on that access.
9. 7.1.9.linkOne card, Information Sifting, uses a method other than a breach to establish a set of cards for the Runner to access. The Runner accesses those cards one at a time in the order of their choice. Each access is performed as a separate instruction. See rule 9.11.4b. Accessing cards in this way is an exception to rule 9.12.2a.
10. 7.1.10.linkOne card, Counter Surveillance, instructs the Runner to access a certain number of cards from a server without mentioning a breach. The procedure for these accesses follows the normal rules for breaching that server except: there is no random access limit if the server is HQ or R&D; and the procedure ends once the designated number of cards have been chosen for access.

7.2. Steps of Accessing a Cardlink

1. 7.2.1.linkThe card is accessed. Conditions related to accessing this card are met.
2. 7.2.2.linkThe Runner may use a single mid-access ability, such as the basic trash ability.
3. 7.2.3.linkIf the accessed card is an agenda, the Runner must steal it.
4. 7.2.4.linkThe access is complete. Conditions related to an access ending are met.

7.3. Breaching Serverslink

1. 7.3.1.linkBreaching a server is the process of the Runner accessing a particular set of cards associated with that server. Most accesses occur during a breach. Step 6.9.5b of a run calls for the Runner to breach the attacked server, but card abilities can also directly instruct the Runner to breach a server.
2. 7.3.2.linkWhen the Runner breaches Archives, all the facedown cards in the Corp's discard pile are turned faceup before the Runner accesses any cards.
   1. a.linkIf a card is added to Archives facedown after this step, that card remains facedown for the remainder of the breach, even after it is accessed. The Runner can only look at a facedown card in Archives while accessing it.
3. 7.3.3.linkThe cards associated with a breached server that the Runner could potentially access are called Candidates. The set of candidates is compiled from the cards in the root of the breached server and, for central servers, the cards in the zone that corresponds to that server (see rule 4.6.7a). Section 7.4 defines which of these cards are candidates.
4. 7.3.4.linkDuring a breach, the Runner is presented with the current candidates. They choose 1 of those cards and access it. This process repeats until there are no longer any candidates.
   1. a.linkWhen presented with candidates during a breach of HQ, the Runner chooses either a specific candidate that is not in the Corp's hand or to access a random candidate from among the ones in the Corp's hand. A card randomly chosen this way is treated as though the Runner had chosen it.
   2. b.linkOne card, Dedicated Neural Net, instructs the Corp to choose which cards the Runner accesses from HQ. While this effect applies, the Runner still chooses candidates that are not in the Corp's hand as normal. Whenever the Runner chooses to access a candidate from the Corp's hand, instead of a candidate being chosen at random, the Corp chooses 1 of those candidates for the Runner to access. The chosen card is still treated as though the Runner had chosen it.
5. 7.3.5.linkThe Runner can only choose candidates from the Corp's hand or deck a limited number of times during a breach of HQ or R&D, respectively. This number is called the Random Access Limit. Before the Runner begins accessing cards during a breach of HQ or R&D, the random access limit for that breach is determined, after which it will not change for the remainder of that breach.
   1. a.linkBy default, the random access limit is 1.
   2. b.linkIf an ability allows the Runner to "access additional cards" during a breach of HQ or R&D, the effect of that ability is to increase the random access limit. Such an ability can only be applied at the beginning of the breach, before the value of the random access limit is set.
   3. c.linkCards are counted against the random access limit in the manner described in rule 7.3.6a.
6. 7.3.6.linkSome rules and abilities refer to the number of cards the Runner accesses or the number of times the Runner accesses a card.
   1. a.linkIf such a reference applies while a breach is in progress, it counts the number of times a candidate has been chosen so far during that breach, regardless of how many of those candidates have actually been accessed.
      1. Example: The Runner plays Immolation Script, and the subroutine on Hudson 1.0 resolves before Archives is breached. The Runner will only be able to choose 1 candidate during the breach, regardless of whether they choose to access that card or apply Immolation Script's replacement effect.
   2. b.linkIf such a reference applies after a breach is complete, it counts only the number of times the Runner actually resolved an access during that breach.
      1. Example: The Runner plays Rip Deal while they have Obelus installed. If they use Rip Deal's ability to replace accesses of cards in HQ with adding cards from the heap to the grip, the cards those replacement effects applied to were not accessed. When Obelus's ability resolves after the breach ends, it will only cause the Runner to draw cards for upgrades they accessed in the root of HQ.
7. 7.3.7.linkIf a run is in progress, an instruction to end the run ends any breach taking place. If there is no run in progress, an instruction to end the run has no effect on a breach.
8. 7.3.8.linkIf a server would be breached while a breach is already in progress, instead the new breach takes place when the current breach ends. The effect creating the delayed breach is treated as a conditional ability controlled by the Runner.
   1. Example: The Runner steals Clone Retirement during a breach of HQ, causing the Corp to take bad publicity. The Runner must complete the current breach before beginning the breach granted from Raymond Flint's first ability.

7.4. Determining Candidateslink

1. 7.4.1.linkThe candidates at the beginning of a breach are as follows:
   1. a.linkEach card in the root of the breached server is a candidate
   2. b.linkIf the breached server is HQ, each card in the Corp's hand is a candidate
   3. c.linkIf the breached server is R&D, the top card of the Corp's deck is a candidate.
   4. d.linkIf the breached server is Archives, each card in the Corp's discard pile is a candidate.
2. 7.4.2.linkIf at any time the Runner is prohibited from accessing an object, that object ceases to be a candidate and cannot become a candidate.
   1. Example: The Corp performs a successful trace with the ability on Ash 2X3ZB9CY, prohibiting the Runner from accessing any card other than Ash for the remainder of the current run. When the server is breached, Ash will be the only candidate for the Runner's first selection, and then there will be no candidates remaining, so the breach will end.
   1. a.linkOne card, Hudson 1.0, creates an effect that prohibits the Runner from accessing more than 1 card during a run. This effect always considers whether the Runner has actually accessed a card during that run, even when rule 7.3.6a would normally apply. If the Runner has accessed any cards, this effect prohibits all accesses, and therefore there will be no candidates.
3. 7.4.3.linkOnce the Runner chooses a candidate for access, it ceases to be a candidate for the remainder of that breach. It does not matter whether the chosen candidate is actually accessed. As long as the card is chosen, it ceases to be a candidate.
   1. Example: The Runner is breaching Archives during a run made with Immolation Script. They choose a piece of ice from the set of candidates, and apply Immolation Script's replacement effect to trash another card instead of accessing the chosen ice. After resolving this, the chosen ice is no longer a candidate and cannot be accessed again this breach. (The newly-trashed card, however, could be a candidate.)
   2. Example:
4. 7.4.4.linkWhen the random access limit is reached during a breach of HQ or R&D, all candidates in the zone corresponding to the breached server cease to be candidates, and no cards in that zone can become candidates for the remainder of that breach. See section 7.3.5.
5. 7.4.5.linkIf a candidate leaves the breached server, it ceases to be a candidate. Note that the moved card could be a new object, which could be eligible to become a new candidate if appropriate.
   1. Example: The Runner trashes an installed upgrade during a breach of Archives. That card moves to the Corp's discard pile. The new object for the upgrade's existence in the Corp's discard pile becomes a candidate, so the Runner will access the same physical card twice during this breach.
6. 7.4.6.linkCards entering a server while a breach is in progress can become candidates.
   1. a.linkIf a card enters the root of a server during a breach of that server, the Runner decides whether that card becomes a candidate during step 10.3.1i of the next checkpoint.
   2. b.linkIf a card enters the Corp's hand during a breach of HQ while the random access limit has not yet been reached, that card becomes a candidate.
   3. c.linkIf a card enters the Corp's deck during a breach of R&D, that card could become a candidate (either at that time or later in the breach), depending on the random access limit and its position within the deck. See section 7.4.7.
   4. d.linkIf a card enters the Corp's discard pile during a breach of Archives, that card becomes a candidate. See also rule 7.3.2a.
7. 7.4.7.linkDuring a breach of R&D, the Runner is presented with 1 candidate from the Corp's deck at a time in turn, working down from the top of the deck. Cards are made candidates 1 at a time until the access limit is reached.
   1. a.linkAfter the Runner chooses a candidate from the Corp's deck and whenever any cards enter, leave, or are reordered within the Corp's deck, all cards in the Corp's deck cease to be candidates. Then, if the random access limit has not been reached, the topmost eligible card in the deck becomes a candidate. A card is eligible for this purpose if the Runner has not already chosen to access that object and is not prohibited from accessing that object in this breach.
      1. Example: The Runner plays The Maker's Eye and breaches R&D, accessing 2 additional cards. They access Celebrity Gift and then access and steal Bacterial Programming. The Corp uses Bacterial Programming's ability to rearrange cards in R&D, but they leave Celebrity Gift as the top card of R&D. The cards returned to the top of R&D are new objects, so the Runner must continue the breach from the top of R&D and will access Celebrity Gift again.
      2. Example: The Corp is playing Seidr Laboratories and has Strongbox rezzed in the root of R&D. The Runner breaches R&D with a random access limit of 4. They first access the top card of the Corp's deck and leave it in place. The 2nd card from the top now becomes a candidate, and turns out to be an agenda, which the Runner steals by spending [click] to pay the additional cost imposed by Strongbox. The Corp then uses Seidr Laboratories to add 1 card from Archives to the top of R&D. The 3rd candidate presented to the Runner is the card newly added to the top of R&D. After accessing that card, the next card down is still the object that was accessed first, so the card below that (currently 3rd from the top) becomes the 4th and final candidate.
   2. b.linkOne card, Showing Off, allows the Runner to access cards from the bottom of R&D. While this effect applies, candidates in the Corp's deck are presented working up from the bottom: treat rule 7.4.1c as if it said "bottom" instead of "top" and rule 7.4.7a as if it said "bottommost" instead of "topmost".

7.5. Steps of Breaching a Serverlink

1. 7.5.1.linkBreaching the server formally begins. Conditions related to breaching this server are met.
2. 7.5.2.linkIf the breached server is Archives, turn all cards in the Corp's discard pile faceup.
3. 7.5.3.linkIf the breached server is HQ or R&D, determine the limit to how many times the Runner can choose a candidate from the Corp's hand or deck.
4. 7.5.4.linkThe Runner chooses a candidate. If they cannot, skip to step 7.5.7.
5. 7.5.5.linkThe Runner accesses the chosen card.
6. 7.5.6.linkReturn to step 7.5.4.
7. 7.5.7.linkThe breach is complete. Conditions related to the breach ending are met.

8. Card Manipulationlink

8.1. Faceup and Facedown Statuslink

1. 8.1.1.linkAn agenda, asset, upgrade, or piece of ice is unrezzed if it is installed and facedown. An asset, upgrade, or piece of ice is rezzed if it is installed and faceup. Runner cards, faceup agendas, operations, events, and counters are neither rezzed nor unrezzed.
2. 8.1.2.linkTo rez an unrezzed card is to turn it faceup.
   1. a.linkSome paid ability windows allow the Corp to rez assets and upgrades. See section 9.2.7. The paid ability window at step 6.9.2b of a run allows the Corp to rez ice.
   2. b.linkCard abilities can direct or allow the Corp to rez cards at other times.
   3. c.linkAgendas cannot be rezzed.
   4. d.linkBefore rezzing a card, the Corp must pay that card's rez cost. This includes both rezzing in a paid ability window and rezzing through a card ability. Card abilities can modify or ignore rez costs, but must state this explicitly.
   5. e.linkTo resolve rezzing a card, the Corp pays its rez cost (accounting for any modifiers or additional costs), a checkpoint occurs (as required by rule 10.3.4), then the Corp turns the card faceup. For purposes of meeting trigger conditions, the card is considered to be rezzed at the conclusion of this process.
3. 8.1.3.linkTo derez a rezzed card is to turn it facedown.
   1. a.linkCards are only derezzed by card effects.
   2. b.linkThere is no inherent cost associated with derezzing a card.
   3. c.linkDerezzing a card is instantaneous and has no component steps.
4. 8.1.4.linkSome abilities can install Runner cards facedown or turn already-installed Runner cards facedown.
   1. a.linkInstalled Runner cards that are facedown do not have a name, type, or subtypes, and their abilities are not active.
   2. b.linkFacedown installed Runner cards are distinct. The origin of each such card (when and how it was installed facedown, or what faceup installed card was turned facedown) is open information.
   3. c.linkAfter a facedown Runner card enters the heap, it is turned faceup.
   4. d.linkA Runner card turned facedown is not considered to be uninstalled and simply remains in the play area.
   5. e.linkIf an installed facedown Runner card is turned faceup, the card gains its name, type, and subtypes, and it becomes active. Turning an installed facedown Runner card faceup does not meet the trigger conditions of "when installed" abilities.
   6. f.linkRunner cards are never considered rezzed or unrezzed.

8.2. Card Movementslink

1. 8.2.1.linkA movement is a way that cards change their zone or location following special rules. The movements are: arrange, draw, forfeit, install, play, search, score, steal, swap, and trash.
   1. a.linkOther terms that change the locations of cards are not movements. If an ability directs a player to "add" or "move" cards to 1 or more locations, simply put those cards in the indicated locations. If an ability or game rule directs a player to "discard", "set aside", or "remove from the game" 1 or more cards, simply put those cards in their owner's discard pile, the set-aside zone, or the removed-from-game zone, respectively.
2. 8.2.2.linkIf a replacement effect modifies the effects of a movement, but does not replace the entire movement by name, the modified effect is still an occurrence of that movement and can still meet trigger conditions relating to that type of movement.
   1. Example: Harbinger's ability modifies the effects of trashing it by replacing adding Harbinger to the heap with turning it facedown. Harbinger is still trashed when the modified effect resolves. If this is the first time this turn that the Runner trashed one of their installed cards, they will be able to resolve Wasteland's ability.
   1. a.linkIf a movement is replaced or prevented entirely or otherwise cannot be carried out, that movement does not take place and conditions related to that type of movement are not met.
      1. Example: The Corp is resolving the first subroutine on Rototurret to trash an installed program. The Runner uses Sacrificial Construct to prevent the program from being trashed. Since trashing did not occur, the Runner does not place a power counter on District 99, and District 99 can still meet its trigger condition if a program or piece of hardware is successfully trashed later in the turn.
3. 8.2.3.linkTo arrange a set of cards is to reposition them among their current locations. The full rules for arranging are detailed in section 8.3.
4. 8.2.4.linkTo draw a given number of cards is to move that many cards from the top of a player's deck to their hand. The full rules for drawing cards are detailed in section 8.4.
5. 8.2.5.linkTo forfeit an agenda is to move it from a player's score area to the removed-from-game zone. When a player forfeits an agenda, its agenda points no longer contribute to that player's score, and any objects hosted on it are trashed.
6. 8.2.6.linkTo install a card is to move it from its current zone to the play area. The full rules for installing cards are detailed in section 8.5.
7. 8.2.7.linkTo play an event or operation is to move it from its current zone to the play area, resolve its play abilities, and then trash it. The full rules for playing events and operations are detailed in section 8.6.
8. 8.2.8.linkTo search is to look at a specified zone and potentially set aside cards from that zone. The full rules for searching are detailed in section 8.7.
9. 8.2.9.linkTo score an agenda is to move it from its current zone to the Corp's score area. The full rules for scoring are detailed in section 1.17.
10. 8.2.10.linkTo steal an agenda is to move it from its current zone to the Runner's score area. The full rules for stealing are detailed in section 1.17.
11. 8.2.11.linkTo swap a pair of cards is to move each card to the other's location simultaneously. The full rules for swapping are detailed in section 8.8.
12. 8.2.12.linkTo trash a card is to move it from its current zone to its owner's discard pile. The full rules for trashing are detailed in section 1.19.

8.3. Arranging and Rearranging Cardslink

1. 8.3.1.linkTo arrange or rearrange an ordered set of 2 or more cards is to reposition them among their current locations. The words "arrange" and "rearrange" are synonymous.
   1. a.linkIf a player is instructed to arrange 1 or fewer cards, instead that player does nothing.
2. 8.3.2.linkWhen a player arranges a set of installed ice, that player carries out the arrangement by repeatedly choosing and swapping 2 pieces of ice. Each swap follows all the usual rules for swapping cards in section 8.8.
   1. a.linkNo checkpoints occur during the sequence of swaps. An ability that meets its condition while ice is being arranged will become pending at the end of resolving the instruction in which arranging ice is taking place.
3. 8.3.3.linkWhen a player arranges cards from the top of their deck or their opponent's deck, that player sets those cards aside facedown, secretly puts them in the order of their choice, and returns them to the top of that deck. They do not declare which cards moved to which positions. All of the arranged cards become new objects after they are arranged, even cards that remain in the same location in the deck.

8.4. Drawing Cardslink

1. 8.4.1.linkdrawing cards is a process that moves cards from a player's deck to their hand.
2. 8.4.2.linkTo draw 1 or more cards, a player sets aside that many cards from the top of their deck facedown. The cards are then considered drawn, and abilities with trigger conditions related to cards being drawn can act on them. When resolving any such abilities is complete, the set-aside cards are added to their owner's hand.
   1. a.linkAbilities with a trigger condition that refers to cards being drawn can see the drawn cards in the set-aside zone. This is an exception to rule 4.8.3.
   2. b.linkAbilities that do not refer specifically to cards a player has drawn are subject to rule 4.8.3, and only see the drawn cards move directly from the player's deck to their hand.
3. 8.4.3.linkAbilities that resolve while drawn cards are set aside can move those cards or add new cards to that set.
   1. a.linkIf a drawn card leaves the set-aside zone, it is no longer considered "drawn" and remains in its new location when the drawn cards are added to the hand.
   2. b.linkIf a drawn card is swapped with another card, the card swapped into the set-aside zone is now considered "drawn", can be manipulated by other abilities, and will be added to the hand with the other drawn cards.
      1. Example: The Corp takes their mandatory draw while they have Daily Business Show and Raman Rai rezzed. They set aside Wraparound and Enigma from the top of R&D. After looking at those cards and the cards in Archives, the Corp uses Raman Rai to reveal the Enigma and a Tollbooth from Archives and swap them. Then, the corp uses Daily Business Show to add Tollbooth to the bottom of the deck. Finally, the Corp adds Wraparound to HQ.
4. 8.4.4.linkIf an ability directs multiple players to draw cards at the same time, those players follow the procedure for drawing cards together. Abilities relating to all of those draws will become pending in the same reaction window.
   1. a.linkIf an ability gives multiple players the option to draw cards at the same time, first each player indicates whether or how many cards they will draw, starting with the active player. Then the indicated draws are performed simultaneously.
5. 8.4.5.linkSteps of Drawing N Cards
   1. a.linkSet aside N cards from the top of the drawing player's deck. The cards are now considered drawn and can be looked at by their controller.
   2. b.linkA checkpoint occurs.
   3. c.linkAdd the set-aside cards to the player's hand.

8.5. Installing and Uninstalling Cardslink

1. 8.5.1.linkInstalling an agenda, asset, ice, upgrade, hardware, program, or resource card is the act of placing that card into the play area. Events, operations, and identities are never installed.
   1. a.linkCards and counters can also be installed onto other cards if either the card being installed onto or the card or counter being installed has an ability allowing this. The relationship created this way is called hosting and is discussed in section 1.13. Some abilities also host cards without installing them.
   2. b.linkA card or counter is uninstalled when it stops being installed for any reason.
2. 8.5.2.linkCorp cards are installed facedown, unrezzed, and remain inactive until rezzed. Corp cards are installed into specific locations. See section 4.6.6 for more information on servers and the locations of installed Corp cards.
   1. a.linkAs part of installing a card, the Corp chooses which server will be the destination for that card. The Corp can either choose an already existing server as the destination or announces that the card will create a new remote server.
   2. b.linkThe Corp always installs an agenda or asset into the root of a remote server.
   3. c.linkThe Corp always installs an upgrade into the root of a central or remote server.
   4. d.linkUnless otherwise indicated, the Corp always installs ice into the outermost position protecting the destination server.
3. 8.5.3.linkCards in servers cannot be rearranged unless instructed by a card ability. To organize this hidden information for both players, it is important that the Corp observes the following rules for card orientation:
   1. a.linkAgendas, assets, and upgrades are always installed in a vertical orientation. An upgrade in the root of a remote server is installed in the same position as an agenda or asset. The Runner should not be able to tell what type of card is installed in the root of a remote server by its position.
   2. b.linkIce is always installed in a horizontal orientation.
4. 8.5.4.linkRunner cards are normally installed faceup, active. Runner cards are generally installed without designated locations.
5. 8.5.5.linkInstalling cards is an exception to rule 9.12.2a. If an effect would install more than one card, then those cards are chosen and installed one at a time, following all of the steps of the installation process (step 8.5.15) for each card before choosing and installing the next. Each such installation is performed as a separate instruction. See rule 9.11.4b.
   1. Example: The Runner uses Mass Install to install three programs. The Runner can install Dhegdheer first, and then host one of the other two programs on Dhegdheer in order to reduce the install cost.
6. 8.5.6.linkAs part of the installation process, a player installing an agenda, asset, upgrade, ice, or program has the opportunity to trash like cards.
   1. a.linkWhen installing an agenda or asset in the root of a remote server, or an upgrade in the root of any server, the Corp may first trash any number of other cards already installed in the root of that server. If the card to be installed is an asset or agenda, the Corp must trash any other asset or agenda from that server. If the card to be installed is a region, the Corp must trash any other region from that server.
   2. b.linkWhen installing ice protecting a server, the Corp may first trash any number of other ice already installed protecting that server. Ice trashed in this way will not be counted when determining the install cost of the new ice.
   3. c.linkWhen installing a program, the Runner may first trash any number of programs already installed. They must do so if installing the new program would exceed their memory limit.
7. 8.5.7.linkIf the Corp trashes any cards during the installation process, the trashed cards are placed in Archives with the same faceup or facedown status they had while installed.
8. 8.5.8.linkIf the last card protecting a remote server or in the root of that server is uninstalled outside of the process of installing another card, then the server ceases to exist during the next checkpoint. See section 10.3.
9. 8.5.9.linkThe Corp cannot destroy a server by installing cards. While the Corp is installing a card with a remote server as its destination, that server does not cease to exist during any checkpoints that occur before the install effect is complete. Even if the last card installed in the root of or protecting a remote server is trashed during the installation process, it is still considered the same server after the new card has been installed.
10. 8.5.10.linkIf a piece of ice is uninstalled while being approached or encountered, any open paid ability window is completed. Then the approach or encounter ends without completing any further steps of that timing structure. The Runner passes the position the uninstalled ice had occupied, and the run continues. See section 6.2 for rules about positions during a run.
11. 8.5.11.linkSome types of cards have an install cost, which must be paid before the card can become installed, unless an ability indicates that this cost should be ignored.
    1. a.linkThe install cost of a piece of ice is 1 credit for each piece of ice already installed protecting the destination server at the time the cost is to be paid. The install cost of a piece of hardware, program, or resource is indicated on the card. Assets, agendas, upgrades, and facedown Runner cards have no install cost. See also rule 1.16.6b.
    2. b.linkIf a card has an install cost of X, the value for X is chosen by the player at the time the cost would normally be paid, according to any stipulations indicated in the card's text box. This value of X is maintained until the install effect is complete.
    3. c.linkAfter the install cost is paid, a checkpoint occurs, as required by rule 10.3.4.
12. 8.5.12.linkSome upgrades have an ability that specifies 1 or more central servers or "remote server" followed by the word "only". This is a restriction on the locations an upgrade can occupy that applies at all times, even if the upgrade is inactive. The Corp cannot choose the root of a non-specified server as the installation destination for such an upgrade, and such an upgrade cannot be swapped into the root of a non-specified server.
13. 8.5.13.linkIf a player attempts to install a facedown card or a card from a hidden or secret zone, they are required in certain cases to reveal that card in order to verify that the installation is valid.
    1. a.linkPlayers are not required to and should not reveal an installed card simply to verify that it has an appropriate card type.
       1. Example: The Corp controls a remote server with a facedown card in its root, and uses a basic action to install another card into that root. To satisfy the rules, the new card must be an asset, upgrade, or agenda, since those are the only card types that can normally be installed in the root of a remote server. Additionally, at least one of the two cards must be an upgrade, since there can only be at most 1 asset or agenda in the root of a server. However, the Corp does not reveal cards to verify either of these properties.
       2. Example: The Corp resolves the first subroutine on Brân 1.0. They do not reveal the card they install to verify that it is a piece of ice as stipulated in the text of the subroutine, nor do they reveal the card to verify that it is a piece of ice as necessitated from installing it protecting a server.
    2. b.linkPlayers are not required to and should not reveal an installed card to verify that it meets server limitations.
       1. Example: The Corp installs a card in the root of a server with a rezzed region upgrade. The new card cannot also be a region upgrade (unless the old one is trashed as part of the installation), as per section 3.6.5. They do not reveal the installed card to verify this.
    3. c.linkPlayers are required to reveal an installed card to verify any other requirements imposed by the ability that installs the card.
       1. Example: The Corp triggers the ability on Ob Superheavy Logistics by trashing a card with printed rez cost 5. They search R&D for Archer and install it, but decline to pay the additional cost to rez Archer. Since the ability requires the installed card to have printed rez cost 4, and the card is not otherwise visible to the Runner at any point in this process, the Corp must reveal Archer to verify that the installation is legal.
    4. d.linkSome abilities "install and rez" 1 or more cards. If the player resolving an "install and rez" effect is allowed to choose a card that they are unable to rez, or if the installed card has an additional cost to rez that the player declines to pay (see rule 1.16.4c), the player must reveal the installed card, regardless of whether other restrictions apply.
       1. Example: The Corp plays Trust Operation and installs an agenda from Archives with its "install and rez" effect. Since agendas cannot be rezzed, the Corp must reveal the installed agenda.
       2. Example: The Corp plays Ad Blitz. Since the "install and rez" effect on this card stipulates "if able", the Corp cannot choose to install cards they are unable to rez, nor can they decline additional costs if any apply.
14. 8.5.14.linkSome abilities install cards to a specific location. If an ability specifies a destination that is invalid or cannot be identified, no installation can take place.
    1. Example: The Corp uses Nanisivik Grid to resolve the first subroutine on a copy of Brân 1.0 in Archives. This subroutine attempts to install ice "directly inward" from Brân 1.0, but this copy of Brân 1.0 is not protecting a server and therefore does not have a position from which "directly inward" can be evaluated. There is no legal way to install a card as directed, so the subroutine will have no effect.
15. 8.5.15.linkSteps of Installing a Card
    1. a.linkPlace the card into the play area with the same faceup or facedown status it will have when the installation is complete. It is not yet installed or active.
    2. b.linkChoose and declare the install destination appropriate to the card that will be installed, including any host relationships, if applicable.
    3. c.linkTrash like cards as described in section 8.5.6.
    4. d.linkPay the appropriate install cost. (The cost-paid checkpoint then occurs.)
    5. e.linkIf the card is to be the first card in the root of or protecting a new remote server, that server is created. Move the card to the chosen install location. It becomes installed. If the card is faceup, it becomes active.
    6. f.linkAny "When installed..." abilities that apply to the installation meet their trigger conditions, including those on the installed card, and the install effect is complete.