RESCUE MODE
Introduction
In Rescue Mode, Earth’s most powerful corporations have
launched a world-wide offensive on the 404th, capturing many
of the group’s most important members and holding them in
the state-of-the-art security rooms found in the corporations’
headquarters. Your team is a cell of the last free bots in the
organization. You must work together to free your compatriots
from their imprisonment, sabotage the corporations, and steal
back some of the advanced programming that was stolen from
your mind during the Code Wipe.
Rescue Mode allows you to chain multiple burncycle
missions together for a high-stakes challenge across multiple
corporations. As your team progresses through the missions,
you will gain more team-building options and unlock powerful
new burncycle chips, but you will also face new hardships that
will only grow more challenging as more missions unfold.
We do not recommend Rescue Mode for players who are brand
new to the game.
First Mission Setup
Print the Rescue Mode Tracker, available as a PDF at
chiptheorygames.com/support. An example of this tracker can
also be found later in this document.
Set up Rescue Mode as a normal game, with the following
alterations:
Choosing Your Mission
Before the first mission in Rescue Mode, randomly select a
1-floor, 2-floor and 3-floor mission from each of the corporations
you own.
This means you will have 9 missions in total with the
base game and 3 additional missions for each corporation
expansion you own.
As a team, decide which corporation you will go up against
first. Its 3-floor mission will be your first mission. You can openly
look at all of the mission cards when deciding which corporation
to start with.
Choosing Your Bots and Placing Captives
Randomly deal out bot cards equal to player count +2, in view
of all players.
As a team, decide which of these bots will be your command
module for the first mission.
Each player will then select one of the remaining bots as their
agent for this mission.
Keep the leftover bot in a spot near your play area. This spot
is designated as your bot reserve and is where you will keep bots
that you have rescued but are not currently being played.
Place the rest of the bot cards in another designated area.
These are captured bots that will join your bot reserve as you
rescue them.
Look at the floorplan to see if the security room is present on
the current floor (which should already be set up). If so:
Randomly select a captured bot and place its bot chip on
the space in the security room with its shut down side
up.
Changing Floors During Gameplay
Each time you change floors, if the security room exists on
the floor, add a captured bot to the security room as described
above.
Gameplay
Prior to starting each game, fill out the “Before” section of the
Rescue Mode Tracker.
Your team will play the mission as normal, with the exception
that on any floor containing a captured bot, your team has the
option to rescue it.
To rescue a bot, the security room must be surveilled and then
cleared of all security units and terminals.
As soon as the security room has been surveilled and has no
terminals or security units in it, the bot is rescued, even if you
later lose the mission. Remove its chip from the security room
and place it in your bot reserve immediately.
End of the Mission
Win or lose, use the Rescue Mode Tracker to record your game
and determine how many points you earned for the mission.
If you won the mission:
Gain 2 points, plus 1 point for each bot rescued.
Points will be used later for reducing threat between
games.
Record your current threat as your ending threat.
Decide if your command module will be resting –
meaning it will not be participating in the next mission.
If it does rest, choose one of the following resting tasks
for your command module to complete, and record
this on the Tracker. The next time this bot is played,
whether as a command module or as an agent, the
team will gain the corresponding benefit.
1
 Archive – Immediately: Choose any equipment
