An install-advance bluff is not simply “put down a trap and hope the Runner hits it.” The stronger play is to create a remote that could reasonably contain an agenda, then make the Runner choose between spending resources to challenge it and giving the Corp a possible scoring window.
That uncertainty is valuable even when the Runner guesses correctly. A run can consume clicks, credits, cards, and information. Declining to run can give the Corp time to score, develop its board, or make the next remote harder to interpret. The bluff works by forcing a decision whose alternatives both carry opportunity costs.
What install-advance represents
Corp cards are normally installed facedown. Agendas, assets, and upgrades in a remote server’s root share the same vertical orientation, and the rules require the Corp to position cards so the Runner cannot identify a root card’s type from its placement. A remote root can contain one agenda or one asset, plus any number of upgrades. The Netrunner Comprehensive Rules provides the exact structure and installation rules.
The Corp may always advance an agenda. A non-agenda can be advanced only when its card text permits that, including while the card is unrezzed. The facedown advanced card therefore represents a limited but strategically important range: an agenda, an advanceable asset, or occasionally another legal advanceable card supported by the current card pool.
The basic install-advance line costs two clicks and one credit. Install-advance-advance consumes the Corp’s normal three-click action phase and costs two credits. Scoring itself costs no click once an agenda has enough advancement counters, although the Corp may choose not to score immediately.
That click math shapes what the Runner should believe. Without another effect, a requirement change, or an existing counter, the Corp cannot install a three-advancement agenda and give it all three ordinary advances during the same action phase. Effects that place advancement counters can change the calculation because placing a counter is distinct from taking the advance action.
A credible bluff tells a consistent story
A facedown card with a counter is technically ambiguous, but ambiguity alone does not make it persuasive. The board must support the story that the Corp wants the Runner to believe.
Suppose the Corp installs behind two pieces of ice and advances once. If the Corp has enough credits to rez that ice and has spent previous turns preparing the server, the card looks like a serious scoring attempt. If the Corp is nearly broke and the Runner can cross both pieces cheaply, the same counter may look more like bait—or simply a scoring attempt made from a weak position.
Before committing to the line, the Corp should ask:
- If this were an agenda, would advancing it now fit my scoring plan?
- Can I pay for the ice protecting the remote, or am I representing defenses I cannot afford?
- What does the Runner lose by checking: credits, clicks, cards, or the ability to pressure a central server?
- What happens if the Runner calls the bluff immediately?
- Will this line make a later real agenda easier to score, even if the current card is exposed?
The best bluff usually resembles a normal line from the deck. A remote becomes suspicious when the Corp suddenly protects and advances cards in ways that do not match its economy, previous decisions, or likely agenda requirements.
The card is only half of the bluff
A credible remote also needs credible ice. The Runner approaches and passes installed ice one piece at a time before reaching the root. Ice remains horizontal while root cards are vertical, and installed cards cannot simply be rearranged to obscure their order. For a fuller walkthrough of that sequence, see how runs, ice, and access work.
The Corp does not necessarily need an impenetrable server. It needs a server whose cost creates the desired decision. A taxing remote may make the Runner postpone a check. A dangerous access effect may make running with a small hand risky. A cheap-looking server can invite a run when the Corp actively wants the installed card accessed.
Urtica Cipher illustrates the last case. It is an advanceable asset whose access effect deals two net damage plus one additional net damage for each hosted advancement counter. The important lesson is broader than one card: advancement can increase both the apparent value of a remote and the consequences of checking it.
How the Runner should read an advanced remote
The Runner’s job is not to name the facedown card with certainty. The useful question is whether running now has better expected value than waiting.
A successful run on a remote breaches the server and accesses every card in its root. Accessed agendas are stolen, while accessed assets and upgrades can generally be trashed by paying their trash costs. That means “it might be a trap” is not a complete reason to stay away. The Runner must compare the possible agenda points or valuable trash against the cost and danger of reaching the root.
Evaluate four factors before committing:
- Reachability: Can you pass the ice with the breakers and credits available now?
- Consequences: Can your grip, credits, and board absorb plausible access effects and trash costs?
- Urgency: Could the Corp score the card next turn, or is there time to improve your position first?
- Alternatives: Would pressure on HQ, R&D, or Archives reveal more or punish the Corp for spending clicks and credits on the remote?
A run can still be useful without stealing an agenda. It may force ice rezzes, reveal the server’s real cost, expose an asset, or show that the Corp cannot defend what it represented. That information can make the next remote easier to judge. Conversely, repeatedly checking every advanced card can let the Corp control the Runner’s tempo with inexpensive threats.
Use uncertainty to create a scoring window
The strategic purpose of bluffing is not to win a guessing contest. It is to create a window in which the Runner cannot contest every relevant server effectively. Null Signal’s Corp learning guide frames remote scoring around finding or creating exactly that kind of window.
Sometimes the bluff succeeds because the Runner stays out and the Corp gains time. Sometimes it succeeds because the Runner spends a full turn and most of a credit pool checking an asset. Sometimes the Runner calls correctly, but the Corp learns what defenses the Runner can currently defeat. Each result changes the information and tempo available for the next scoring attempt.
Treat install-advance as a context-dependent tool, not a ritual. Advance a bluff when its story fits your deck, your economy can support the representation, and the Runner faces a meaningful cost for checking. When those pieces align, the facedown card matters less than the decision it forces.