Re: Developing Bugs
Ah... that's easy to explain.RedDeckWins wrote:Sorry, to clarify, there is no exception:
The bug is that the effect is put into the command zone of the wrong player when it resolves. There is no exception. The pasted callstack just a little insight into how/where the activating player is being set incorrectly before the EffectEffect resolves.
The spellability instances are reused, that is there is only one per ability per card. AI tends to set activating player to itself when it... 'thinks' - I don't know exactly what it does, either evaluates threat from abilities on stack or their costs. But this often involes assigning "activating player" with AI's player.
To restore the correct player as the ability resolves, it's store in SpellAbilityStackInstance. Yesterday being unaware of the above described effect I deleted that field - that lead to a wide variety of bugs. Today I had to revert that change - r21483. So this should have solved issues with wrong player that recieves an effect.
Did you ever bring up the issue on the forum here so that one of the guys familiar with inputs could see if they could track down the cause?
Missed tht somehow. I'll remove it from svn before the next build.