search

xkos / wagic

Automatically exported from code.google.com/p/wagic
0 stars 0 forks source link

(Usability) Add more graphical feedback for the Persist Ability #23

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
When the AI blocks, damage resolution and everything goes way too fast 
(actually, it's not displayed at all).Example: I attacked with a 5/5, and 
the AI blocked with a "3/2 persist  - when this card comes into play, you 
gain 2 life". But this didn't show graphically. What I saw was: I attacked 
with a 5/5, and suddenly my opponent gained 2 life and his creature (which 
I did not visually see blocking) lost -1/-1, while mine became 5/2. 
Extremely confusing.

Original issue reported on code.google.com by wagic.the.homebrew@gmail.com on 12 Sep 2009 at 11:34

GoogleCodeExporter commented 8 years ago 
After playing a little bit, I think it's more a problem with Persist than 
anything
else. We discussed this already, but having the card with persist going to the
graveyard and coming back to play (even if it looks like they are 2 different 
cards
with same time animations) would probably help

Original comment by wagic.the.homebrew@gmail.com on 1 Oct 2009 at 1:38

GoogleCodeExporter commented 8 years ago 
I actually have had problems with priority during the beginning of combat step.

For instance, I start off with a default file with Puppeteer in my collection, 
yet
it's not clear when I'm able to tap my opponent's Craw Wurm before he can 
declare it
as an attacker.

The same issue exists for the end step, in which I don't seem to get priority 
to ping
with Prodigal Sorcerer or used Puppeteer if I hadn't already.

Original comment by jvdth...@gmail.com on 13 Oct 2009 at 5:53

GoogleCodeExporter commented 8 years ago

Original comment by wagic.the.homebrew@gmail.com on 9 Dec 2009 at 5:54

GoogleCodeExporter commented 8 years ago

Original comment by wagic.the.homebrew@gmail.com on 13 Dec 2009 at 10:10

GoogleCodeExporter commented 8 years ago 
This issue has been here for too long and nobody seems to want to work on it. 
It is not a "bug" because it does not prevent from playing the game correctly,  
so I'm closing this

Original comment by wagic.the.homebrew@gmail.com on 18 Sep 2010 at 9:10