Collectible Card Game Headquarters

Today I saw Kiora, the Crashing Wave 's emblem show the card pic itself in the Command zone rather than the token pic for the specific emblem.

Here's an unusual hang bug when the game is supposed to end with a victory but it doesn't go to the end game screen and ends up hanging in that "Waiting for opponent" state. This appears to be different from the "declare attackers" phase "Waiting for opponent" bug that sometimes happens when using E.

This particular situation was induced twice on a Mac OS X system within the last week or so, once on the previous version of the game (1.5.24) and once on the latest version of the game (1.5.25). The phases in the last turn were skipped with Space, pretty sure the End Turn button wasn't used. After the opponent was dealt critical damage and the victory message was shown in the log, the game did not proceed to the end game screen, instead hanging on the battlefield. Clicking anything on the screen did not help (tried clicking all the cards, all the buttons, all the phases, etc., and also all the buttons in the dock - clicking "End Turn" in the dock resulted in the "Cannot pass priority at this time" message appearing on the screen). The only way to proceed was to force-quit Forge and restart.

Interestingly, this issue did not (yet?) happen to me on Linux platform. It may or may not be platform-specific.

Here are the screenshots showing the hung Forge screen upon winning (#1) and also the "Cannot pass priority" message after clicking End Turn in the dock (#2).





- Agetian

I think that there is still another buggy Zendikar-block card (or M12?) out there.
The game tends to crash during quite some quest-draft tournaments.
Underneath is a crash report and a screenshot- I just cannot tell what exactly has happened 'cause I've been rushing through the game at 10x-speed, but the log is visible.
report:

NullPointerException | Open

Code: Select all

Forge Version:    1.5.24-r27072
Operating System: Windows 7 6.1 x86
Java Version:     1.7.0_67 Oracle Corporation

java.lang.NullPointerException
   at forge.game.ability.AbilityUtils.applyAbilityTextChangeEffects(AbilityUtils.java:1521)
   at forge.game.ability.AbilityUtils.getDefinedCards(AbilityUtils.java:84)
   at forge.ai.ComputerUtilCombat.predictPowerBonusOfAttacker(ComputerUtilCombat.java:1133)
   at forge.ai.ComputerUtilCombat.damageIfUnblocked(ComputerUtilCombat.java:127)
   at forge.ai.AiAttackController.doesHumanAttackAndWin(AiAttackController.java:404)
   at forge.ai.AiAttackController.notNeededAsBlockers(AiAttackController.java:316)
   at forge.ai.AiAttackController.declareAttackers(AiAttackController.java:840)
   at forge.ai.AiController.declareAttackers(AiController.java:1126)
   at forge.ai.PlayerControllerAi.declareAttackers(PlayerControllerAi.java:405)
   at forge.game.phase.PhaseHandler.declareAttackersTurnBasedAction(PhaseHandler.java:474)
   at forge.game.phase.PhaseHandler.onPhaseBegin(PhaseHandler.java:291)
   at forge.game.phase.PhaseHandler.startFirstTurn(PhaseHandler.java:1060)
   at forge.game.GameAction.startGame(GameAction.java:1558)
   at forge.game.Match.startGame(Match.java:81)
   at forge.control.FControl$4.run(FControl.java:442)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)

screenshot:

| Open

Edit: Sorry, I didn't see that I still have version 1.24.

Symphonic wrote:The game tends to crash during quite some quest-draft tournaments.

NullPointerException | Open

[code]
Forge Version: 1.5.24-r27072

Please don't report bugs from old versions, I have a fairly lengthy article about how we request users post bugs in my signature.

I'm very pleased with the new auto yield feature, especially how it applies to every instance of that ability regardless of its source; it makes managing the stack much quicker. A note, though, if the stack contains other copies of the top ability, and "auto yield" is clicked on one other than the one at the top of the stack, the game will not notice that the ability on top of the stack is now flagged to auto yield.

E.g., if you have 2 Arcbound Crusher on the field and play an artifact, and then right-click the lower of the 2 triggered abilities on the stack to auto yield, the game will not proceed even though the top ability is now also flagged to auto yield.

