Bug Reports (snapshot builds)

[friarsol]

I can't seem to redirect damage from attacking creatures to plainswalkers (damage spells work all right though).

Combat damage is not "redirected"; you have to attack planeswalkers directly. During the declare attackers step, click on the PW you want to attack. Then choose the creatures you want to attack it. Rinse, repeat.

[borsuk]

Version 1.5.26, problem with Reprisal card, i've encountered sitution when i can't use this card because when i'm trying i can only see animation of card comming frome upper left screen (player's field window). There's no any card on battleground that would block casting this spell. I was trying to post the screenshoot via [img]jpeg%20url...[/img] but i'm getting "Your post looks too spamy for a new user, please remove off-site URLs.", what's going on? Raw screenshot url is imageshack.us/i/iqNb1e42j

[SecretCaveman]

with the latest 1.5.29 build, when starting the program. Had the same issue with the regular 1.5.28 version.

Description: [describe what you were doing when the crash occurred]

NullPointerException | Open

Code: Select all

Forge Version:    1.5.29-SNAPSHOT-r27812 (mixed revisions detected; please update from the root directory)
Operating System: Windows 7 6.1 amd64
Java Version:     1.8.0_20 Oracle Corporation

java.lang.NullPointerException
   at java.util.Collections.shuffle(Unknown Source)
   at java.util.Collections.shuffle(Unknown Source)
   at forge.quest.QuestEventDraft.getRandomDraftOrNull(QuestEventDraft.java:751)
   at forge.quest.data.QuestAchievements.generateDrafts(QuestAchievements.java:258)
   at forge.screens.home.quest.CSubmenuQuestDraft.initialize(CSubmenuQuestDraft.java:95)
   at forge.view.FView.initialize(FView.java:123)
   at forge.control.FControl$3.run(FControl.java:224)
   at java.awt.event.InvocationEvent.dispatch(Unknown Source)
   at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
   at java.awt.EventQueue.access$400(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)


[Fizanko]

Started a constructed duel in r27853 just freshly downloaded and noticed that tapped lands do not untap correctly, probably again the problem with areas not refreshing visually.

example : AI End Turn phase :


My Upkeep phase :

Notice one of the land isn't untapped visually despite it should (nothing on the battlefield prevent it)

My M1 phase after i recieved a card :

still not correctly displayed, the land isn't untapped.

I play a land


And only then the land is then correctly displayed as untapped

[Fizanko]

still r27853

Probably linked to incorrect refreshing, the P/T flicker again.

example :

Deathbellow Raider that has 2 Fearsome Temper

I decide to add an Aspect of Gorgon to it, so i click the card and :


the P/T go back at the card original P/T instead of current ones
Only once i effectively played it, the P/T is refreshed to correct values

And it's not only with auras, i played later Flurry of Horns, and when i clicked on that card, the Deathbellow raider P/T went back to original value, only when the 2 minotaur token appeared on the battlefield the P/T correctly refreshed.

And still maybe once every 3 or 4 phases in a same turn (both AI and mines) i notice it's flickering.

[KrazyTheFox]

with the latest 1.5.29 build, when starting the program. Had the same issue with the regular 1.5.28 version.

Description: [describe what you were doing when the crash occurred]

NullPointerException | Open

Code: Select all

Forge Version:    1.5.29-SNAPSHOT-r27812 (mixed revisions detected; please update from the root directory)
Operating System: Windows 7 6.1 amd64
Java Version:     1.8.0_20 Oracle Corporation

java.lang.NullPointerException
   at java.util.Collections.shuffle(Unknown Source)
   at java.util.Collections.shuffle(Unknown Source)
   at forge.quest.QuestEventDraft.getRandomDraftOrNull(QuestEventDraft.java:751)
   at forge.quest.data.QuestAchievements.generateDrafts(QuestAchievements.java:258)
   at forge.screens.home.quest.CSubmenuQuestDraft.initialize(CSubmenuQuestDraft.java:95)
   at forge.view.FView.initialize(FView.java:123)
   at forge.control.FControl$3.run(FControl.java:224)
   at java.awt.event.InvocationEvent.dispatch(Unknown Source)
   at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
   at java.awt.EventQueue.access$400(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)


That's been fixed. Update to the latest latest version.

[phantumdragun]

A few things i noticed in r27859: often times cards don't untap, or they mechanically untap but visually they do not. Also, in a Quest mode Duel against "Jesse James" running a Green Blue Morph deck (although the description said WB Morph), he plays cards with no regard for mana cost. He played a 13/13 Krosan Cloudscraper on turn 3 with one island and 2 forests. The card costs 10 mana to cast. He did this with multiple huge creatures over and over again.

[Marek14]

A few things i noticed in r27859: often times cards don't untap, or they mechanically untap but visually they do not. Also, in a Quest mode Duel against "Jesse James" running a Green Blue Morph deck (although the description said WB Morph), he plays cards with no regard for mana cost. He played a 13/13 Krosan Cloudscraper on turn 3 with one island and 2 forests. The card costs 10 mana to cast. He did this with multiple huge creatures over and over again.

I noticed both of these. Casting cards face down is broken: you can cast the card for 3 mana, but it enters the battlefield face up.

[Fizanko]

r27859
minor bug, Niv-Mizzet 3.dck (Niv-Mizzet Hard) in Ravnica world has 62 cards instead of 60

[lujo]

Face-down creatures come into play face up.

[Sloth]

r27859
minor bug, Niv-Mizzet 3.dck (Niv-Mizzet Hard) in Ravnica world has 62 cards instead of 60

Decks are allowed to have more than 60 cards, or am i missing something?

In the main world there are decks with 65, 68, 77, 91, 120, 263 and even 572 cards.

[Fizanko]

Oh ?
I thought the rule was about 60 cards deck (and if more, it was what the sideboard was made for), my bad if there's no rule then.

[friarsol]

Oh ?
I thought the rule was about 60 cards deck (and if more, it was what the sideboard was made for), my bad if there's no rule then.

Magic typically only has rules for Minimum card deck sizes. There's a few variants that state specifically how many cards in your deck (like Commander where its 100 including your Commander). Cards like Battle of Wits couldn't exist with a maximum deck size.

[Fizanko]

Interesting, i thought it was an official rule to have a max limit of 60 (out of sideboards of course), so the 60 cards rule is just in fact an unofficial agreement between players in some format ?

[sweetLu]

People play 60 card decks because it improves the consistency of your deck. It maximizes the chance you will get the cards you want or need in your opening hand or draws. Tournament level decks typically use this as a rule because it gives them the best chance of winning.