Operation 4: Digital Download
Intel
As a world completely manifest in data, the Aehterium offers an endless supply of information for those users that are willing to find and take it. Inevitably, the boundless data caches that are spread across the Aehterium attract attention for those wishing to store sensitive information.
Server Setup
The Server consists of 1 large, 2 medium, and 4 small schemas.
Deployment
As normal
Objective
Primary:
Full completion – Download the data cahce and escape off the server with it.
Partial completion – Control the data cache, but do not escape off the Server with it.
Secondary:
1. Have at least 1 Function in play at the end of the game.
2. Delete all enemy Functions.
Endgame:
Both players have completed 5 re-calibrations
Victory Conditions
The player with the most victory points at endgame wins
Victory Points
Primary Objective – full completion = 7 vp
Primary Objective – partial completion = 5 vp
Secondary Objective = 3 vp each
Control the Node = 2vp
control pylons = 1 vp
Special Rules
Data Cache
The data cache starts within the Node. To download the data, a player must have a model adjacent to the Node at the start of its activation. the model must then spend its entire activation doing nothing while it downloads the data. The model may not spend CS in any way, may not make any attacks, may no use .EXES, may not change facing, and may not use RAM for overclocking.
If for any reason, the downloading model is moved and/or is no longer adjacent to the Node, then the download stops immediately and must be attempted again in a later activation. Once downloaded, the downloading model gains immediate control of the data cache. Place the data cache token on the controlling model’s Data Card. As long as this model is in play, it is carrying the data.
If the model is deleted, then the data cache is placed in any square that the carrying model was occupying. Once placed back on the Serve, any model is allowed to pick up the data cache by moving into an adjacent square and spending 2 cs. The square with the data cache is considered to be occupied. It does not block LOS.
To escape the Server, the model carrying the data cache must be adjacent to a friendly controlled pylon (Not the node) and spend 3 cs to leave the server.
Subroutines Inferior:
Subroutines cannot attempt to download or carry the data cache at any time.