Princess of the Fire Pit Balance Repost [Written]

[Ninjask Is Bae]

So, this seems to be an infamous example of a bad card in Advanced. I'm afraid I might have neutered it completely. Of course any feedback is welcome. Harsh feedback is apreciated the most.

 

Princess of the Fire Pit

Xyz l Rank-2 l Effect l FIRE

2 level-2 monsters

If this card is Xyz Summoned while you control other monsters than "Princess of the Fire Pit"; banish 1 monster on your side of the field.

Once per turn, during either player's turn, if a monster is summoned; negate that summon and attach it to this card as Xyz-Material.

If this card would be sent to the graveyard, banish it and all Xyz-Materials attached to it instead.

300 ATK / 1000 DEF

 

So, the second two effects were already present on the old card with the exception of it not banishing itself on the original. I added that so it couldn't be brought back. Seeing as it doesn't really care about having material attached or not.

I added the first effect so you couldn't lock your opponent as hard like the old card could. And to make it a little more situational than it already was. The old one just denied them their main phace-1 at the least. This one denies them their main phace 1 in certain situations.

This would be a Rank-2 option after you just field wiped now. Whereas before it was just. "What play should I make? Oh yeah, Princess of the Fire Pit is litterally the best thing two level-2 monsters can do."

 

Edit: Now negates the summon in addition to eating it but only does so once per turn. Made the destruction effect less harch.

[Flash Flyer - Sakura]

[spoiler=Background notes]

Yeah, that card got several vets involved [including Black] and some users having a spamfest about how we're too harsh on members wanting a review. I think I linked the original thread in the Casual design guide, or you can find it yourself through the search function. Before you ask "then why didn't you do anything about it?", I was not a moderator at the time this was made; hence why Yin had to cut it off.

 

(Those of you who are curious can see everything for yourself)

 

 

 

====

That being said, the second effect alone warranted the criticism that the veteran members at the time gave about it, and that's just eating whatever monster that came on the field; yes, even your own. While it is true that you made it banish your other 'mons when summoned (and itself when leaving), I honestly don't think this card could be redone without completely overhauling it. Let's say it's a much tamer version, but the concept of it alone is still going to raise concern (well, unless you happen to already have a setup board before this comes out and eats everything).

 

tl;dr, this isn't a card that should've been redone, given its nature.

[Ninjask Is Bae]

I guess I already understood the fact is card was kind of unsavable. I just wanted to check how to make the card. Idk. Less horrid.

I honestly don't think the card would be OP in this state. It would just be a horrid card to play against in some situations.

[Dokutah]

from the first 2 effects alone this card is cannot be redeemed. its a non-targeting and non-destruction removal that doesn't let your opponent save any card he have once this dropped successfully (unlike Struggling Battle). Rank 2 may not as popular as 3 or 4 but the card pool can pull this card with so much ease. closest to meta we get probably Paleo- (i mean) Burgessstoma, which actually have no problem with this card double-edged removal since Burgessstoma is unaffected by other monster effect. this card weak stat is also barely a problem since once you wipe clean the field when it was summoned any monster that should beat over it is get attached to this card. granted though, this card doesn't have any immunity to further secure itself, but since this card doesn't affect any of your back-row with either its effect you can just secure this monster with some floodgates and create an annoying one-sided situation.  

[Flash Flyer - Sakura]

I think you misread the first effect there; it only banishes other monsters YOU control; not the opponent's stuff. If this were the case and was a BRD-style nuke, it'd be a lot more irritating than the original version. So basically, once this comes on board, you're stuck with a 300 / 1000 monster and nothing else but backrow.

[Dokutah]

ah my bad.

 

obviously WAY less of a threat now. make it less desirable in most Rank 2 deck barring Burgesstoma (still with the same reasoning).

[Darj]

Just give it an OPT or hard OPT clause to the second effect, really. It would still be threatening enough IMO, and with the first effect as drawback plus the low stats it shouldn't be overwhelming. Heck, you could even be a bit more forgiving with the first effect and/or stats after said change.

[Flash Flyer - Sakura]

Think a lot of us would be fine with a [hard] OPT on it; would still be a pain to deal with (for slower Decks that can't field as much monster advantage), but least you can bait this card's effect when it steals something, and summon something later.

 

Looking back at the older card, I think someone suggested it and TC just ignored that altogether, but will need to look at it again (because the thread got toxic after a few posts).

[Darj]

Yeah, also if you destroy the princess before it resolves its effect, your monster will be just fine, since the princess is no longer there to attach your monster and doesn't negate the Summon nor anything, like S.H.Ark. Funnily enough, that makes it vulnerable to Snow Rabbit xD

Not saying that because Snow Rabbit, or counters, exist, means the card is fine, for the record.

 

Off-topic note but I went to read the thread, and I find amusing how it was mentioned that Chalice was not relevant at that time, when nowadays AFAIK it is the most relevant monster effect negation card, while Veiler is coming back on OCG last time I checked.

[Ninjask Is Bae]

Edited the card: Now negates the summon in addition to eating it but only does so once per turn. Made the destruction effect less harch.