Page 2 of 3

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 18 Jul 2019, 04:18
by Msdos4
It seems Blood Moon doesn't work well. Shock-lands (if you decline to pay) enter the battlefield tappet although it should enter untapped. Also it works worng with lands enters with counters (i.e. Blast Zone, that enter with charge counter), they should enter without counters.

Long known issue. No cure in sight, unfortunately. https://github.com/magefree/mage/issues/4202

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 19 Jul 2019, 18:59
by Hoac
For some reason Sisay, Weatherlight Captain is treated as a WURBG Legendary Creature (inside the command zone, as well as once it enters the battlefield), and thus destroy-able by stuff like Pyroblast.

| Open
Screenshot (5).png

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 20 Jul 2019, 09:34
by BlackLotus82
Hi, just a few things you're maybe just aware of:
1) "9th Edition Box" set symbol is wrongly associated to "8th Edition" symbol (see screenshot below);
2) several missing set symbols;
3) multi-numbered token images not correctly displayed.

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 20 Jul 2019, 14:35
by Taru
Blightbeetle doesn't prevent counters put on Voracious Hydra when entering the battlefield, as it should according to:
https://gatherer.wizards.com/Pages/Card ... eid=466841

Bug with Attriotion in Commander

PostPosted: 29 Jul 2019, 09:16
by Firutin
I could not target Alesha, Who Smiles at Death with Attrition as a non-black creature. I know her color identity is red-white-black, but she is only a red creature.

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 29 Jul 2019, 18:18
by birkemand
Just installed Xmage on Mac and get this dyld error message in the XMage Client console. Can anyone help?

dyld: lazy symbol binding failed: Symbol not found: _pthread_set_qos_class_self_np
Referenced from: /Users/USER/Downloads/java/jre.1.8.0_201.jre/Contents/Home/lib/libjfxwebkit.dylib
Expected in: /usr/lib/libSystem.B.dylib

Symbol not found: _pthread_set_qos_class_self_np
Referenced from: /Users/USER/Downloads/java/jre.1.8.0_201.jre/Contents/Home/lib/libjfxwebkit.dylib
Expected in: /usr/lib/libSystem.B.dylib

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 02 Aug 2019, 11:48
by JayDi
birkemand wrote:Just installed Xmage on Mac and get this dyld error message in the XMage Client console. Can anyone help?

dyld: lazy symbol binding failed: Symbol not found: _pthread_set_qos_class_self_np
Referenced from: /Users/USER/Downloads/java/jre.1.8.0_201.jre/Contents/Home/lib/libjfxwebkit.dylib
Expected in: /usr/lib/libSystem.B.dylib

Symbol not found: _pthread_set_qos_class_self_np
Referenced from: /Users/USER/Downloads/java/jre.1.8.0_201.jre/Contents/Home/lib/libjfxwebkit.dylib
Expected in: /usr/lib/libSystem.B.dylib
It's can be java download problem/broken.

Download launcher file from xmage.de, PUT that file to new folder like /Users/USER/games/xmage/
Run that launcher file and update. That's must fix java files in game folder.

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 04 Aug 2019, 16:49
by illuknisaa
Marchesa, the Black Rose is bugged. If she and other creatures with counters die at the same time (due to a boardwipe or something) only she returns and nothing else.

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 08 Aug 2019, 05:27
by Lord0fHam
During a 3 player game of commander, a player cast Kaya's Ghostform on a Seedborn Muse. The Kaya's Ghostform was destroyed using Aura of Silence. After this ability resolved, the Seedborn Muse was exiled with Path to Exile. Once that resolved, the Seedborn Muse was still returned to the battlefield even though Kaya's Ghostform had been destroyed.

multi player AI only 1 AI graveyard accessible

PostPosted: 14 Aug 2019, 21:19
by JoeMoyle
Hi Devs,

First let me say thank you for making xMage. Great job. Onto the bug. I'm playing against 2 AI players. Only one of those players grave yards show up when clicking a grave yard. The other shows up empty when opening it no matter how many cards may be in it. Makes it so cards that pull from an opponents grave don't work except against one of the two AI players. Makes it so that cards like Necromantic Selection freeze the game if 1 AI player is dead and the remaining one is the one with no graveyard access. This has been a bug for many versions for many months as far back as I can recall.

Joe Moyle

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 15 Aug 2019, 03:23
by sudsmcduff
"Nix" is not countering Hogaak, Arisen Necropolis. It should.

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 17 Aug 2019, 01:32
by protective1
I was playing against AI. I got "has run out of time, losing the match". However, I was not idle when this happened. From the game log:

<font color="#CCCC33">9:17 PM: </font><font color="#20B2AA">m</font><font color="Orange">
has joined the game</font>
...
...
<font color="#CCCC33">9:22 PM: </font><font color="#20B2AA">computer</font><font color="White">
attacks with 1 creature</font>
<font color="#CCCC33">9:22 PM: </font><font color="#20B2AA">m</font><font color="White">
has lost the game.</font>
<font color="#CCCC33">9:22 PM: </font><font color="#20B2AA">m</font><font color="White">
has run out of time, losing the match.</font>
<font color="#CCCC33">9:22 PM: </font><font color="#20B2AA">computer</font><font color="White">
has won the game</font>

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 20 Aug 2019, 05:35
by jerryrider
XMage Launcher works just fine. Application starts up in Java, connect to Xmage.de - "Application Not Responding" in OSX Mojave every. damn. time. It's been 6 months of this and now I'd really like to get back into testing and hoping someone has found a workaround. Uninstalled and reinstalled full package. Running out of desktop XMAGE folder created for this purpose.

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 20 Aug 2019, 07:22
by Fuistus
There's a bug with watcher for tomorrow. When it quits the battlefield, the hideaway trigger goes in the stack but you never get the card in your hand

Re: Bug Reports XMage 1.4.37 SOFTWARE

PostPosted: 26 Aug 2019, 17:36
by Tharkon
An error has occurred on the MAGE server. Your last action will be rollbacked.
Please post the following report here: http://www.slightlymagic.net/forum/post ... =70&t=3116
The above mentioned topic was locked so I couldn't post there.
This is the report that happened during a game between 1 player and 2 AI's right as one of the AI's turns was starting.

Game exception occurred: mage.MageException: Iterated player priority after game exception too often, game ends!
Server version: 1.4.37V4 (build: 2019-07-13 15:59)
mage.game.GameImpl.playPriority(GameImpl.java:1292)
mage.game.turn.Step.priority(Step.java:61)
mage.game.turn.Phase.playStep(Phase.java:184)
mage.game.turn.Phase.play(Phase.java:89)
mage.game.turn.Turn.play(Turn.java:126)
mage.game.GameImpl.playTurn(GameImpl.java:850)
mage.game.GameImpl.play(GameImpl.java:759)
mage.game.GameImpl.start(GameImpl.java:723)
mage.server.game.GameWorker.call(GameWorker.java:34)
java.util.concurrent.FutureTask.run(FutureTask.java:266)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
java.lang.Thread.run(Thread.java:748)