Page 1 of 1

[fixed/closed]Heavy Fog

PostPosted: 20 Feb 2014, 16:17
by Aswan jaguar
Describe the Bug:
1- If AI attacks and you cast Heavy Fog till the end of turn if AI plays something or activates or,.... you will be asked for "interrupts..damage prevention" for every single land AI taps or activates,or every step....so numerous clicking.Also Effect lasts until the end of the turn (incorrectly and thus causing problem).
2new- I am adding a new bug:Heavy Fog prevents damage to creatures at least to Argothian Pixies
Which card did behave improperly ?
Heavy Fog

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
2014/02/18: Born of the Gods v2 - DUEL

What exactly should be the correct behavior/interaction ?
1- Probably prompt only if the attacking creatures somehow do non-combat damage while they are still attacking?
Heavy Fog effect ends when the combat ends (unless a new one begins although those cards we have don't work ) :D
2- It won't prevent damage attacking creatures would deal to creatures or planeswalkers you control.see rulings below:
Rulings:
Rulings: | Open
10/1/2009 If all the attacking creatures attack your planeswalkers, you can't cast Heavy Fog. To cast it, a creature needs to have attacked _you_.
10/1/2009 Heavy Fog prevents only damage that would be dealt to you by attacking creatures. It won't prevent damage attacking creatures would deal to creatures or planeswalkers you control.
10/1/2009 Heavy Fog prevents all damage attacking creatures would deal to you this turn, not just combat damage. Noncombat damage from those creatures is prevented only if they're still attacking at the time that damage would be dealt or, if the creature has left the battlefield by then, if it was an attacking creature at the time it left.


Are any other cards possibly affected by this bug ?
-

Re: Heavy Fog demands numerous clicking

PostPosted: 20 Feb 2014, 22:33
by BAgate
When I try your savegame the described behavior doesn't happen. I cast Heavy Fog, damage is prevented, AI then taps 4 lands and casts Ivory Guardian and I am never asked for interrupts...damage prevention.

Re: Heavy Fog demands numerous clicking

PostPosted: 21 Feb 2014, 05:00
by Aswan jaguar
Do you have duh mode on?Or maybe it is due to another config.txt value I have on and you don't.
edit.You didn't say if you confirm though that the effect lasts longer than is needed.

Re: Heavy Fog demands numerous clicking

PostPosted: 21 Feb 2014, 05:31
by BAgate
Duh mode doesn't matter (tried both), don't know if it is something else. As to it lasting too long, I'll leave that to the devs, but I think until we nail the second combat phase, it should be left.

As a side note, regardless of the legacy card length it works appropriately. I attacked with a Prodigal Sorcerer, AI cast Heavy Fog, no damage was dealt, I untapped him later that turn with a twiddle and when I tim'd him he suffered damage (but when I untapped in the middle of combat and tim'd him he didn't suffer damage). So I don't think there is really a bug.

Re: Heavy Fog demands numerous clicking

PostPosted: 21 Feb 2014, 20:02
by Aswan jaguar
I am adding a new bug:Heavy Fog prevents damage to creatures at least to Argothian Pixies.

Re: Heavy Fog demands numerous clicking

PostPosted: 21 Feb 2014, 20:24
by Korath
Confirm only that it prevents damage from attacking creatures to everything, not just you. Will be an easy fix once I finish up splicing. Also affects Deep Wood, which is identical.

It's supposed to last until end of turn; making the effect card go away at end of combat would be incorrect when combined with extra-combat-phase cards like Relentless Assault.

I don't know what's causing your extra prompts, but it's not this.

Re: Heavy Fog demands numerous clicking

PostPosted: 21 Feb 2014, 22:16
by Korath
Fixed c43c31a.

Re: [still bugged]Heavy Fog

PostPosted: 06 May 2014, 05:25
by BAgate
Can't cast it. AI attacks, I'm asked for fast effects, assign attackers and Heavy Fog does not highlight and can not be cast.

Re: [still bugged]Heavy Fog

PostPosted: 06 May 2014, 11:02
by Korath
It was checking if your opponent was attacked, not you (but also that it wasn't your turn, so it wasn't castable at any time). Fixed f1d605c.