It is currently 08 Jul 2021, 04:34
   
Text Size

[fixed/closed]Molten Vortex no prompt to damage & taps

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

[fixed/closed]Molten Vortex no prompt to damage & taps

Postby Aswan jaguar » 30 Dec 2015, 17:19

Describe the Bug:
1-When you activate Molten Vortex after you select land to discard,it get's discarded but then no prompt to target creature or player to damage.
2- When activated it taps.
Which card did behave improperly ?
Molten Vortex

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
Manalink 2015/12/25: Battle For Zendikar,duel

What exactly should be the correct behavior/interaction ?
1- Molten Vortex
2- Tap is not required for activation cost
Are any other cards possibly affected by this bug ?
-
Attachments
molten vortex-no target prompt.rar
(3.4 KiB) Downloaded 90 times
Last edited by Aswan jaguar on 19 Jan 2016, 14:53, edited 3 times in total.
Reason: fixed/closed
---
Trying to squash some bugs and playtesting.
User avatar
Aswan jaguar
Super Tester Elite
 
Posts: 7450
Joined: 13 May 2010, 12:17
Has thanked: 639 times
Been thanked: 351 times

Re: Molten Vortex no prompt to damage & taps

Postby Korath » 31 Dec 2015, 11:08

The result of poorly-designed interfaces: generic_activated_ability() and generic_spell() can be customized in substantially identical ways, using flags that are named substantially identically; but their flags have different values, and neither is capable of detecting when it's given the other function's flags. So for example in this case, the instruction to require and select a target turned into an activation cost of {T}.

The same problem affects (with varying effects and severities) Arenson's Aura, Flicker, Forerunner of Slaughter, Gateway Shade, Goblin Chirurgeon, Haazda Shield Mate, Hecatomb, Nihilistic Glee, Pia and Kiran Nalaar, Quillspike, Seismic Assault, Spike Rogue, Trade Caravan, and Vedalken Mastermind. All fixed in 13e1d37.

There's bugs open for Vedalken Mastermind and Flicker; the former should be fixed by this (the bug changed a prompt-changing flag into a -1/-1 counter requirement), and I'll confirm it shortly, but the latter seems unrelated. It's certainly possible that some of the others actually were working already due to having both the wrong flag and wrong kind of flag and got the correct values by accident; they'll be broken now.
Last edited by Aswan jaguar on 15 Jan 2016, 19:13, edited 1 time in total.
Reason: strikethrough fixed/closed
User avatar
Korath
DEVELOPER
 
Posts: 3522
Joined: 02 Jun 2013, 05:57
Has thanked: 491 times
Been thanked: 1037 times


Return to Archived Reports

Who is online

Users browsing this forum: No registered users and 2 guests


Who is online

In total there are 2 users online :: 0 registered, 0 hidden and 2 guests (based on users active over the past 10 minutes)
Most users ever online was 1922 on 07 Jun 2021, 06:01

Users browsing this forum: No registered users and 2 guests

Login Form