[fixed]Dual Nature copies tokens

by **Korath** » 29 Aug 2017, 12:07

Describe the bug:
Dual Nature copies creature tokens. Including those that it creates at the resolution of its trigger, so if you get one creature, it keeps on making copies until it hits the 150-card-per-player maximum.

Which card behaved improperly?
Dual Nature.

Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Dev fa1f629.

What exactly should be the correct behavior/interaction?
"Nontoken".

Are any other cards possibly affected by this bug?
This bug makes Dual Nature's two leave-the-bf triggers inconvenient to test, so I didn't try; though thinking about it now, you could test the first one by making a token copy with something else before putting Dual Nature on the bf.

Source for the EMNv2 version looks ok. (At least, it has a F1_NO_TOKEN stuck in the middle of specific_cip()'s huge opaque list of arguments.)

by **Aswan jaguar** » 02 Sep 2017, 08:11

The first of ~10 errors that Dual Nature produces when a creature is played if it helps:

dump error | Open: bad parameters
get_card_instance(1, -1)
0: 0x0247CE18
1: 0x024A4FDE
2: 0x0249236B
3: 0x02492D3B
4: 0x0206E0DD
5: 0x024EC735
6: 0x024D745D
7: 0x024D74BF
8: 0x024D54B4
9: 0x0206DE79
10: 0x024EC735
11: 0x024D745D
12: 0x024D7FC4
13: 0x024D8376
14: 0x004367C3
15: 0x024D84B0
16: 0x004766DC
17: 0x024D76FF
18: 0x024D7E16
19: 0x024DEE84
20: 0x024DFFAB
21: 0x02492CE9
22: 0x0206E0DD
23: 0x024EC735
24: 0x024D745D
25: 0x024D74BF
26: 0x024D54B4
27: 0x0206DE79
28: 0x024EC735
29: 0x024D745D

by **Aswan jaguar** » 17 Mar 2019, 13:39

Fixed in commit b0fe95f.