|
Author
|
Topic: AQ Jumpluff: Nitty-Gritty
|
HollowDragonMaster
Member # 118182
|
posted June 03, 2003 08:02 AM
Okay, maybe I should have made just on topic on this critter instead of other card-effects and powers.
All rulings have had me a bit confused of what can damge an AQ Jumpluff with a damage counter on it and it's Poke-Body. I read that Murkrow CAN damage it, but Umbreon can't (as Active) for example.
Honestly, I can't sit hear and fear Jumpluff all my life and I need options to fight against it. Jumpfluff's power seems so direct that the opponent can flip for "anything" you try to throw at it Active or Benched - and status effects don't appear to be able to turn its Power off.
I know there are Jumpluff lovers out there and I agree it's a good card, but I need to know what options I have - if any. Thanks for your inputs.
Registered: Dec 2002
| IP: Logged
|
|
WizPog_BJJ
Member # 113374
|
posted June 03, 2003 08:22 AM
Um Umbreon's Feint Attack, like all Feint Attacks, goes through an Active Jumpluff. A Benched Jumpluff (with active Poké-Body) would get to flip for it's Power to see if it's damaged (except when attacked by Aq Houndour's Feint Attack as nothing stops that attack).
There was a post about Fluff when it first came out. If you go back you will see the debate it caused.
Fluff only can prevent damage and effects on Jumpluff, not your Bench. So Jumpluff can prevent the damage done from Tyranitar's Trample to itself, but Trample can still damage the Bench. Dark Tyranitar can still Discard cards from the top of your deck, even if it cannot damage Jumpluff. A Rapid Spin attack can send the attacker to the attacker's Bench, while Jumpluff takes no damage and remains Active.
--------------------
The Compendium
WizPog Posting Rules
Wizards.Community Code of Conduct
From: Warwick RI USA | Registered: Nov 2002
| IP: Logged
|
|
HollowDragonMaster
Member # 118182
|
posted June 03, 2003 08:42 AM
Okay - I'll try to find it. You have been a great help today. Thanks.
Registered: Dec 2002
| IP: Logged
|
|
|
Printer-friendly view of this topic
