Page 1 of 2
Bug Reports XMage 1.4.44 SOFTWARE

Posted:
10 Jul 2020, 16:28
by JayDi
If you have encountered any problems while using XMage 1.4.44 you can post them here.
Please mention who you were playing against: Human or the AI type.
Please describe how you got to that point. A screenshot of the battlefield at the moment something went wrong will be useful too. Otherwise, naming the cards that interacted will suffice. If you get an error log please add that too. Also often does a gamelog file from the mage-client/gamelogs/ folder help to reproduce the problem.
- Please use a separate post for each problem/bug.
- Don't report here problems concerning to install, start or connect xmage. Only game related problems of using xmage.
- Don't report here cards you would like to see implemented. Please report those card requests here:
http://www.slightlymagic.net/forum/viewtopic.php?f=70&t=19067
Thank you for your help in detecting bugs.Known Issues:https://github.com/magefree/mage/issuesAlready fixed but not available until the next XMage updateLook here before you post and describe a problem. Often the problems are already fixed and you only have to wait for the next update. If your problem is already mentioned as solved, there is no need to post it in this thread again.
See here:
https://github.com/magefree/mage/wiki/Features-and-fixes-not-released-yet
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
11 Jul 2020, 04:52
by CumCaptain
There are mill cards that are not working with Bruvac, traumatize is one of the more important ones that come to mind.
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
14 Jul 2020, 01:34
by catman123456
palace siege is not getting the k'rrik reduction
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
14 Jul 2020, 18:34
by Lucky13
The AI doesn't know how to use
Odric, Master Tactician whe its ability triggers and just stops working
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
17 Jul 2020, 19:29
by TheDeathryder
I've been having issues with
Mindslaver and Emrakul the Promised End vs the AI. When I move to take control of the opponent AI's turn, I'm able to view their hand, but the AI still controls all actions instead of allowing me to dictate what plays are made.
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
17 Jul 2020, 20:09
by pleaseaziz
Not a bug strictly speaking, but I just downloaded the xmage launcher from xmage.de and it does not contain the mage-client and mage-server directories, nor the startClient.sh and startServer.sh launch files that the installation instructions tell me to expect. What's going on here? I downloaded this same jar file on a different computer a couple months ago and had no issues. This directory structure doesn't look at all familiar. How can I launch xmage on Linux without those sh files?
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
18 Jul 2020, 20:38
by JayDi
pleaseaziz wrote:Not a bug strictly speaking, but I just downloaded the xmage launcher from xmage.de and it does not contain the mage-client and mage-server directories, nor the startClient.sh and startServer.sh launch files that the installation instructions tell me to expect. What's going on here? I downloaded this same jar file on a different computer a couple months ago and had no issues. This directory structure doesn't look at all familiar. How can I launch xmage on Linux without those sh files?
xmage.de contains only launcher file. So you must run that launcher.jar and it downloads all other files too. Also you can manually download files from
https://github.com/magefree/mage/releases , unpack it and run custom sh scripts.
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
19 Jul 2020, 15:15
by tuberov
Opponent cast Kroxa, Titan of Hunger's Deat from exile via a cascade trigger and it stayed on the battlefield rather than being sacrificed to it's own ETB trigger.
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
23 Jul 2020, 16:48
by TheDeathryder
Bronze Bombshell equipped with
Assault Suit doesn't trigger the Bombshell's state based action to end the game in a draw when given to another player. Instead, the ability triggers once, resolves, then never triggers again after initial resolution. This was discovered vs the AI in commander free for all.
In the same game,
Assault Suit did not prevent the sacrifice of equipped DanDan.
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
23 Jul 2020, 22:02
by AlexUNLIMITED
I can choose Jegantha as a companion even with a
Walking Ballista in the deck from the g2.
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
24 Jul 2020, 05:47
by WinglessTension
Having an issue in sealed where one player will load into the match but the other won't. Both of us submit our decks but only one loads in, the announcement bar on the right says it will resend the game invite after 120 seconds but even after waiting long after that nothing will happen. Any fix?
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
26 Jul 2020, 03:09
by robotabc773
Unesh, Criosphinx Sovereign doesn't allow me to choose which opponent creates the piles. Instead it always gives the choice to the next player in the turn order.
EDIT: This was not against AI
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
30 Jul 2020, 17:19
by Nerava
A friend used
Eternal Dominion to put into play
Propaganda and
Mirrormade, copying
Propaganda.
The copy of
Propaganda required infinite payments of 2 mana to attack with a single creature, making him completely immune to attack.
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
31 Jul 2020, 23:16
by CooperKid
The Ur-Dragon's command zone ability is not working, as of the last update.
Ability reads: As long as
The Ur-Dragon is in the command zone or on the battlefield, dragon spells you cast cost 1 less to cast.
I've played a few games and the ability is not working at all, wherever
The Ur-Dragon is my dragon spells cost their full casting cost.
Re: Bug Reports XMage 1.4.44 SOFTWARE

Posted:
01 Aug 2020, 18:38
by illuknisaa
You can't cast multiple spells with Karador in the same turn. If karador leaves the battlefield and them comes back you should be able to cast another creature because karador is a new object.
Fixed with the next update.