TheManaDrain.com
March 18, 2026, 06:38:25 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Search Calendar Login Register  
Pages: [1]
  Print  
Author Topic: triskelion or grim poppet for 2010?  (Read 1531 times)
TheRogue
Basic User
**
Posts: 69



View Profile
« on: July 03, 2009, 08:34:27 pm »

with the new rules about the damage not using the stack, it makes a lot of cards like mogg fanatic and others with good abilities lose some of there effectiveness.

i was thinking how the new rules would make triskelion only be able to fight off threats with toughness lower than its own power it could never under the new rules kill anything bigger than 4 toughness. (if any such threat were to exist that isn't killed through other means)
then i started thinking about grim poppet it enters play small but makes other creatures permanently smaller while it becomes bigger yet it only does -1/-1 counters instead of doing points of damage.

the two server there purpose of hitting for 4 damage, and knocking off small guys like welder, confidant, and various other "nats" the big trade off is triskelion can 3 damage to a player where grim poppet cannot, yet poppet being an artifact can cripple big creatures, and often any substantial target most likely won't be immune to artifact targeting. so in this sense of the creature fighting one can get your last 3 damage through wile the other can negate 3 damage being recieved.

boil it all down is under the new rules for decks like welder survival/slaver/workshop decks and anything else that usually only makes space for 1 triskelion, would it be wise to replace it with grim poppet or keep playing triskelion in that spot despite is losing some possibly crucial functionality.  
Logged

-Bomb Technician- "If i'm running you better be right behind me!"

Got more than magic on your mind. Come swing by the Collaborative pub for Some great posts. The place for Creative writing to Politics and more.
http://www.collaborativepub.com/
zeus-online
Adepts
Basic User
****
Posts: 1807


View Profile
« Reply #1 on: July 04, 2009, 02:23:33 am »

If you're playing welder you could go, shoot twice on whatever, shoot your trisk, weld it back in shoot again! (sort of like..reloading Smile)

Sometimes shooting players or planeswalkers is very relevant. Which is why i'd go with good ol' triskelion or triskelavus.
Logged

The truth is an elephant described by three blind men.
TheRogue
Basic User
**
Posts: 69



View Profile
« Reply #2 on: July 08, 2009, 11:36:14 pm »

you raise a good point about planeswalkers. i'm still forget often that anything that hits a player can hit a planeswalker atleast as far as lighting bolts and other player target abilitys are concerned.

only one i can think of shooting in tezzeret but hes never out when i have trisky out (as of yet hasn't happened.)
Logged

-Bomb Technician- "If i'm running you better be right behind me!"

Got more than magic on your mind. Come swing by the Collaborative pub for Some great posts. The place for Creative writing to Politics and more.
http://www.collaborativepub.com/
TracerBullet
Full Members
Basic User
***
Posts: 577


TracerBullet1000
View Profile Email
« Reply #3 on: July 09, 2009, 05:06:29 am »

you raise a good point about planeswalkers. i'm still forget often that anything that hits a player can hit a planeswalker atleast as far as lighting bolts and other player target abilitys are concerned.

only one i can think of shooting in tezzeret but hes never out when i have trisky out (as of yet hasn't happened.)

Moreover, that it's not a beater unless they have critters to kill is a major minus.  Having played quite a bit of MonoBrown, you'll often rely on a single beater to go all the way, and losing out on 2-3 of those in your deck is simply too much to lose.
Logged

The room is on fire, and she's fixin' her hair...
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.248 seconds with 20 queries.