Page 1 of 1

[engine limitation]Imprison no ability trigger, bad combat

PostPosted: 03 Oct 2014, 01:58
by Nexhro
Describe the Bug:
1) Imprison doesn't trigger off activated abilities with {T} in their activation costs of the creature it's enchanting.

2) When enchanted creature attacks or blocks and {1} is paid for imprison's triggered ability, Imprison is tapped instead of the enchanted creature and the creature is not removed from combat.

Which card did behave improperly ?
Imprison

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
CoRM15 mini3, duel

What exactly should be the correct behavior/interaction ?
Imprison triggers off activated abilities with {T} in their activation costs of the creature it's enchanting.

When enchanted creature attacks or blocks and {1} is paid for imprison's triggered ability, that creature is tapped and removed from combat.

Are any other cards possibly affected by this bug ?
-

Re: [confirmed]Imprison no ability trigger, bad combat

PostPosted: 16 Oct 2014, 14:03
by Gargaroz
Actually, the "counter ability" part was never coded as it's impossible to discriminate between the various activation legacy.
The other bug is fixed in 8f57b03

Re: [confirmed]Imprison no ability trigger, bad combat

PostPosted: 16 Oct 2014, 14:14
by Aswan jaguar
Gargaroz wrote:Actually, the "counter ability" part was never coded as it's impossible to discriminate between the various activation legacy.
The other bug is fixed in 8f57b03
Yes,but what about all the other creature cards that have an activation cost and don't need a legacy to be activated,why don't we make it work at least with those?

Re: [confirmed]Imprison no ability trigger, bad combat

PostPosted: 02 Nov 2014, 16:35
by Gargaroz
I meant: in Manalink, when a card is activated, a invisible legacy card is created to carry on that card code (is needed as some cards requires its own sacrifice to activate).
By parsing that legacies we could know some information about the source card, but no the kind of information Imprison needs to function (and this is the reason why it wasn't coded back in the days, I suspect).