Bug Reports xmage 1.4.12
by BetaSteward
Moderators: North, BetaSteward, noxx, jeffwadsworth, JayDi, TheElk801, LevelX, CCGHQ Admins
Re: Bug Reports xmage 1.4.12
by Deanwinchester » 06 Jul 2016, 16:25
can't cast Demonic Dread at all.
jeffwadsworth: Works fine for me. Are you sure that you had a valid target available? If not, you can't cast it.
jeffwadsworth: Works fine for me. Are you sure that you had a valid target available? If not, you can't cast it.
- Deanwinchester
- Posts: 1
- Joined: 06 Jul 2016, 16:21
- Has thanked: 0 time
- Been thanked: 0 time
Re: Bug Reports xmage 1.4.12
by Professor Chronotis » 07 Jul 2016, 16:01
Shared Fate does not work as intended.
When it is in play each player should be effectively "drawing" out of their opponent's deck. The "drawn" cards should be exiled face-down, yet remain visible and playable to one player (effectively making the exiled cards behave as a second "hand").
Everything works great, except neither player can see their "new hand". The exiled cards appear face-down to all viewers. Note that the cards are in fact playable - so currently we are forced to put each face-down card onto the stack to figure out what's in our hands. This is less than ideal not only because we have to remember our cards and their positions in our hand, but it also means that the content of our new hand is visible to our opponents because the stack is a public zone!
Please fix Shared Fate so we can see our new hands.
Thank you so much.
When it is in play each player should be effectively "drawing" out of their opponent's deck. The "drawn" cards should be exiled face-down, yet remain visible and playable to one player (effectively making the exiled cards behave as a second "hand").
Everything works great, except neither player can see their "new hand". The exiled cards appear face-down to all viewers. Note that the cards are in fact playable - so currently we are forced to put each face-down card onto the stack to figure out what's in our hands. This is less than ideal not only because we have to remember our cards and their positions in our hand, but it also means that the content of our new hand is visible to our opponents because the stack is a public zone!
Please fix Shared Fate so we can see our new hands.

