So I was playing against rogue and he had a Forsaken Lieutenant stealthed on the board. The following turn he played a Gigafin which consumed my board and gave him a 2/2 Gigafin + the 4/7 maw and a 7/4 Gigafin + a 4/7 maw.
So far so good - the 2/2 is the copied version from the Forsaken Lieutenant and the "normal sized" maw is due to the collosal key-word.
Where things get odd is that I had no way to destroy the gigafin(s) without killing both maws first. When I killed the 2/2 Gigafin I got my board back.
This seems like a bug to me but maybe there's some twisted logic that makes this make sense....
For the blackwater behemoth example I know it doesnt always attack the behemoth associated with the lure. I'm not sure if there's an order though (such as which one is summoned first) or if it's random.
My guess is that Gigafin's battlecry is what assigns what the Maw's deathrattle should do, so without that battlecry the Maw is effectively a dud.
Coding wise this probably makes sense - the 2/2 copy still has the minions in it (because it's a copy of a Gigafin which activated its battlecry) but the maw doesnt (because there was no battlecry activated by the copy).
Id wager the data the maw clears on deathrattle is defined by the battlecry so when LT copies it stores the deathrattle data from the initial gigafin battlecry but doesnt apply it to the maw since the maw isn't spawning conventionally after the battlecry is defined.
To get it to work they need to decouple the maw's deathrattle from the battlecry data and make it absolute and generic (clear spawned from gigafin deathrattle data). Kinda like silencing it but not.
So I was playing against rogue and he had a Forsaken Lieutenant stealthed on the board. The following turn he played a Gigafin which consumed my board and gave him a 2/2 Gigafin + the 4/7 maw and a 7/4 Gigafin + a 4/7 maw.
So far so good - the 2/2 is the copied version from the Forsaken Lieutenant and the "normal sized" maw is due to the collosal key-word.
Where things get odd is that I had no way to destroy the gigafin(s) without killing both maws first. When I killed the 2/2 Gigafin I got my board back.
This seems like a bug to me but maybe there's some twisted logic that makes this make sense....
For the blackwater behemoth example I know it doesnt always attack the behemoth associated with the lure. I'm not sure if there's an order though (such as which one is summoned first) or if it's random.
My guess is that Gigafin's battlecry is what assigns what the Maw's deathrattle should do, so without that battlecry the Maw is effectively a dud.
Coding wise this probably makes sense - the 2/2 copy still has the minions in it (because it's a copy of a Gigafin which activated its battlecry) but the maw doesnt (because there was no battlecry activated by the copy).
If that's the case this is probably a bug
Id wager the data the maw clears on deathrattle is defined by the battlecry so when LT copies it stores the deathrattle data from the initial gigafin battlecry but doesnt apply it to the maw since the maw isn't spawning conventionally after the battlecry is defined.
To get it to work they need to decouple the maw's deathrattle from the battlecry data and make it absolute and generic (clear spawned from gigafin deathrattle data). Kinda like silencing it but not.
tldr, does it mean permanently whatever they are?