Gagarin Baloney 0.5

falseidol 436

I wouldn't normally publish a deck still in its infancy, but I wanted to get it out there and contribute to the Gagarin conversation as well as get a bit of feedback while I continue to hone the deck.

The deck uses Dedicated Response Team and Eliza's Toybox as punishment for leaving remote servers unchecked, while Gagarin and Paywall Implementation act as a pop-up window over all my servers. Usually its best to leave the PADs facedown until the runner checks them, same with Jackson. When you decide to score, they may not have the time to check them all before running, which makes blowing through a Data Raven a huge risk. The Toshiyuki is a goof I'm experimenting with as I found 3x Eliza's a little overkill, but you just toss him down and use him as a bit of extra tax (they have to pay to access whatever you throw down) and you can keep doing that until you run out of cards to swap. 2x Lotus field or an ASH would be very solid uses of that influence as well.

ICE package is still a rough draft, constellation ICE was to have a higher presence of Data Raven, with Orion and Wormhole firing the DR subroutine in a pinch, as well as being good targets for Eliza's Toybox. I didn't really have space for constellation protocol though, which makes them sort of a sore thumb and IDK if I might just be better off with run-of-the-mill big ICE like Hadrian's Wall. I'm playing Firmware Updates over Hostile Takeover, which acts like a mini PriReq, and this deck hates BP, as even just 1 blanks your ID ability. Builder felt awkward, but being able to move around a code gate is great against Kit, so it might go back in I'm not sure.

0 comments