Thank you so much.
- Professor Chronotis
- Posts: 3
- Joined: 07 Jul 2016, 15:48
- Has thanked: 0 time
- Been thanked: 0 time
Re: Bug Reports xmage 1.4.12
by Doctor Weird » 07 Jul 2016, 16:59
Shared Fate's comment @ line 163 says:Professor Chronotis wrote:Shared Fate does not work as intended.
That's probably the problem.// You already get asked to confirm when casting a spell, but not when playing a land.
Right now, if you click on a card exiled with Shared Fate and it's a land it will open a second pop-up window showing the card and you're asked if you want to play [land name], which is fine, but if the card is not a land it will immediately be put on the stack (if it's legal to play the card at that time, of course) and you're asked to pay its mana cost.
Simplest solution is probably to just remove the land criteria when deciding whether or not to ask "Play (...)?" and have it ask regardless (line 164).
- Doctor Weird
- Posts: 180
- Joined: 25 May 2015, 01:33
- Has thanked: 7 times
- Been thanked: 52 times
Re: Bug Reports xmage 1.4.12
by Professor Chronotis » 07 Jul 2016, 19:27
Thanks for the quick reply, and for posting the code.
Removing the land criterion from line 164 would indeed solve the problem, although just barely. It would still be necessary to click on each card to find out what it is, click cancel to avoid playing it, and then remember its position in your hand lest you have to click on it some more later. All this clicking sounds cumbersome.
It would be nice if there was a way to reveal to players the cards which are face-down in their own exile piles, while keeping the face-down cards in opponents' exile piles hidden. I'm no Java programmer, but I would wager that if this is to be accomplished it would require an extra line of code (or two?) between lines 113 and 114. Even if it just enabled players to mouse-over their own cards and see what they are rather than "face-down card", that would be immensely beneficial.
Removing the land criterion from line 164 would indeed solve the problem, although just barely. It would still be necessary to click on each card to find out what it is, click cancel to avoid playing it, and then remember its position in your hand lest you have to click on it some more later. All this clicking sounds cumbersome.
It would be nice if there was a way to reveal to players the cards which are face-down in their own exile piles, while keeping the face-down cards in opponents' exile piles hidden. I'm no Java programmer, but I would wager that if this is to be accomplished it would require an extra line of code (or two?) between lines 113 and 114. Even if it just enabled players to mouse-over their own cards and see what they are rather than "face-down card", that would be immensely beneficial.
- Professor Chronotis
- Posts: 3
- Joined: 07 Jul 2016, 15:48
- Has thanked: 0 time
- Been thanked: 0 time
Re: Bug Reports xmage 1.4.12
by Doctor Weird » 07 Jul 2016, 20:01
Cards with Morph or Megamorph already have something similar, where hovering over the face down card shows the tool-tip text of the card, scrolling up shows the morph reminder token image, and scrolling down shows the actual card image.Professor Chronotis wrote:Even if it just enabled players to mouse-over their own cards and see what they are rather than "face-down card"
- Doctor Weird
- Posts: 180
- Joined: 25 May 2015, 01:33
- Has thanked: 7 times
- Been thanked: 52 times
Re: Bug Reports xmage 1.4.12
by jeffwadsworth » 08 Jul 2016, 13:40
Ruling from 7/18/2014:tuberov wrote:While playing a game of EDH, I had an Everglades on the field with a Caged Sun set on black and Urborg, Tomb of Yawgmoth. Hovering the mouse over Everglades tells me it two colorless (one old colorless symbol, one new one) or one B mana. The card is printed to add 1B (or B if tapped as an ordinary Swamp).
Urborg’s ability causes each land on the battlefield to have the land type Swamp. Each land thus has the ability “{T}: Add

Last edited by jeffwadsworth on 08 Jul 2016, 15:35, edited 2 times in total.
- jeffwadsworth
- Super Tester Elite
- Posts: 1172
- Joined: 20 Oct 2010, 04:47
- Location: USA
- Has thanked: 287 times
- Been thanked: 70 times
Re: Bug Reports xmage 1.4.12
by ShivaFang » 08 Jul 2016, 13:50
The console threw an error at me related to Dragon Hunter blocking a flying dragon.
This happened in a simulation game while I was testing AI - so I don't know if the block was prevented or not because I couldn't see the results.
This happened in a simulation game while I was testing AI - so I don't know if the block was prevented or not because I couldn't see the results.
- Code: Select all
WARN 2016-07-08 07:47:13,546 Found non-flying non-reach creature blocking creature with flying =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombatIfNeeded
ERROR 2016-07-08 07:47:13,547 > Tracing game state... =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,547 > <font color='#F0E68C'>Dragon Hunter [53c]</font> could block <font color='#DAA520'>Dragonlord Silumgar [82d]</font> =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,547 > =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,547 > Attacker abilities: =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,547 > Cast Dragonlord Silumgar, id=2513ed9f-f8af-4247-be08-d871122993d1 =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,547 > Flying, id=2d47d1a2-f6d8-4cf4-be6c-1c608dfb3eb7 =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,547 > Deathtouch <i>(Any amount of damage this deals to a creature is enough to destroy it.)</i>, id=7789da77-7dfe-4161-a6e4-c875b2b1b56f =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,548 > When {this} enters the battlefield, gain control of target creature or planeswalker for as long as you control {this}., id=8ab3eb2d-3231-46d3-8615-9a82604aaf9c =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,548 > Blocker abilities: =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,548 > Cast Dragon Hunter, id=752eb47c-3ba8-4bc2-8891-7a3f78f272d6 =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,548 > Protection from Dragons, id=d1f80f2a-6478-4f35-909a-5adf70e54d3b =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,548 > {this} can block Dragons as though it had reach., id=2f3256e4-c54e-4b40-8d1b-da4c4ee9f29c =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,548 > =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,548 > Flying ability id: 2d47d1a2-f6d8-4cf4-be6c-1c608dfb3eb7 =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,548 > Reach ability id: 40f68ed5-21ac-4db3-bad1-bcd1527146e0 =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,549 > Intimidate ability id: d972d6c4-5c03-4835-b7de-e80eaa278845 =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,549 > =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,549 > Restriction effects: =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,549 > Applied to ATTACKER: =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,549 > mage.abilities.keyword.FlyingEffect@17499ea =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,549 > id=e322a2be-a7bd-4236-8631-57f19e8f9754 =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,549 > ability=Flying =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,549 > Applied to BLOCKER: =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,549 > =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,550 > List of all restriction effects: =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,550 > mage.abilities.keyword.FlyingEffect@17499ea =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,550 > id=e322a2be-a7bd-4236-8631-57f19e8f9754 =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,550 > =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,550 > Trace Attacker: =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,550 > effect=mage.abilities.keyword.FlyingEffect@17499ea id=e322a2be-a7bd-4236-8631-57f19e8f9754 =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceForPermanent
ERROR 2016-07-08 07:47:13,550 > ability=Flying, applies_to_attacker=true =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceForPermanent
ERROR 2016-07-08 07:47:13,550 > =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,550 > Trace Blocker: =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceCombat
ERROR 2016-07-08 07:47:13,551 > effect=mage.abilities.keyword.FlyingEffect@17499ea id=e322a2be-a7bd-4236-8631-57f19e8f9754 =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceForPermanent
ERROR 2016-07-08 07:47:13,551 > instanceof StaticAbility: true, ability=Flying =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceForPermanent
ERROR 2016-07-08 07:47:13,551 > usable zone: false, ability=Flying =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceForPermanent
ERROR 2016-07-08 07:47:13,551 > zone: ALL =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceForPermanent
ERROR 2016-07-08 07:47:13,551 > object: null =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceForPermanent
ERROR 2016-07-08 07:47:13,551 > test_zone: null =>[GAME f4aa1225-43d3-40f5-9d1f-e13ea5a982ff] TraceUtil.traceForPermanent
ERROR 2016-07-08 07:47:13,551 >
Re: Bug Reports xmage 1.4.12
by rigeld2 » 08 Jul 2016, 16:13
Right. He's saying the tooltip for Everglades is showing that it taps forjeffwadsworth wrote:Ruling from 7/18/2014:tuberov wrote:While playing a game of EDH, I had an Everglades on the field with a Caged Sun set on black and Urborg, Tomb of Yawgmoth. Hovering the mouse over Everglades tells me it two colorless (one old colorless symbol, one new one) or one B mana. The card is printed to add 1B (or B if tapped as an ordinary Swamp).
Urborg’s ability causes each land on the battlefield to have the land type Swamp. Each land thus has the ability “{T}: Addto your mana pool.” Nothing else changes about those lands, including their names, other subtypes, other abilities, and whether they’re legendary or basic.





Re: Bug Reports xmage 1.4.12
by jeffwadsworth » 08 Jul 2016, 19:31
Check the attachment for what my client displays.rigeld2 wrote:Right. He's saying the tooltip for Everglades is showing that it taps forjeffwadsworth wrote:Ruling from 7/18/2014:tuberov wrote:While playing a game of EDH, I had an Everglades on the field with a Caged Sun set on black and Urborg, Tomb of Yawgmoth. Hovering the mouse over Everglades tells me it two colorless (one old colorless symbol, one new one) or one B mana. The card is printed to add 1B (or B if tapped as an ordinary Swamp).
Urborg’s ability causes each land on the battlefield to have the land type Swamp. Each land thus has the ability “{T}: Addto your mana pool.” Nothing else changes about those lands, including their names, other subtypes, other abilities, and whether they’re legendary or basic.
{C} or
when it should show that it taps for
![]()
or
.
- jeffwadsworth
- Super Tester Elite
- Posts: 1172
- Joined: 20 Oct 2010, 04:47
- Location: USA
- Has thanked: 287 times
- Been thanked: 70 times
Re: Bug Reports xmage 1.4.12
by Doctor Weird » 08 Jul 2016, 20:57
Everglades' bug was fixed already by LevelX 18 days ago, there just hasn't been a new version released to the public yet since then, and I'm guessing jeff is using a client with said fix off GitHub, which is why it displays the correct mana for him. By the way, both Urborg, Tomb of Yawgmoth and Caged Sun were irrelevant here, the problem was just Everglades adding two colorless mana instead of one colorless and one black.jeffwadsworth wrote:Check the attachment for what my client displays.
Attachment for reference.
- Doctor Weird
- Posts: 180
- Joined: 25 May 2015, 01:33
- Has thanked: 7 times
- Been thanked: 52 times
Re: Bug Reports xmage 1.4.12
by jeffwadsworth » 08 Jul 2016, 23:08
All you needed to do was post the bugfix. Cheers.Doctor Weird wrote:Everglades' bug was fixed already by LevelX 18 days ago, there just hasn't been a new version released to the public yet since then, and I'm guessing jeff is using a client with said fix off GitHub, which is why it displays the correct mana for him. By the way, both Urborg, Tomb of Yawgmoth and Caged Sun were irrelevant here, the problem was just Everglades adding two colorless mana instead of one colorless and one black.jeffwadsworth wrote:Check the attachment for what my client displays.
Attachment for reference.
- jeffwadsworth
- Super Tester Elite
- Posts: 1172
- Joined: 20 Oct 2010, 04:47
- Location: USA
- Has thanked: 287 times
- Been thanked: 70 times
Re: Bug Reports xmage 1.4.12
by Zakading » 08 Jul 2016, 23:46
This is concerning Angelic Skirmisher. The bug has been around for a bit and I figured I might as well report it now.
It occurs when the combat step starts and its effect would normally triggers and efficiently crashes the entire application.
I would love to post the error log, as image or directly, though the spam prevention will not let me.
It occurs when the combat step starts and its effect would normally triggers and efficiently crashes the entire application.
I would love to post the error log, as image or directly, though the spam prevention will not let me.
- Zakading
- Posts: 8
- Joined: 23 Mar 2016, 15:45
- Has thanked: 0 time
- Been thanked: 0 time
Re: Bug Reports xmage 1.4.12
by booot » 09 Jul 2016, 08:58
While I activating ability, I rollback game so game in bugging...
Re roll back so fixs.
https://youtu.be/SGxKZl6vFkA
Re roll back so fixs.
https://youtu.be/SGxKZl6vFkA
- booot
- Posts: 67
- Joined: 19 Oct 2015, 19:00
- Has thanked: 0 time
- Been thanked: 0 time
Re: Bug Reports xmage 1.4.12
by booot » 09 Jul 2016, 09:57
Inescapable Brute's second ability not working, and tooltip is missing.
- booot
- Posts: 67
- Joined: 19 Oct 2015, 19:00
- Has thanked: 0 time
- Been thanked: 0 time
Re: Bug Reports xmage 1.4.12
by ShivaFang » 10 Jul 2016, 15:24
Just got this;
- Code: Select all
FATAL 2016-07-10 09:20:34,526 Error in rule text generation of Ruinous Path with awaken: Create a bug report or fix the source code =>[GAME 19e68b98-4558-438a-b72e-b6f41a571592] AbilitiesImpl.getRules
Who is online
Users browsing this forum: No registered users and 10 guests