Dominion Strategy Forum

Please login or register.

Login with username, password and session length
Pages: [1]

Author Topic: New Death Engine?!?!  (Read 1821 times)

0 Members and 1 Guest are viewing this topic.

Wolphmaniac

  • Golem
  • ****
  • Offline Offline
  • Posts: 198
  • Shuffle iT Username: DividedSpy
  • Respect: +279
    • View Profile
New Death Engine?!?!
« on: March 02, 2012, 12:17:20 am »
0

I've seen stuff about the glitch/death engine of King's Court/King's Court/Goons/Masquerade which forces your opponent to hand over his entire deck...but I've never heard anything about this next engine that I just stumbled into, and it did the same thing.  (And' it's easier to assemble.) 

The engine is: King's Court/Masquerade/Farming Village/Bishop.

First you play the FV.  (Having more than one is OK, just play them all to get them out of the way.)  Next, if you have anything else that has come into the hand from FV, trash it with Bishop.  (This is how you hone in on completing the engine...Bishop just keeps trashing whatever you have that isn't part of the engine.)  Finally, you are left with just KC/Masq in your hand, forcing the opponent to hand over three cards.  Trash the first two so you aren't giving any cards back.  On his third card, keep the card so you can play Bishop next turn and have something to trash that isn't your KC or Masq.  (And you get some bonus VP tokens to boot.)

I am pretty sure this engine leaves the opponent absolutely no outs.  Even if he can gain at least 3 cards per turn for a while, he eventually will not be able to.  You will obliterate his entire deck.

Thoughts?  And is this new or has someone found this before?  I haven't seen it anywhere but I certainly haven't read everything there is to read.     

Game log:
http://dominion.isotropic.org/gamelog/201203/01/game-20120301-205427-9d79223e.html

(P.S. Chalkdust Torturer is my other handle.)
Logged

Wolphmaniac

  • Golem
  • ****
  • Offline Offline
  • Posts: 198
  • Shuffle iT Username: DividedSpy
  • Respect: +279
    • View Profile
Re: New Death Engine?!?!
« Reply #1 on: March 02, 2012, 12:24:54 am »
0

It's not quiiiite as effective as KC/KC/Goons/Masq because your opponent still has a 2-card turn to play...but he's going to have to reduce his deck by three cards every turn.  So unless he can end the game on those 2-card turns, he has no outs.
Logged

dondon151

  • 2012 US Champion
  • *
  • Offline Offline
  • Posts: 2522
  • Respect: +1856
    • View Profile
Re: New Death Engine?!?!
« Reply #2 on: March 02, 2012, 12:39:18 am »
0

Generally anything involving KC-Masq is a partial pin, even without forcing the opponent to discard any cards prior to Masq being played.
Logged

blueblimp

  • Margrave
  • *****
  • Offline Offline
  • Posts: 2849
  • Respect: +1560
    • View Profile
Re: New Death Engine?!?!
« Reply #3 on: March 02, 2012, 01:18:50 am »
0

Having played KC-Masq without support once (and I lost) and having it played against me once (and I won), I'm 100% sure that plain KC-Masq is really not very scary. It does force the other player to hurry up and either end the game or break the combo, but breaking the combo is really pretty easy: just hold on to a Masquerade and play that.
Logged

Wolphmaniac

  • Golem
  • ****
  • Offline Offline
  • Posts: 198
  • Shuffle iT Username: DividedSpy
  • Respect: +279
    • View Profile
Re: New Death Engine?!?!
« Reply #4 on: March 02, 2012, 08:14:30 am »
0

breaking the combo is really pretty easy: just hold on to a Masquerade and play that.

That defense is not quite so easy against this engine because this engine can add extra Farming Villages that are both unnecessary to the engine AND don't hurt the engine at the same time.  So even if my opponent did the play-a-Masquerade defense I could just keep passing him my extraneous Farming Villages while I am breaking him down. Right?
Logged

ftl

  • Mountebank
  • *****
  • Offline Offline
  • Posts: 2056
  • Shuffle iT Username: ftl
  • Respect: +1345
    • View Profile
Re: New Death Engine?!?!
« Reply #5 on: March 02, 2012, 09:36:03 am »
+2

Thing is, youre still leaving him with a 2 card hand. That's enough for KC-something. KC lab, or governor, or scrying pool, or hunting party, or maybe golem, let him play on completely normally. KC any cantrip gives you enough cards to start up an engine, at least. KC any gainer or plus buy restores the same number of cards which got destroyed, and might end the game on cheap piles pretty quick. And you're trashing bad cards for him.

 I bet the opponent can set up a counter pin AFTER being pinned himself. And you have obligingly trashed all the filler from your deck, so a single hit on you destroys your pin and your whole deck. Unless you keep around not just one, but many extra villages. Or even then.

I'm sure this can be a good strategy, but it's not as unstoppable as a pin that leaves you at a zero card hand. You have to either catch the opponent off guard, or go over the rest of the kingdom carefully to make sure that it's appropriate and doesn't provide a convenient escape via kc.
« Last Edit: March 02, 2012, 10:01:40 am by ftl »
Logged

Wolphmaniac

  • Golem
  • ****
  • Offline Offline
  • Posts: 198
  • Shuffle iT Username: DividedSpy
  • Respect: +279
    • View Profile
Re: New Death Engine?!?!
« Reply #6 on: March 02, 2012, 10:16:06 am »
0

Well-put ftl.  That all makes sense.  The conditions were right in that game I attached, but the ultimate success of the engine as a pin are definitely condition-reliant.  It CAN be a full pin, but if the opponent sees it coming or if other kingdom conditions apply, then it could also be a partial pin or it could even fail completely.  Best-case scenario is assembling the engine before the opponent gains a King's Court...you're most likely in good shape at that point...but even then, depending on the kingdom, there could be myriad ways that the opponent could play strongly through his 2-card hands.  In a kingdom with no +card action cards available, this engine would probably be a very strong strategy.  Thanks for the feedback!
Logged
Pages: [1]
 

Page created in 0.044 seconds with 20 queries.