It is currently 22 Nov 2025, 13:33
   
Text Size

[confirmed]cascade mechanic + Rakdos, Lord of Riots = bad

Report wrong Card behavior to get it fixed.
PLEASE ADD SAVEGAMES TO YOUR TOPIC !

Moderators: Aswan jaguar, gmzombie, stassy, BAgate, drool66, CCGHQ Admins

[confirmed]cascade mechanic + Rakdos, Lord of Riots = bad

Postby BAgate » 09 May 2016, 06:31

Describe the Bug:
You may cast Rakdos, Lord of Riots via cascade even if opponent has not lost life this turn.

Which card did behave improperly ?
cascade and/or Rakdos, Lord of Riots

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
Manalink 2016/01/15: Battle For Zendikar v2,duel

What exactly should be the correct behavior/interaction ?
Can't effects take precedence over can effects (101.2).

Are any other cards possibly affected by this bug ?
-
Attachments
cascade.rar
(2.86 KiB) Downloaded 155 times
Last edited by Aswan jaguar on 10 May 2016, 13:29, edited 1 time in total.
Reason: confirmed
Working on: housekeeping and archived reports
User avatar
BAgate
Tester
 
Posts: 2444
Joined: 06 Mar 2012, 11:09
Has thanked: 117 times
Been thanked: 158 times

Re: cascade mechanic + Rakdos, Lord of Riots = bad

Postby Korath » 09 May 2016, 10:56

(Bloodbraid Elf, for handy reminder text in the autocard.)

This is a side effect of the way we implement "can't cast this card" effects for creatures, artifacts, and (only in theory? are there any?) lands. The engine only sends EVENT_CAN_CAST to cards if they're part sorcery, instant, or enchantment (and only to the card itself, see here), so we make the card say it has an effectively-infinite casting cost (100 of each color mana plus 100 generic) instead to make it uncastable.

I've been experimenting in Shandalar with using a flag to indicate a card needs EVENT_CAN_CAST sent to it despite being only a creature (initially for Serra Avenger), but not quite all the places that check it have been rewritten yet, so I think it still uses something analogous to Manalink's infinite_casting_cost() hack in one place.

Two alternate solutions, neither of which I think is scalable in the long term but both of which are better than starting to add individual hacks for each individual card into the backend of cascade and similar effects:
  • Flag these cards as sorceries so they get EVENT_CAN_CAST normally. Make sure all the checks for TYPE_SORCERY go through is_what(), never just a card_data_t::type & TYPE_SORCERY check, like for the flash-as-TYPE_INSTANT hack.
  • Add an EVENT_CANT_BE_PLAYED that gets sent by can_legally_play_iid(), and make each of these cards respond to that in addition to their EVENT_MODIFY_COST handlers. (CANT_BE_PLAYED instead of CAN_BE_PLAYED so that the default return value of 0 is right for everything that doesn't handle the event.)
User avatar
Korath
DEVELOPER
 
Posts: 3708
Joined: 02 Jun 2013, 05:57
Has thanked: 496 times
Been thanked: 1108 times


Return to Bug Reports

Who is online

Users browsing this forum: No registered users and 76 guests

Main Menu

User Menu

Our Partners


Who is online

In total there are 76 users online :: 0 registered, 0 hidden and 76 guests (based on users active over the past 10 minutes)
Most users ever online was 9824 on 10 Nov 2025, 04:33

Users browsing this forum: No registered users and 76 guests

Login Form