Re: Bug Reports (snapshot builds)
Posted: 17 Feb 2014, 14:51Thanks. Yea it was using devmode. It's much easier to test new cards this way, so I'm glad it works as I expect when going through this route.
Collectible Card Game Headquarters
High Quality Resources for Collectible Card Games and Home of the CCGHQ Team
https://www.slightlymagic.net/forum/
Bug Reports (snapshot builds)
https://www.slightlymagic.net/forum/viewtopic.php?f=52&t=6333
Page 187 of 487
Posted: 17 Feb 2014, 14:51Re: Bug Reports (snapshot builds)
Posted: 17 Feb 2014, 23:16r24884
Quest Mode Matches seem to be broken currently. As soon as the game starts (after mulliganing) the game ends and I'm told I won (Actually looking at the log, we both win and lose simultaneously). Then when the next game starts, I'm told I lost the last game and asked if I want to play/draw. Then when that game starts I get this crash:
java.lang.NullPointerException
at forge.gui.match.QuestWinLose.awardEventCredits(QuestWinLose.java:328)
at forge.gui.match.QuestWinLose.populateCustomPanel(QuestWinLose.java:157)
at forge.gui.match.ViewWinLose.<init>(ViewWinLose.java:116)
at forge.control.FControlGameEventHandler$6.run(FControlGameEventHandler.java:145)
I guess because the loss states are all messed up.
Quest Mode Matches seem to be broken currently. As soon as the game starts (after mulliganing) the game ends and I'm told I won (Actually looking at the log, we both win and lose simultaneously). Then when the next game starts, I'm told I lost the last game and asked if I want to play/draw. Then when that game starts I get this crash:
java.lang.NullPointerException
at forge.gui.match.QuestWinLose.awardEventCredits(QuestWinLose.java:328)
at forge.gui.match.QuestWinLose.populateCustomPanel(QuestWinLose.java:157)
at forge.gui.match.ViewWinLose.<init>(ViewWinLose.java:116)
at forge.control.FControlGameEventHandler$6.run(FControlGameEventHandler.java:145)
I guess because the loss states are all messed up.
Re: Bug Reports (snapshot builds)
Posted: 17 Feb 2014, 23:39Description: I WAS USSING THE DECK EDITOR
- UncheckedExecutionException | Open
Re: Bug Reports (snapshot builds)
Posted: 18 Feb 2014, 01:18Sorry, that must have been me trying to get team victories working. I won't be on again until Wednesday, but r24881 and r24882 need to be reverted. Alternatively, I think the issue is that I checked the team values against -1, which works great with constructed matches because they assign team numbers, but -1 was the default value for team before.friarsol wrote:r24884
Quest Mode Matches seem to be broken currently. As soon as the game starts (after mulliganing) the game ends and I'm told I won (Actually looking at the log, we both win and lose simultaneously). Then when the next game starts, I'm told I lost the last game and asked if I want to play/draw. Then when that game starts I get this crash:
java.lang.NullPointerException
at forge.gui.match.QuestWinLose.awardEventCredits(QuestWinLose.java:328)
at forge.gui.match.QuestWinLose.populateCustomPanel(QuestWinLose.java:157)
at forge.gui.match.ViewWinLose.<init>(ViewWinLose.java:116)
at forge.control.FControlGameEventHandler$6.run(FControlGameEventHandler.java:145)
I guess because the loss states are all messed up.
So either revert or try change GameOutcome.getWinningTeam to return 0 instead, and in ViewWinLose compare winningTeam != 0. Or if anyone can implement team victories better, that would be awesome.
Re: Bug Reports (snapshot builds)
Posted: 18 Feb 2014, 01:47I'll take a look marc. It should be simpler to just make sure all Players end up on different teams even if they don't go through the Constructed match UI.
Re: Bug Reports (snapshot builds)
Posted: 18 Feb 2014, 02:27r24886
Rite of Passage doesn't seem to interact with Persist creatures dying due to damage, when they return to the battlefield the Rite trigger still affects them even though they are a different game object. This pretty apparent playing against the Apu Quest deck.
Rite of Passage doesn't seem to interact with Persist creatures dying due to damage, when they return to the battlefield the Rite trigger still affects them even though they are a different game object. This pretty apparent playing against the Apu Quest deck.
Re: Bug Reports (snapshot builds)
Posted: 18 Feb 2014, 02:55Hey Max, what's the deal with checkin 24886? That's kind of a cryptic description, and now I'm playing against Treebard Quest deck, and he has a Bosk Banneret in play and 3 lands and is tapping out during M2, but not casting any cards. I looked at the AIs hand and he has two 5 CMC cards in hand. Was this intentionally put in to test some code?
It looks like cards are being just.. removed from his hand and not going anywhere in these circumstances?
It looks like cards are being just.. removed from his hand and not going anywhere in these circumstances?
Re: Bug Reports (snapshot builds)
Posted: 18 Feb 2014, 09:09The objective of this change is to have AI tests use a separate list of mana. (not the one returned by sa.getPayingMana())
That what you've seen is a rare situation when AI though it would be able to pay the mana cost but apparently could not.
That what you've seen is a rare situation when AI though it would be able to pay the mana cost but apparently could not.
Re: Bug Reports (snapshot builds)
Posted: 18 Feb 2014, 11:55Prompt string "Multikicker for" didn't show up for multikicker cards.
Re: Bug Reports (snapshot builds)
Posted: 18 Feb 2014, 13:03Well, it seemed to be happening everytime the AI tried to cast something that match when he had a cost reducing permanent in play, where the cost reduction was being used to cast the spell (3 mana available from lands, cost reduced by 1, cmc 4), which isn't the most common scenario, but I also wouldn't necessarily call it rare.Max mtg wrote:That what you've seen is a rare situation when AI though it would be able to pay the mana cost but apparently could not.
Re: Bug Reports (snapshot builds)
Posted: 18 Feb 2014, 13:21AI Commander doesn't suffer the cost raise effect. It's very unfairMax mtg wrote:The objective of this change is to have AI tests use a separate list of mana. (not the one returned by sa.getPayingMana())
That what you've seen is a rare situation when AI though it would be able to pay the mana cost but apparently could not.
Re: Bug Reports (snapshot builds)
Posted: 18 Feb 2014, 23:35Yes, AI had some incorrect cost calculation code. I believe I've fixed it (24901)
There's another bug, that is quite puzzling for me:
Give AI Goblin Electromancer, put an Island into play for AI, add Mana Leak to its hand. The cast some spell so that AI could counter.
The strange point here is that I am asked to pay
- not 
as the card rules read. Was the cost of 'unless its contoller pays ' reduced by Goblin Electromancer?
There's another bug, that is quite puzzling for me:
Give AI Goblin Electromancer, put an Island into play for AI, add Mana Leak to its hand. The cast some spell so that AI could counter.
The strange point here is that I am asked to pay
- not as the card rules read. Was the cost of 'unless its contoller pays ' reduced by Goblin Electromancer?Re: Bug Reports (snapshot builds)
Posted: 19 Feb 2014, 00:02The Electromancer definitely shouldn't be reducing the unless cost. I just downloaded the last release (1.5.12), and when Mana Leak is played in this scenario I'm prompted to pay 3, so something since the release is causing that issue.Max mtg wrote:Yes, AI had some incorrect cost calculation code. I believe I've fixed it (24901)
There's another bug, that is quite puzzling for me:
Give AI Goblin Electromancer, put an Island into play for AI, add Mana Leak to its hand. The cast some spell so that AI could counter.
The strange point here is that I am asked to pay
Re: Bug Reports (snapshot builds)
Posted: 23 Feb 2014, 06:27r24942: I noticed a UI issue with the deck viewer: the deck viewer changes its size when you look at different cards, so it becomes bigger and smaller all the time, which is quite irritating. I think this is caused by the card detail box shrinking and enlarging depending on the length of the card name (as far as I could tell). A good way to reproduce: load some Mono-Blue Devotion deck, such as the one by Pierre Dagen from Pro Tour Theros, for viewing in the deck viewer (e.g. double-click it in the Constructed deck list). Look at Master of Waves and then at Thassa, God of the Sea.
- Agetian
- Agetian
Re: Bug Reports (snapshot builds)
Posted: 23 Feb 2014, 14:13I hope this is no longer an issue after r24950.friarsol wrote:The Electromancer definitely shouldn't be reducing the unless cost. I just downloaded the last release (1.5.12), and when Mana Leak is played in this scenario I'm prompted to pay 3, so something since the release is causing that issue.Max mtg wrote:Yes, AI had some incorrect cost calculation code. I believe I've fixed it (24901)
There's another bug, that is quite puzzling for me:
Give AI Goblin Electromancer, put an Island into play for AI, add Mana Leak to its hand. The cast some spell so that AI could counter.
The strange point here is that I am asked to pay