Page 1 of 1

[fixed/closed]Firestorm Phoenix can be cast the turn it dies

PostPosted: 03 Oct 2014, 01:03
by Nexhro
Describe the Bug:
When Firestorm Phoenix is returned to its owner's hand via its triggered ability, it can be cast during that turn.
When it is returned to hand this way, a blood counter is put on it which will remain on it for as long as Phoenix is in its owner's hand

Which card did behave improperly ?
Firestorm Phoenix

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
CoRM15 mini3, duel

What exactly should be the correct behavior/interaction ?
When Firestorm Phoenix is returned to its owner's hand via its triggered ability, it can't be cast until its owner's next turn.

Are any other cards possibly affected by this bug ?
-

Re: [confirmed]Firestorm Phoenix can be cast the turn it die

PostPosted: 16 Oct 2014, 13:09
by Gargaroz
Fixed in e37cfb4

Re: [fixed]Firestorm Phoenix can be cast the turn it dies

PostPosted: 21 Oct 2014, 23:11
by Nexhro
As of CoRM15 mini5, a legacy effect card is put onto the battlefield when Phoenix dies.
Other than that, its behavior seems to be almost identical to that mentioned in the initial report. It can still be casz the turn it dies and still gets the blood counter once it has been returned to hand. The blood counter now remains on it when it's on the battlefield, though.

Re: [still bugged]Firestorm Phoenix can be cast the turn it

PostPosted: 10 Nov 2014, 02:00
by Gargaroz
Fixed & tested in eb08e6b, plus fixed bad valued in "ct_all".

Re: [still bugged]Firestorm Phoenix can be cast the turn it

PostPosted: 01 Dec 2014, 05:14
by BAgate
This might be an implementation thing, but while the card works as intended there are 2 strange items.

1) a blood counter gets put on the card in your hand until your next turn.

2) a legacy card gets created, it says processing Firestorm Phoenix, then that legacy card is destroyed and another is created.

Is all that intentional?

Re: [still bugged]Firestorm Phoenix can be cast the turn it

PostPosted: 05 Dec 2014, 16:44
by Gargaroz
1) Yes, it's intentional
2) That second legacy should be invisible. Done it in 887b74c