or mod currently on any bot, and record its name
on the Tracker. When next played: At the end of
setup, any bot on the team may start with the
recorded equipment or mod (uninstalled).
Recon – When next played: At the end of setup,
any bot on the team may surveil up to 2 rooms.
Scavenge – When next played: At the end
of setup, any bot on the team may draw three
equipment cards and choose one to keep.
Assign – When next played: During initial guard
setup, for one hallway guard of the team’s choice,
the team may choose a guard of the appropriate
level from supply instead of randomly drawing it.
Charge – When next played: At the end of
setup, any bot on the team may gain up to 2 power.
If you lost the mission:
Set your points to 0 (even if bots were rescued).
Record your ending threat as 0.
Place your command module in the captured bots
area. It is no longer part of your team. If your team no
longer has bots equal to player count +1, you have
failed Rescue Mode, as your team no longer has enough
members to embark on another rescue mission.
Place all remaining played and rescued bots in the bot reserve.
If you finished the third and final mission of a corporation and
won at least 2 of the 3 missions for that corporation, you have
gained valuable intel to help you with the rest of your campaign!
Take the CEO chip for the corporation you just completed, flip
it over, and add it to the chip tray with the rest of your action
chips. This is now an action chip that you have access to for the
remainder of the campaign.
Setup for Subsequent Missions
Each mission played in Rescue Mode is treated as a new game.
You start from scratch, with the following modifications made.
Choosing Your Mission
After playing through the 3-floor mission of a corporation, you
will then play its 2-floor mission, followed by its 1-floor mission.
After completing a corporation by playing through all 3 of its
missions, decide as a team which corporation to take on next,
and work through its missions starting with its 3-floor mission.
Choosing Your Bots and Placing Captives
As a team, decide which bot from the reserve will be your
command module.
You cannot select the previously played command
module if it is resting.
2
Each player will then select one of the remaining bots as their
agent for this mission. Players can choose the same agent as
previously played or select a different one. As more bots are
rescued, players will have more command module and agent
options to choose from!
Again, the previously played command module cannot
be selected if the team decided to rest it.
Check your Tracker to see if any bot on this mission has a
resting benefit that has not been used yet. If so, carry it out during
the appropriate time during setup. Cross out the benefit on your
tracker so you know it was used. It is possible to have multiple
bots with benefits on the same mission. The team determines
the order of any benefits that would resolve at the same time.
Remember to add a captured bot to the space of the
security room if it is present on the floorplan.
If you have managed to rescue all captured bots, skip this
step.
Creating the Burncycle
Create the burncycle as normal, also adding any CEO chips
that you have collected to the draw bag. Remove a general action
chip for each CEO chip added so that the number of chips in the
draw bag still equals the number of burncycle slots you have.
If you have more CEO chips than can be included to fill the
burncycle, choose which CEO chips to include. Remember
that you must always still include the captain action chip in
the burncycle.
Example: If your burncycle has 2 active slots and you
have collected 2 base game CEO chips, your draw bag will
consist of the captain action chip and 1 CEO chip of your
choice, with the remaining CEO chip and all general action
chips remaining in the supply.
Do the same each time the burncycle is rebooted.
Setting Threat
By default, if you won the previous mission, your threat will
start where it finished for the previous mission. However, you do
have a way to reduce your starting threat – by spending points.
For every 1 point spent, your starting threat can be
reduced by 5.
After spending points, record your starting threat on the
Tracker as well as your new point total. If the mission you
are playing sets threat to any particular number, ignore that
part of the mission’s setup.
Do not carry out any threat events that are already past
your starting threat. Any escalations that are passed are
active as normal, however.
If you lost the previous mission, your threat should already be
set to 0, and you should have no points to spend. Again, ignore
any part of the mission’s setup that sets threat above 0.
End of Rescue Mode
If all of the selected missions for each corporation completed
without failing by losing too many bots, you have successfully
finished Rescue Mode! Congratulations!

CEO Chips in Your Burncycle and Ignacia Torres – Salida

Reserve
Each CEO chip has a different function when you take an action
on it in the burncycle. Certain bot abilities and missions could
result in having these chips in reserves as well.
Action Step: Gain 1 power when taking any action on this chip
in the burncycle.
Network Step: Gain 1 power and move 1 node on the network.
In Your Reserve: Use to alter the burncycle, or discard as a free
action to gain 1 power.

Bo Zeffries – NeedChain

Action Step: Both physical and utility actions are optimized
when taken on this chip. Moving to this chip in the burncycle
during a keypad action will fulfill all physical and utility inputs
on the keypad.
Network Step: Choose whether to use this as a physical or utility
chip when using this chip to move on the network.
In Your Reserve: Use to alter the burncycle, or discard to resolve
all physical and utility inputs on a keypad.
Latipah Loong – BioDefend (Expansion)
Action Step: Gain 1 additional AP (for a total of +3 AP) when
taking an optimized physical action on this chip. Moving to
this chip in the burncycle during a keypad action will fulfill all
physical inputs on the keypad.
Network Step: Use as a physical chip when moving on the
network on this chip in the burncycle, and optionally move 1
additional node if you would land on a physical node.

In Your Reserve: Use to alter the burncycle, or discard to resolve

all physical inputs on a keypad.

Abeo – Ocularity

Action Step: Both tech and utility actions are optimized when
taken on this chip. Moving to this chip in the burncycle during a
keypad action will fulfill all tech and utility inputs on the keypad.

Network Step: Choose whether to use this as a tech or utility

