Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Two bugs playing against the Sinister Six

A topic by quantumodo created 10 days ago Views: 79 Replies: 9
Viewing posts 1 to 6

Hi,

I think I've encountered a couple of bugs when playing against the Sinister Six ([0.5.9.4]-spider-man-sinister_six-(141)-(1931062262).json). 

- I defeated a villain with Taunting Presence (https://marvelcdb.com/card/27104) attached. It was the only villain. No threat was removed from Light at the End. However, it has been ruled that you can remove threat from Light at the End even in this case: 

“When defeated” abilities trigger before the card is discarded. Taunting Presence attachment reads “Threat cannot be removed from Light at the end”. Does it mean, If I defeat the attached villain, I cannot remove 4 (or 7) from Light at the end with villain’s “when defeat” ability?

You can remove threat from Light at the End when you defeat a Sinister Six villain, even if that villain had Taunting Presence attached.

- I played Toe to Toe (https://marvelcdb.com/card/10015) and was attacked by Scorpion. I played Back Flip and received no damage. But either way I was stunned and the 5 damage of Toe to Toe were not dealt to the villain. 

Thanks in advance

Let me add that the boos card was Sweeping Swoop (https://marvelcdb.com/card/01168)

Oh, OK, I see now. This is correct because Sweeping Swoop stuns if it DEALS damage, not if it DAMAGEs. Sorry, my bad. It was a complicated interaction. 

I've been thinking about this a little more. The Toe to Toe attack had been initiated before being stunned. The damage of Toe to Toe should be resolved and I should be stunned after the whole activation. 

Developer

Hi @quantumodo,

Thank you for bringing these issues to our attention and for providing your save file. Let’s discuss them one by one, starting with “27104” (Taunting Presence).

We reviewed the FAQ you provided, and we understand it suggests that an asset card won’t function when its attached card is defeated. However, after updating the code to align with that rule, we believe this interpretation may be incorrect.

For example, if you have a minion with the upgrade “01007” (Spider-Tracer), you can definitely trigger its effect when you defeat that minion.

“01007” reads:

Forced Interrupt: When attached minion is defeated, remove 3 threat from a scheme.

Therefore, we believe “01007” can be triggered because it is in play when you defeat the minion it is attached to, and “27104” should also work for the same reason, as it is also in play at that time.

We aim to avoid creating special rules for specific cards (unless that card has special text printed on it stating otherwise), as this could lead to more complications in the future.

Thank you for your understanding, and we appreciate your feedback!

(1 edit)

Yes, I see your point and I think it makes sense. However, this is not the only card with a similar behaviour. For instance, Sanctuary (https://marvelcdb.com/card/21116) states that Thanos cannot take damage, but its "When defeated" ability is, precisely, to deal damage to Thanos.  In that case, if an exception is not implemented, then the "When defeated" ability simply makes no sense. 

Developer

Hi @quantumodo,

Thank you for pointing out this example.

Card “21116” can function as intended because we have a special rule: a card with an effect that deals damage will ignore all damage prevention effects on it.

For “27104,” we have added a rule stating that all non-keyword effects on an asset will be ignored if its attached card is defeated. This change allows it to work in accordance with the FAQ and has passed all our unit tests.

Thank you for your understanding, and we appreciate your feedback!

That's awesome, thanks!

Developer

Hi @quantumodo,

Regarding “10015” (Toe to Toe), the question arises: what happens if my hero receives a stunned card while playing an event with the ‘attack’ label?

The attack of “10015” does not deal damage because we check the stunned status on the attacker each time before they deal any damage. This is based on legacy code that was in place before we fully implemented the ‘attack’ label.

According to the rules about being stunned, it states:

A stunned status card cancels a character’s next attack.

Since it specifies the “next attack,” we believe that the second part of the effect of “10015” should also trigger. We will address this in the next version.

Thank you for your understanding!

I completely agree with you. Thanks for fixing this!