Simply put, an interaction in the video game has been posted in my "Interactions that seem like bugs" thread on the Steam forums where someone attempted to get rid of Twisting Back Alleys by it's condition (Play the top card of the villain and environment deck) and it didn't count targets played by Mad Bomber Blade keeping Twisting Back Alleys in play, is this the correct interaction or should it be reported to Handelabra as a bug?
Sounds like a bug to me, you played a card, doesn't matter that it was destroyed because of text on a different card you still fulfilled Twisting Back Alleys' condition.
Agreed, a card is played, just because it's put straight under Mad Bomber Blade shouldn't stop Twisting Back Alleys from being destroyed.
On his front side I would think it should keep playing cards if it was a target that went under him.
Yes, definitely. that's what his card says after all....
Ah, is that what was happening in your game bluedarky? Was it playing multiple cards and not not counting the targets it was playing but behaving as the text on Blade says it should?
Blade played multiple cards, then the environment played a card, then it moved on to the next environment cards EoT text without destroying Twisted Back Alleys.
It isn't being destroyed, nor is it going into the Baron's play area. It is going under the character card and having no effect upon the game, at least until he flips.
Not quite correct, I think.
Whenever a Villain Target enters play, put it under this card and play the top card of the Villain deck. Cards under this card have no game text, are indestructible, and are not considered in play.
This says to me that the card does enter Blade's play area. It then stays in the Baron's play area, but loses all text (because it's under his card). Therefore, the card is being played (since that's how it enters play, which is what causes it to be moved under the Blade), and should destroy Twisting Back Alleys.
The wording on Mad bomber moves cards that enter play, and doesn't use instead, so they are played, then go under.
It is doing it wrong inthe app.
Yup, MigrantP has just responded that it is a bug in the app here.