So, this time I should have been using the right version^^.
The opponent attacked with its Cadaver Imp into my Lightmine Field.
report:

| Open

Forge Version: 1.5.25-r27161Mu (mixed revisions detected; please update from the root directory)
Operating System: Windows 7 6.1 x86
Java Version: 1.7.0_67 Oracle Corporation

java.util.ConcurrentModificationException
at java.util.ArrayList$Itr.checkForComodification(Unknown Source)
at java.util.ArrayList$Itr.next(Unknown Source)
at forge.screens.match.controllers.CCombat.getCombatDescription(CCombat.java:104)
at forge.screens.match.controllers.CCombat.update(CCombat.java:49)
at forge.screens.match.CMatchUI.showCombat(CMatchUI.java:305)
at forge.GuiDesktop.showCombat(GuiDesktop.java:383)
at forge.control.FControlGameEventHandler$2.run(FControlGameEventHandler.java:63)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$200(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
[/code]

screenshot:

| Open

Kodama of the Center Tree no longer has P/T based on the number of Spirits and instead has 0/0 (normally resulting in instant death). I know this card worked correctly a few versions back, but it looks like the part of the ability which defines the value to set the P/T is now missing from the card file.

Nekoatl wrote:Kodama of the Center Tree no longer has P/T based on the number of Spirits and instead has 0/0 (normally resulting in instant death). I know this card worked correctly a few versions back, but it looks like the part of the ability which defines the value to set the P/T is now missing from the card file.

Is it just displaying as 0/0 on the overlay, or does is it actually being treated as though it was 0/0. If so, it should not even stay on the field.

I ask partly because I recently saw Clone-type cards displaying 0/0 on their overlay instead of the copied creature's P/T, and this may be a related bug.

drdev wrote:Is it just displaying as 0/0 on the overlay, or does is it actually being treated as though it was 0/0. If so, it should not even stay on the field.

It says 0/0 while in your hand and dies instantly when cast.

I came across a rather unusual and frustrating bug: the AI attacked me with Alms Beast, I was the defending player. I blocked with Myr Welder and brought it back to life with Nim Deathmantle, but the AI got rid of it with Condemn even though I was on the defense. I noticed that my Myr Welder got erroneously flagged as attacking at the moment when Condemn resolved (had the attacker icon and all), possibly a bug in Deathmantle itself? Or in the related code?

Screenshots attached. Note that I'm the one being attacked, not the attacker. On screenshot #2 you can clearly see Condemn being cast, as well as an erroneous "attacker" icon put over my defending (blocking) creature.




- Agetian

Agetian wrote:I came across a rather unusual and frustrating bug: the AI attacked me with Alms Beast, I was the defending player. I blocked with Myr Welder and brought it back to life with Nim Deathmantle, but the AI got rid of it with Condemn even though I was on the defense. I noticed that my Myr Welder got erroneously flagged as attacking at the moment when Condemn resolved (had the attacker icon and all), possibly a bug in Deathmantle itself? Or in the related code?

ok, I can definitely repro this. It's a very odd scenario and both the Alms Beast and the Nim Deathmantle are important for the repro.

I'll see if I can figure out a fix.

Edit: Ok, should be fixed now.

Intet, the Dreamer's ability still doesn't work. I can pay the 2U and exile the card but I can't play it under any circumstances.

My game says I have 13813 cards, not 14 :< I have the newest version, too.

UncleHeffy wrote:My game says I have 13813 cards, not 14 :< I have the newest version, too.

Are you looking in the deck editor? The 14k number includes nonstandard cards (Vanguard, Schemes, Conspiracy, etc) which are filtered out of the primary view of the deck editor.

Forge Beta 1.5.25 (and earlier versions)

Has anyone tried playing "Human" vs "Human" in the constructed mode? I have tried this many times using different computers and different Forge versions. It's either bugged or am I missing something?

The issue is that you can't see the opening cards for the 2nd. human player, so you do not know if you should mulligan.

On the turn, however, you can see the newly drawn card. The old ones show up as texts, and can be viewed perfectly on the right window.