Posted to r.g.f.c. on Apr. 18
Although I realize the game is not yet into general distribution I'd like to start discussion on using the Netrunner CCG as a supplement/replacement for the current netrunning rules for CP2020. Quick Overview: ------------------------------------ There are two sides and two sets of cards in the game. One is the Corp who represents a corporation's assets placed on the net. The other is a Runner, representing the netrunner we all know, love, and (rarely) play in the RPG. The game is won by the Corp by completing agendas or killing the Runner. Runner wins by stealing agendas before they come about by making runs on data forts. The Corp has these types of cards: * Agendas - Black and Grey Ops that will gain the corporation power. * Nodes - Corporate projects not as important as Agendas. * Upgrades - Additions to the inner data fort (i.e. last line of defense) * Operations - Offensive attacks of the corporation, can be net or reality based. * ICE - Three types: 1)Sentry 2)Walls 3)Code Gates The Runner has these: * Programs - Everything from ICEbreakers to shields to scanners. * Hardware - Decks and deck add-ons. * Resources - Contacts and back doors to make runs easier. * Preps - One shot cards to boost a run (like Operations for the Corp). Gameplay consists of using your resources (called a bit pool) to build up your dataforts or netrunning gear then the Runner makes runs on the forts, defeating each layer of ICE inturn or accepting its affects and trying to get to the node or agenda underneath. First Impressions: --------------------------------------- At this point I can see Netrunner being easily used for runs on a corp's datafort. Runner vs. Runner or Sysop vs. Runner might not be so easy. I'll have to see more cards. The game of Netrunner sims a campaign of multiple runs against a corporation. The whole underlying turn structure should be throuwn out and just concentrate on the point when the Runner decides to make the run. All card accessibility should be conrtolled by the GM and roleplaying. Either buy the your programs and hardware, or steal it, not get it from a random draw. The Runner should get to decide which programs to load for the run. Standard decks have 4MU which is okay since it is _rare_ for a program to take more up more than one. The datafort construction should be layed out by the GM including ICE layers deemed appropriate. Runs should only be made on dataforts. Runs on R&D, the Archive, or HQ should be simulated by larger regular dataforts as the campaign structure is not being used. All cards used in the run should be on the table at the start of the run. Nothing in the hands to bring into play later, this should have already been taken care of by the GM or roleplaying. For bit pools (used by the Corp to rez layers of ICE and by the Runner to strengthen and activate programs) I'm leaning towards INT+Interface for the Runner and a predetermined amount for the Corp (I'd assume enough to rez all ICE except in special circumstances... perhaps a random amount). The run should be done as in the rules. Tags would have roleplaying consequences. Meat damamge should probably be handled on a 2 for 1 basis. (i.e. 1 Meat damage = 2 hit points). Brain damage would be a 1 for 1 INT loss. Net damage would be tricky... nothing comes to mind right off the top of my head. Summary: --------------------------------- I realize things are a little sketchy and disorganized at the point, but I wanted to get things starting as soon as I could. Please feel free to comment/add/critisize/whatever and keep this thread running. I'll be watching and posting summaries of any concensus that we reach to the CP2020 Web Archive in the Essays and Dissertations section under "The Netrunner Project". -Paul Tobia Manager of the CP2020 Web Archive http://falcon.cc.ukans.edu
Get your own Free Home Page