Page 1 of 1

[fixed/closed]Turn // Burn

PostPosted: 20 Nov 2013, 17:12
by Aswan jaguar
Describe the Bug:
Turn // Burn
1- the Turn if you have no {R} mana untapped costs only {U}. It costs correctly Only if you have no {R} mana untapped ***not confirmed-fixed
2- the Turn,makes 0/1 but doesn't in fact turn creature to Red. ***confirmedfixed by korath
3- the Turn doesn't let creature affected turn back to it's type until end of game(few turns checked)Remains a Weird. :D ***unconfirmed (in my test with your savegame creature type did not change at all, but legacy card disappeared and P/T returned to normal when they should)fixed by korath
4- Burn if you don't have 3 mana available you can't cast Burn. ***confirmed

Which card did behave improperly ?
Turn // Burn

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
onslaught.v2

What exactly should be the correct behavior/interaction ?
1- Turn costs {2} {U} all the time.
2- the Turn,makes creature Red.
3- effect of Turn is until end of turn then creature gains it's original types and colour.
4- Burn costs {1} {R} all the time.
Are any other cards possibly affected by this bug ?

Re: [partially confirmed]Turn // Burn

PostPosted: 21 Nov 2013, 21:50
by Korath
I've already fixed #2 and #3 (only) in the process of doing something else. (The easiest way to confirm #3 is with a "choose a subtype from a card in play" effect like Adaptive Automaton. Things like Lord of Atlantis work too, depending on the card's normal subtypes. The legacy card's not a good indicator.)

Turn // Burn also shows up as blue (only) while in hand for me.

Re: [partially confirmed]Turn // Burn

PostPosted: 22 Nov 2013, 01:26
by BAgate
never thought of that method korath, thx.

Re: [partially confirmed]Turn // Burn

PostPosted: 22 Nov 2013, 06:21
by Aswan jaguar
Stassy you saw that it was onslaught.v2 right?

Re: [partially confirmed]Turn // Burn

PostPosted: 22 Nov 2013, 06:28
by stassy
Well, it doesn't matter since the check/fix is at PTT, right? Or am I missing something else...

Re: [partially confirmed]Turn // Burn

PostPosted: 22 Nov 2013, 07:59
by BAgate
I didn't think it mattered. If the errors are still there, they still need to be fixed.

Re: [partially confirmed]Turn // Burn

PostPosted: 22 Nov 2013, 09:41
by Aswan jaguar
Ok,so only the 4th needs to be fixed.

Re: [confirmed only bug 4]Turn // Burn

PostPosted: 30 Nov 2013, 00:19
by Gargaroz
Fixed as 59a53fb
My hatred for these split cars is unbearable.

Re: [fixed by gargaroz]Turn // Burn

PostPosted: 17 Jan 2014, 05:37
by BAgate
Sorry Gargaroz, but it's still bugged.

1) Still shows up as blue only in hand (but that could be a frames issue).
2) Can't cast Burn if only have 2 mana available.
3) Minor, but in the menu choosing what to cast, Burn has a lower case 'b'.

Re: [still bugged]Turn // Burn

PostPosted: 18 Jan 2014, 03:50
by RanDomino
All three confirmed.

Re: [still bugged]Turn // Burn

PostPosted: 03 Jun 2014, 15:17
by Gargaroz
Fixed 1 & 3 in 8659fe8
2 requires an update to "ct_all".

Re: [ct_all update needed]Turn // Burn

PostPosted: 17 Jul 2014, 13:25
by Gargaroz
Well, it seems that all the color entry of split cards on "ct_all" only cover one half, and this is wrong as:
"4/15/2013: In every zone except the stack, split cards have two sets of characteristics and two converted mana costs. If anything needs information about a split card not on the stack, it will get two values.
4/15/2013: On the stack, a split spell that hasn't been fused has only that half's characteristics and converted mana cost. The other half is treated as though it didn't exist.
4/15/2013: Some split cards with fuse have two monocolor halves of different colors. If such a card is cast as a fused split spell, the resulting spell is multicolored. If only one half is cast, the spell is the color of that half. While not on the stack, such a card is multicolored.
4/15/2013: Some split cards with fuse have two halves that are both multicolored. That card is multicolored no matter which half is cast, or if both halves are cast. It's also multicolored while not on the stack."

And this means we need a specific hack in the "get_cmc" and "get_color" function to deal with this. Luckily, whit the standardization of "split cards", now I know exactly when to look, so consider this fixed :)