goupildb / wagic

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

functionality of selecting targets you intend to blocked during large combat scenarios #463

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. play against any token creator base opponent deck.
2. hold back until they have about 21 different creature
3. try to block a specific creature in the middle.

What is the expected output? What do you see instead?

what i see is that it becomes increasing more difficult to block the correct 
opponent creature, this might seem trivial UNTIL you fight against an opponent 
deck with cards such as phaige the unstoppable, which will make you lose the 
game if hit by her. 

consider this, in 3 matches vs an ai deck i built that contained 1 phaige, i 
was only able to successfully pick her out of the horde of zombie tokens that 
deck had once. 2/3 times losing due to not knowing exactly what in the middle 
im blocking means that this should be considered for repair and adjusting.

what i would like to see:

when you are moving the "blocker" along the row to select who you will block. 
have it grey out EVERYTHING that it is NOT going to be considered "blocked" by 
this card, and slightly enlarge(just as a visual queqe) and highlight the one 
that the current "blocker" is considered blocking maybe with a shiney glittery 
sprinkly boarder or as if it is "backlit" by a light source, consider having 
this highlighted thumbnail view "move to top layer"
so you can be extra certain of the card you are declaring blocked.

currently the card will remain tapped being overlapped by the card next to it 
not highlight, not enlarge, no visual queqes at all that it is being declared 
blocked by your creature.

for an exsample of the requested fix, have 20 cards in your hand, notice how 
the one that you are currently on gives you visual queqes by enlarging, "moving 
to the top layer" ect? something like this but as you are moving a creature 
across the feild, and with an added "greying out "non blocked creatures" as 
long as you currently have your "declaree" as the cursors main focus. as soon 
as you move to another creature/object have it return things to normal, if you 
move BACK to that creature, grey everything out and trigger the visual Qeuqes 
again (enlarge what its blocking slightly, move the card view of what its 
blocking to top layer so you can see it clearly, MAYBE fancy glittery effects 
or backlit just for a touch of wow factor)

Please use labels and text to provide additional information.

Original issue reported on code.google.com by omegabla...@gmail.com on 26 Sep 2010 at 10:47

GoogleCodeExporter commented 9 years ago
for some neat already possible eyecandy effect queqes...consider the following

backlighting the "blocked card"

use momir fancy name of card flying across screen as it becomes the card you 
are declaring "blocked" in this format "Blocking [cardname]"

a 1/4 sized(compared to big view) card view near the upper left or right hand 
courner. that shows up as you have the "blockee" selected as cursor.

Original comment by omegabla...@gmail.com on 26 Sep 2010 at 10:59

GoogleCodeExporter commented 9 years ago
for minimum amount of work to fix this issue:

have card that is being declared "blocked" enlarge and move to top layer ( the 
same way cards in hand currently handle this same action) as you have "blockee" 
selected as cursor.

Original comment by omegabla...@gmail.com on 26 Sep 2010 at 11:01

GoogleCodeExporter commented 9 years ago

Original comment by wagic.the.homebrew@gmail.com on 27 Sep 2010 at 12:31

GoogleCodeExporter commented 9 years ago
i have a *slight* improvement to this, it does not include eyecandy, simply a 
small visual Queqe that will show you what you are currently under.

Original comment by omegabla...@gmail.com on 30 Sep 2010 at 6:58

GoogleCodeExporter commented 9 years ago

Original comment by omegabla...@gmail.com on 16 Nov 2010 at 7:26

GoogleCodeExporter commented 9 years ago
blocking was changed to a non-targeted target action, this is no longer a valid 
issue.

Original comment by omegabla...@gmail.com on 31 Jan 2013 at 7:00