chip when moving on the network on this chip in the burncycle.

In Your Reserve: Use to alter the burncycle, or discard to resolve

all tech and utility inputs on a keypad.

3
 Rescue Mode Tracker Example
Mission 1 – Before

Mission Command Threat Points New Point Starting

Corporation # of Floors (Before (Before Points Spent
Name Module Adjusted) Adjusted) Total Threat

Megamarket
NC 3 Transmitter 0 0 0 0 0
Sweep

Mission 1 – After

# Bots Points Earned Ending Threat Ending Points CM’s Task Equip/Mod
Won or Lost? CM Rested? (if task is Archive)
Rescued (if rested)

Mod –
Won 1 3 19 3 Yes Archive
Safehack

This team has just successfully finished the NeedChain mission Operation: Megamarket Sweep. They rescued one bot and won,
giving them 3 points total. They finished with 19 threat. They decide to rest Transmitter, choosing the Archive option. This means
that the team cannot play Transmitter in the next mission, but the next time Transmitter is played, a bot on the team will start the
game with the Safehack Mod.

Mission 2 – Before

Mission Command Threat Points New Point Starting

Corporation # of Floors (Before (Before Points Spent
Name Module Adjusted) Adjusted) Total Threat

Ruxpin
NC 2 Access 19 3 4 1 9
Rampage

Going into their next mission, Operation: Ruxpin Rampage, the team decides to spend 2 points to reduce the threat to 9 for the
start of that mission. This also means that the threat events Activity Tracking and Remote Spindown will not happen, since they are
already passed (though the escalation Monitor Protocol is immediately in effect).

Mission 2 – After

# Bots Points Earned Ending Threat Ending Points CM’s Task Equip/Mod
Won or Lost? CM Rested? (if task is Archive)
Rescued (if rested)

Lost 1 0 0 0 N/A N/A N/A

The team was unsuccessful on their second mission, losing to threat reaching 26. They did, however, successfully rescue a bot, which
they still get to keep in their bot reserve. Their command module, Access, is captured, so she is placed with the other captured bots.

4
Mission 3 – Before

Mission Command Threat Points New Point Starting

Corporation # of Floors (Before (Before Points Spent
Name Module Adjusted) Adjusted) Total Threat

Terminal
NC 1 Interface 0 0 0 0 0
Viscosity

Going into their third mission, the team has 0 threat and 0 points. Transmitter is all charged up and ready to rejoin the team. This
time, Transmitter is being used as an agent instead of the command module, but this still gives the team its resting benefit, so any
agent will start the game with the Safehack mod uninstalled in their inventory. Make sure to cross out the Archive task recorded in
Mission 1 to show this benefit is now used.

Mission 3 – After

# Bots Points Earned Ending Threat Ending Points CM’s Task Equip/Mod
Won or Lost? CM Rested? (if task is Archive)
Rescued (if rested)

Won 1 3 21 3 Yes Charge N/A

The team succeeded at their final NeedChain mission, Operation: Terminal Viscosity! They will go into the next corporation with 3
points, 21 threat, and 3 bots rescued (though a command module was captured in the process). Since they won 2 out of 3 of the
NeedChain missions, they earned Bo Zeffries’s CEO chip and will place it with their action chips to be used for the remainder of the
campaign! The team can now choose which corporation they will take on next!

5
Mission – Before

Mission Command Threat Points New Point Starting

Corporation # of Floors (Before (Before Points Spent
Name Module Adjusted) Adjusted) Total Threat

Mission – After

# Bots Points Earned Ending Threat Ending Points CM’s Task Equip/Mod
Won or Lost? CM Rested? (if task is Archive)
Rescued (if rested)

Mission – Before

Mission Command Threat Points New Point Starting

Corporation # of Floors (Before (Before Points Spent
Name Module Adjusted) Adjusted) Total Threat

Mission – After

# Bots Points Earned Ending Threat Ending Points CM’s Task Equip/Mod
Won or Lost? CM Rested? (if task is Archive)
Rescued (if rested)

Mission – Before

Mission Command Threat Points New Point Starting

Corporation # of Floors (Before (Before Points Spent
Name Module Adjusted) Adjusted) Total Threat

Mission – After

# Bots Points Earned Ending Threat Ending Points CM’s Task Equip/Mod
Won or Lost? CM Rested? (if task is Archive)
Rescued (if rested)