[fixed/closed]Torture produce errors

[Aswan jaguar]

Describe the Bug:
AI wanted to cast Headstone with no cards in any graveyard and 2 dump errors were produced.(Game seemed to work fine after that).wrong
Korath below says error is from Torture.

2nd error | Open

bad parameters
get_card_instance(-1, -1)
0: 0x02467F44
1: 0x0241DED5
2: 0x02417A1D
3: 0x0216272F
4: 0x004018E0
5: 0x004A2806
6: 0x02475ED5
7: 0x0242959D
8: 0x024295E7
9: 0x02429C8E
10: 0x004368C6
11: 0x024260E8
12: 0x0043C200
13: 0x004399BD
14: 0x0047902C
15: 0x004946E9
16: 0x7C80B729

Which card did behave improperly ?
HeadstoneTorture

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
Manalink 2016/08/27: Eldritch Moon v2, duel

What exactly should be the correct behavior/interaction ?
Torture

Are any other cards possibly affected by this bug ?
-

[Korath]

That dump is from Torture, not Headstone.

Code: Select all

show_backtrace(...)
get_card_instance(...)
No line number information available for address 0x2417a1d <add_or_remove_counters_impl.part.1+29>
card_torture(...)
call_cards_function<eax>(card_data_t *cd<eax>, int player, int card, event_t event)
fx_activation_906(int player, int card, event_t event)
call_card_fn_impl(...)
call_card_fn(...)
call_card_function_i(...)
dispatch_event_to_single_card(...)
resolve_top_card_on_stack()
finalize_activation(...)
main_phase(int player, int a4, int a5)
switch_phase(int a3)
start_duel()
start_duel_thread(int a1)
0x7c80b729

[Aswan jaguar]

In case it adds any more info this the first bug produced which is then followed by the one I have in my first post.

1st bug | Open

bad parameters
get_card_instance(-1, -1)
0: 0x02467F44
1: 0x0241DED5
2: 0x02418114
3: 0x0216272F
4: 0x004018E0
5: 0x004A2806
6: 0x02475ED5
7: 0x0242959D
8: 0x024295E7
9: 0x02429C8E
10: 0x004368C6
11: 0x024260E8
12: 0x0043C200
13: 0x004399BD
14: 0x0047902C
15: 0x004946E9
16: 0x7C80B729

[Korath]

Also Torture.

Code: Select all

bad parameters
get_card_instance(-1, -1)
show_backtrace(...)
get_card_instance(...)
add_counters(...)
card_torture(...)
call_cards_function<eax>(card_data_t *cd<eax>, int player, int card, event_t event)
fx_activation_906(int player, int card, event_t event)
call_card_fn_impl(...)
call_card_fn(...)
call_card_function_i(...)
dispatch_event_to_single_card(...)
resolve_top_card_on_stack()
finalize_activation(...)
main_phase(int player, int a4, int a5)
switch_phase(int a3)
start_duel()
start_duel_thread(int a1)
0x7c80b729

[Korath]

Torture's also a heck of a lot more broken than this in dev. Among other things, you can counter its activated ability by Disenchanting or otherwise destroying the aura before the ability resolves. And it looks like the same breaking change is being made systematically to other auras and equipment. Feh. I'm washing my hands of it.

[Gargaroz]

Mmmh, I've fixed at least one of the error that Korath mentioned (the "counter ability with Disenchant". I'll check to see if I introduced similar errors while checking almost the whole cardpool. Believe me, if I have introduced new errors, I've also extirpated AT LEAST the same quantity of coding-horrors I made in the old days before even Mok came and break the 2000 card limit.