Page 2 of 4

Re: Bug Reports xmage 1.4.14

PostPosted: 17 Aug 2016, 23:40
by KillSwitch
There is a HiDPI scaling issue. I am trying to run the app on my surface book pro and the scaling is way off. The resolution I am running at is 3000 x 2000

Re: Bug Reports xmage 1.4.14

PostPosted: 18 Aug 2016, 13:28
by ISmackKids
Hallowed Moonlight does not prevent Brisela, Voice of Nightmares from entering the battlefield.

Not sure wether or not this affects the other two Meld-pairs in the set.

Re: Bug Reports xmage 1.4.14

PostPosted: 18 Aug 2016, 20:11
by Dynamo345
very very simple

the token images are not showing anymore on the battlefield

and these were images downloaded before

the biggest and best example is Omnath, Locus of Rage

See OP first post: Already fixed but not available until the next XMage update
* Fixed that token images were not loaded.

Re: Bug Reports xmage 1.4.14

PostPosted: 19 Aug 2016, 03:19
by amoeba
What changed with the random algorithm for deck shuffle? Since the newest update, the occurrences of draw sequences during games that are so statistically unlikely as to be almost impossible appear to be happening quite often. Did your rand() get tweaked or changed to some pseudo-random?

eg. Standard format, 24 land in a deck. Within a span of 7 matches, the number of time the deck (no changes) has drawn ~half of the entire land in the deck (10+) within the first 15 cards has happened 4 times. The opposite occurs (no land for >10 draw sequences) more often as well.

Re: Bug Reports xmage 1.4.14

PostPosted: 19 Aug 2016, 11:37
by ISmackKids
Brisela, Voice of Nightmares' "Your opponents can't cast spells with converted mana cost 3 or less" effect still lingers around, even after Brisela has been removed from the battlefield.

Also, Emrakul, the Promised End does not grant the chosen opponent an extra turn, so he acts like mindslaver (which he shouldn't).

[EDIT] Seems like the Emrakul issue only applies if you roll back to the controlled turn.

Re: Bug Reports xmage 1.4.14

PostPosted: 19 Aug 2016, 17:12
by amoeba
amoeba wrote:What changed with the random algorithm for deck shuffle? Since the newest update, the occurrences of draw sequences during games that are so statistically unlikely as to be almost impossible appear to be happening quite often. Did your rand() get tweaked or changed to some pseudo-random?

eg. Standard format, 24 land in a deck. Within a span of 7 matches, the number of time the deck (no changes) has drawn ~half of the entire land in the deck (10+) within the first 15 cards has happened 4 times. The opposite occurs (no land for >10 draw sequences) more often as well.
Another 24h of testing. 10 matches, # of times excess land draws in 1st 20 cards of the deck = 5. I bought a lotto ticket today.

At this point, I might as well play a landfall deck to abuse whatever is messed up with the randomization code.

escplan9: nothing has changed in the randomization. What you are experiencing are long strings of unlikely circumstances. These long strings will happen from time to time, but over the course of millions of games the probabilities go to their expected values. This has been discussed many times and it comes down to human's perception bias and difficulty fully grasping long-term statistics.

Re: Bug Reports xmage 1.4.14

PostPosted: 20 Aug 2016, 03:26
by neutralgnome
Thrumming Stone is 1-use; it falls into your library whenever you cast a spell and look at the top cards of your library.
In correct play it should stay on your battlefield.

Demonic Pact does not roll back options you have chosen when you roll back the game, which can be rather devastating.
E.g. Turn 3: there are 2 valid options for me ("Draw 2 Cards" or "Lose the Game"). I choose "Draw 2 Cards". We go to Turn 4. Realizing I made a mistake, I roll back to turn 3. I then only have the option of "Lose the Game".

Re: Bug Reports xmage 1.4.14

PostPosted: 21 Aug 2016, 08:32
by JeskaiCharmer
Opponent said Mox Diamond wasn't prompting him to discard a land - it just resolved and went to graveyard. Haven't confirmed myself.

Another issue I noted is that +1/+1 counters and -1/-1 counters don't seem to be canceling each other out, as per Rule 121.3. I cast Skinrender, putting 3 -1/-1 counters on a Hangarback Walker with 3 +1/+1 counters on it, but my opponent got 3 Thopters when Hangarback died.

escplan9: The interaction between Skinrender and Hangarback is working correctly. See Hangarback Walker rulings here http://gatherer.wizards.com/Pages/Card/ ... eid=398572:

If enough -1/-1 counters are put on Hangarback Walker at the same time to make its toughness 0 or less, the number of +1/+1 counters on it before it got any -1/-1 counters will be used to determine how many Thopter tokens you get. For example, if there are three +1/+1 counters on Hangarback Walker and it gets four -1/-1 counters, you’ll get three Thopter tokens. That’s because Hangarback Walker’s triggered ability checks the creature’s existence just before it leaves the battlefield, and it still has all those counters on it at that point

Re: Bug Reports xmage 1.4.14

PostPosted: 21 Aug 2016, 18:54
by JeskaiCharmer
Thank you for the Hangarback Walker clarification. I disagree with the interpretation of the rules such that that is the ruling in that situation, but if that's the official rule, then as long as the program is doing it correctly I'm happy.

Re: Bug Reports xmage 1.4.14

PostPosted: 22 Aug 2016, 00:27
by markocheese
Simple bug. Survive the Night didn't grant my creature indestructible.

Details:
I had a Hinterland Logger and he blocked with his Blood Brier. After blockers were declared I used Survived the Night and it pumped my logger to the 3 power needed to kill the Blood Brier, but my logger died too.

escplan9: Could not duplicate the issue. Do you have a game log? See https://github.com/magefree/mage/blob/m ... tTest.java for test

Re: Bug Reports xmage 1.4.14

PostPosted: 23 Aug 2016, 17:03
by ISmackKids
Mindslaver effects don't seem to work properly if your opponent F9s.
XMage just skips to the next step whenever the mindslavere'd player has priority.

Re: Bug Reports xmage 1.4.14

PostPosted: 23 Aug 2016, 18:28
by Julia
Currently unable to host a Rich Man Draft tournament. The "new tournament" window creates a window so tall that it's impossible to see the bottom, therefore also impossible to cancel the window, forcing a client restart. As shown in the image, the upper left drop down does not help with the issue either.

Image

Re: Bug Reports xmage 1.4.14

PostPosted: 24 Aug 2016, 07:57
by JeskaiCharmer
Opponent used Channel and added 4 colorless to mana pool. He also had out Oath of Nissa but was saying the game wouldn't let him cast Garruk Wildspeaker with that mana. Can't confirm for sure as it was on opponent's end, but Oath or Channel may be bugged.

Re: Bug Reports xmage 1.4.14

PostPosted: 24 Aug 2016, 11:13
by HarePaiR
May be something wrong with Fate Reforged pack generation. Packs have multiple rares in them.

(Localserver, Mac OS X server and 2 clients, draftbots, FTR KTK KTK, also happens with DTK DTK FTR, but only for FTR packs)
Screen Shot 2016-08-24 at 7.08.38 PM.png

Screen Shot 2016-08-24 at 7.07.40 PM.png


LevelX: Fixed beyond 1.4.15v1

Re: Bug Reports xmage 1.4.14

PostPosted: 25 Aug 2016, 09:42
by crazycoolmc3
I have no idea what is going on it was working fine yesterday now it wont let me do anything

And I dont understand the log at all I have tried reinstalling deleting and redownloading it nothing is working