Page 162 of 441

Re: Current Known Bugs list

PostPosted: 07 May 2010, 20:25
by juzamjedi
I use Control Magic on my opponent's Mogg War Marshal. I equip Skullclamp to it and expect to draw cards, but my opponent draws the 2 cards. I receive the extra goblin from Mogg War Marshal. So then I equip Skullclamp to my goblin token... and the computer draws 2 more cards again!

So pretty clear the problem is somewhere in Skullclamp's code.

Re: Current Known Bugs list

PostPosted: 07 May 2010, 21:14
by slapshot5
juzamjedi wrote:So pretty clear the problem is somewhere in Skullclamp's code.
Yep. It was causing the Equipped card's owner to draw cards. I fixed it to be Skullclamp's controller that draws the cards.

-slapshot5

Re: Current Known Bugs list

PostPosted: 07 May 2010, 21:55
by TonyRoomZ
Goblin Assault in Forge -- official beta: $Date: 2010-04-06 is behaving like bitterblossom in the sense it is draining the player for 1 during upkeep :)

Re: Current Known Bugs list

PostPosted: 07 May 2010, 21:57
by DennisBergkamp
Yeah, this is fixed in the 05/02 version.

Re: Current Known Bugs list

PostPosted: 08 May 2010, 00:24
by freestorageaccount
I wasn't quite paying attention at the time this happened, so I'm not sure about it, but it seems Umezawa's Jitte might not have received counters when the computer Threaten.ed the equipped creature. Could anyone confirm this if it's true (or disprove it if it's not)?

Re: Current Known Bugs list

PostPosted: 08 May 2010, 00:48
by koravain
Noticed another AI "haste" issue. If the AI plays Act of Treason, it'll grab one of your creatures and won't attack with it. It also will use Act of Treason AFTER it attacks, which is even more useless. Oddly enough in several tests the AI seems to play Threaten just fine.

Re: Current Known Bugs list

PostPosted: 08 May 2010, 03:19
by slapshot5
freestorageaccount wrote:I wasn't quite paying attention at the time this happened, so I'm not sure about it, but it seems Umezawa's Jitte might not have received counters when the computer Threaten.ed the equipped creature. Could anyone confirm this if it's true (or disprove it if it's not)?
confirmed and fixed in SVN. Thanks.

-slapshot5

Re: Current Known Bugs list

PostPosted: 08 May 2010, 05:10
by freestorageaccount
Thanks!

To make this a control-change bug trifecta, in the same situation where I control an Umezawa's Jitte equipping a creature I don't control, counters can be used only as a sorcery (i.e., at those times that the Jitte could be equipped).

In addition to having to decide whether or not you might want to use Sensation Gorger.'s mini-.Wheel of Fortune ability before knowing whether it could occur, there is currently no stop between your untap and upkeep steps and the ability isn't implemented as a triggered one that passes through the stack, so you can't even unload instant-speed burn at that time in preparation for an effect that might not actually happen.

Re: Current Known Bugs list

PostPosted: 08 May 2010, 07:49
by indicatie
juzamjedi wrote:I use Control Magic on my opponent's Mogg War Marshal. I equip Skullclamp to it and expect to draw cards, but my opponent draws the 2 cards. I receive the extra goblin from Mogg War Marshal. So then I equip Skullclamp to my goblin token... and the computer draws 2 more cards again!

So pretty clear the problem is somewhere in Skullclamp's code.
slapshot5 wrote:Yep. It was causing the Equipped card's owner to draw cards. I fixed it to be Skullclamp's controller that draws the cards.

-slapshot5
Which should not have been a problem in the case of the equipped goblin token, because since M10 rules, tokens created by an opponent's source under your control are owned by you. This meant the end for my hunted creatures w/ Brand deck....

Re: Current Known Bugs list

PostPosted: 08 May 2010, 07:54
by indicatie
There's something strange going on in the Deck Editor of the quest mode. When I mouse over the picture in the bottom right corner, the previously selected card stays there and the newly selected card is displayed over it. Some strange things happen also in the top left corner when I do this.

Deck editor.jpg

Re: Current Known Bugs list

PostPosted: 08 May 2010, 14:42
by Vecc
Haha, I was gonna use Tarmogoyf as an example to show why Overbeing of Myth would survive but mixed both up in the end. x] Well either way, like Dennis said it's working correctly. :D

Re: Current Known Bugs list

PostPosted: 08 May 2010, 18:50
by Caranthol
Triadasoul wrote:When you tap Gaea's Cradle for mana for paying casting cost with 0 creatures in play, application returns:

Detailed error trace:
java.lang.NullPointerException
at forge.ManaPool.subtractMana(ManaPool.java:328)
at forge.Input_PayManaCostUtil.tapCard(Input_PayManaCostUtil.java:38)
at forge.Input_PayManaCost.selectCard(Input_PayManaCost.java:45)
at forge.GuiInput.selectCard(GuiInput.java:48)
at forge.GuiDisplay3$7.mousePressed(GuiDisplay3.java:353)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(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)
I got the same error using the last version.

Re: Current Known Bugs list

PostPosted: 08 May 2010, 20:48
by Almost_Clever
You can select non-creature cards in your graveyard when you cast Artisan of Kozilek. Instants and sorceries get put on the battlefield in your land area. Auras disappear (they are nowhere I can see) but other enchantments show up where they normally do. You can cast the instants (even with buyback) as though they were in your hand.

I ran into a totally different bug in trying to get an aura into my graveyard while probing the bounds of this bug. I had chosen Robe of Mirrors before I realized that I couldn't Capsize the creature after it was enchanted with the RoM; so I tried to Capsize the creature while the RoM was on the stack. The bug here is that the RoM was not in my graveyard or exiled; it was just gone.

Re: Current Known Bugs list

PostPosted: 08 May 2010, 21:37
by slapshot5
Caranthol wrote:
Triadasoul wrote:When you tap Gaea's Cradle for mana for paying casting cost with 0 creatures in play, application returns:

Detailed error trace:
java.lang.NullPointerException
I got the same error using the last version.
Huh. I remember seeing this, but I swear it was fixed. Oh well. I just checked in a fix for this to SVN. (I saw the crash with the current codebase.)

-slapshot5

Re: Current Known Bugs list

PostPosted: 09 May 2010, 02:54
by freestorageaccount
One game, the computer managed to keep Nemesis of Reason on the table, but I was safe doing my Collective Restraint / Global Ruin / Icy Manipulator hijinks...or so I thought. Thanks to its prudent decision to save a few lands many times rather than many lands a few times, the computer had almost none after the sweep, so I decided to tap one of them instead of the creature itself in order to deny it one mana as well as prevent the attack. This went on for several turns, until I abruptly lost. :-o :-? :-s

Then it hit me that Collective Restraint.'s implementation might be the same for the player as for the computer, so I tested it against some exalted creatures. Sure enough, the abilities triggered and gave the would-be attacker bonuses, albeit ineffective ones. The "pretend to attack, then get cold feet" kludge was the culprit here.