Page 1 of 1

[fixed/closed]Rushing River when kicked bad effect

PostPosted: 21 Dec 2014, 11:06
by Aswan jaguar
Describe the Bug:
Rushing River when kicked opens correctly a menu asking 1 of 2 targets then 2 of 2 targets but then instead of resolving it opens the no kicked menu to target a creature and you are obliged to target one and when you do if the target isn't the first creature you targeted in the kicked menu it will return to hand the 2nd target and the new target.

Which card did behave improperly ?
Rushing River

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
Previous update: Manalink update 14 November 2014: Khans of Tarkir + more

What exactly should be the correct behavior/interaction ?


Are any other cards possibly affected by this bug ?
-

Re: [confirmed]Rushing River when kicked bad effect

PostPosted: 25 Dec 2014, 08:09
by Aswan jaguar
Also AI produced thi dump error when playing Rushing River:

bad parameters | Open
get_displayed_card_instance(-1, -1)
0: 0x023DB788
1: 0x0239849E
2: 0x023E51C1
3: 0x7E418734
4: 0x7E418816
5: 0x7E42927B
6: 0x7E42F40B
7: 0x0047891E
8: 0x00427A43
9: 0x00493617
10: 0x7E418734
11: 0x7E418816
12: 0x7E428EA0
13: 0x7E428EEC
14: 0x7C90E473
15: 0x004AC32A
16: 0x004AC769
17: 0x0044631B
18: 0x7E418734
19: 0x7E423CE4
20: 0x7E423B30
21: 0x7E43E599
22: 0x7E418734
23: 0x7E418816
24: 0x7E42927B
25: 0x7E4292E3
26: 0x7E44FF7D
27: 0x7E4465D2
28: 0x7E425E94
29: 0x7E43B082

Re: [confirmed]Rushing River when kicked bad effect

PostPosted: 27 Dec 2014, 16:04
by Gargaroz
Fixed in b58e86b