Page 1 of 1

Saga cards need fix

PostPosted: 23 May 2018, 22:42
by thanosyro
Chainer’s Torment: the Horror token created after the third ability resolves, DOES NOT deal damage to its controller.
Rite of Belzenlok: the third ability DOES NOT occur... then the card is sacrificed.

I have not try other saga enchantments. i imagine there are issues there too. :(

edit: The Eldest Reborn: the third ability DOES NOT occur... the card is NOT sacrificed.

Re: Saga cards need fix

PostPosted: 30 May 2018, 13:01
by Splinterverse
I have fixed all of the above (but have not tested them).

They should appear in the next CW update.

Thanks for reporting these bugs.

Re: Saga cards need fix

PostPosted: 31 May 2018, 23:04
by thanosyro
thanks Splinterverse.
I ve tested All the Saga Enchantments and ONLY three of them have issues.

The Flame of Keld - III: after the third ability resolves, damage dealt by a red source is normal with no extra two damage.

Time of Ice - I: creature DOES UNTAP. II: creature does NOT untap (as it should)

Triumph of Gerrard - I,II: it puts +1/+0 instead of +1/+1 counter.
III: If it finds No legal target, it does NOT sacrificed and remains in the battlefield, gaining a counter each turn and doing nothing.

Appreciate your work. AND oc Xander's.

Re: Saga cards need fix

PostPosted: 01 Jun 2018, 03:18
by Xander9009
I fixed Time of Ice and Triumph of Gerrard, but The Flame of Keld is really complex and requires a lot more mental energy than I have right now.

Re: Saga cards need fix

PostPosted: 01 Jun 2018, 07:19
by thanosyro
UPDATE AFTER CW Core v1009:

Time of Ice - I. a counter is put normally, but nothing happens (no chose a creature to tap). II & III. working perfectly.

The Flame of Keld - same as before

No error log by the program.

Re: Saga cards need fix

PostPosted: 02 Jun 2018, 04:12
by Xander9009
Time of Ice is fixed. I tested it this time. Issue was that it was using EffectSource() being nil as the queue to end the effect, and since the first ability was being handled during the transition, it was nil once it actually hit the battlefield (and thus was in a new zone). Just needed to protect that pointer.

And yeah, like I said, I didn't touch The Flame of Keld at all.