Page 4 of 4

Re: Bug Reports 1.3.0 dev 2014-08-19

PostPosted: 28 Aug 2014, 07:27
by fireshoes
I had an Altac Bloodseeker and Frost Lynx attack my opponent. Opponent blocked the Lynx and I gave it first strike with Crowd's Favor to kill the block. Altac triggered to get +2/0 and gain first strike, but did not deal damage in the regular combat damage step. Since it did not have first strike when first strike combat damage was dealt, it should have dealt the damage in the regular combat step.

702.7c. Giving first strike to a creature without it after combat damage has already been dealt in the first combat damage step won't prevent that creature from assigning combat damage in the second combat damage step. Removing first strike from a creature after it has already dealt combat damage in the first combat damage step won't allow it to also assign combat damage in the second combat damage step (unless the creature has double strike).

https://github.com/magefree/mage/issues/551

Re: Bug Reports 1.3.0 dev 2014-08-19

PostPosted: 28 Aug 2014, 23:31
by fireshoes
I was unable to tap an Argothian Enchantress to activate Earthcraft's ability. Even though Argothian Enchantress has Shroud, tapping it with Earthcraft doesn't target it. It's just paying the cost of the ability.

FIXED

Re: Bug Reports 1.3.0 dev 2014-08-19

PostPosted: 29 Aug 2014, 00:15
by juanmiguel
I had my forest tap for colorless instead of green on a game against human. It was on a m15 draft tournament. When I left the cursor over forest on sideboard they said "T: add Green" but inside of the game they said "T: add 1".
Somebody said it's happening to mountains too.
There you have a pic of it.

FIXED (I HOPE)

Re: Bug Reports 1.3.0 dev 2014-08-19

PostPosted: 29 Aug 2014, 02:16
by liferider09
In addition to the above, it seems to happen to all mana producers. My Stomping Grounds and Grove of the Burnwillows were having that issue, as well. It seems that cards that allow you to choose a color (eg. Birds of Paradise or Chromatic Star) do not have this problem.

Also, if it helps, the green mana problem happened first, and the red one compounded upon later. Sorry, I do not know the exact time.

FIXED (I HOPE)

Re: Bug Reports 1.3.0 dev 2014-08-19

PostPosted: 29 Aug 2014, 08:32
by LevelX
fireshoes wrote:Edit: Also just noticed that the art on some of the cards from Beta is showing the wrong cards. Not sure if that would be a local problem on my computer somehow or if it affects everyone. Mox Emerald show Meekstone, Mox Jet shows Mox Emerald, Mox Pearl shows Mox Jet, etc.
Yes this cards had at some time in the past the wrong card number assigned. So the download of images saved a wrong images for this card names. You have to manually delete the images which are saved with wrong names.
E.g. delete the file called "Mox Emerald.full.jpg" that shows a Meekstone to correct the problem because Xmage can't check if the image itself is correct or not. As the card numbers are corrected some time ago, XMage will download now the correct images for the cards as you download missing images.

Re: Bug Reports 1.3.0 dev 2014-08-19

PostPosted: 01 Sep 2014, 01:53
by fireshoes
LevelX, I tried deleting each of the beta images that were incorrect from images/LEB.zip. When I restart XMage, it prompts me to download the missing images, but it is just the same incorrect images again. Am I doing something wrong?

Re: Bug Reports 1.3.0 dev 2014-08-19

PostPosted: 01 Sep 2014, 05:23
by LevelX
fireshoes wrote:LevelX, I tried deleting each of the beta images that were incorrect from images/LEB.zip. When I restart XMage, it prompts me to download the missing images, but it is just the same incorrect images again. Am I doing something wrong?
Did you also delete the LEB.thumb.zip to replace the wronmg thumbnail images?
I checked all the examples you mentioned and they all show the correct image for me.

EDIT:
To be sure you can also delete the h2 db files in mage-client/db/ directory and reconnect to the server to get a complete fresh db, where the card numbers are coming from. But as you probably use the lates release that should be the case anyway.