Page 2 of 9

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 02 Aug 2013, 15:57
by ahuinan
Issue with Primordial Hydra, I can't use the cost reduction done by Heartless Summoning to the casting of Primordial Hydra. Happens because the {X} in the casting cost of Primordial Hydra isn't asked before paying for it's cost.

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 02 Aug 2013, 17:20
by Nim
I have a Midnight Banshee and a Necroskitter. I kill the opponent's, Darien, King of Kjeldor (legendary) and it returns under my control. The next turn the AI plays another Darien, King of Kjeldor under his control. Both Darien's stay in play, although they should be buried (legendaries, no Mirror Gallery or similar in play).

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 02 Aug 2013, 17:26
by friarsol
Nim wrote:I have a Midnight Banshee and a Necroskitter. I kill the opponent's, Darien, King of Kjeldor (legendary) and it returns under my control. The next turn the AI plays another Darien, King of Kjeldor under his control. Both Darien's stay in play, although they should be buried (legendaries, no Mirror Gallery or similar in play).
There are new Legendary rules introduced in M14

http://www.wizards.com/magic/magazine/a ... ature/248e

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 02 Aug 2013, 18:43
by lazylockie
ahuinan wrote:Issue with Primordial Hydra, I can't use the cost reduction done by Heartless Summoning to the casting of Primordial Hydra. Happens because the {X} in the casting cost of Primordial Hydra isn't asked before paying for it's cost.
just like Sphinx's Revelation, some X cards haven't been changed yet, but do check Aurelia's Fury and you'll see that cost reduction/increase applies

a simple way to play around cost reductions is to click on "generate mana" (with developer mode activated) and pay your X with the equivalent reduction.

Possibility Storm - not always allowing you to cast a spell.

PostPosted: 02 Aug 2013, 18:52
by Rayenous
Possibility Storm issue: If the spell which triggers this ability is not on the stack when this ability resolves, the ability will properly reveal cards from the top of the Library... but it does not allow you to play a spell.

Example A: Two Possibility Storm are on the Battlefield. Player casts an instant. Two separate instances of "possibility storm" triggered ability are placed on the stack. The first resolves properly... cards are revealed, then spell may be cast. Second ability resolves... cards are revealed, but you are not given the option to cast a spell for free.

Example B: Possibility Storm is on the Battlefield, and I control a Nivmagus Elemental. I cast an instant. Possibility Storm triggers. I use Nivmagus Elemental to exile the original spell and get 2 +1/+1 counters. When Possibility Storm resolves, the cards are revealed, but you are not given the option to cast the spell for free.

Relevant Oracle rulings from Wizards website: 4/15/2013: - "If Possibility Storm's ability doesn't exile the original spell (perhaps because another Possibility Storm already exiled it), you'll still exile cards from the top of your library until you exile a card that shares a card type with it and have the opportunity to cast that spell."

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 02 Aug 2013, 19:33
by Mageta the Lion
In Vanguard games with Momir Vig creature token created with him trigger twice some time.

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 02 Aug 2013, 19:56
by moomarc
Twinkie wrote:This is not really a 1.4.5 bug report because I've had the same problem with the version before but at the moment I cannot start Forge. I run it on Win7 and until like a week or so ago I had no problems but today I tried to start Forge with the .exe and the mouse just turns into the loading symbol for a second and then becomes the normal mouse again and nothing has happened. There is also no Forge-process running when I open the taskmanager so there really doesn't seem to be anything happening. Downloading the newest version didn't fix the issue and I already tried running it as admin and in compatibility mode.
Are you using the latest java runtime environment (java 7)?

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 02 Aug 2013, 22:57
by ahuinan
lazylockie wrote:
ahuinan wrote:Issue with Primordial Hydra, I can't use the cost reduction done by Heartless Summoning to the casting of Primordial Hydra. Happens because the {X} in the casting cost of Primordial Hydra isn't asked before paying for it's cost.
just like Sphinx's Revelation, some X cards haven't been changed yet, but do check Aurelia's Fury and you'll see that cost reduction/increase applies

a simple way to play around cost reductions is to click on "generate mana" (with developer mode activated) and pay your X with the equivalent reduction.
Ok, Thanks.

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 03 Aug 2013, 02:28
by Mageta the Lion
 Gorilla Berserkers has no mana cost.

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 03 Aug 2013, 11:49
by Joril
The AI played Aleatory while there were no creatures in play, the log showed a "Aleatory ability fizzles" and no additional card was drawn on the next turn

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 03 Aug 2013, 14:18
by Sarusei
Description: right after i lost the first match game i got this

NullPointerException | Open
Code: Select all
Forge Version:    1.4.5-r22726
Operating System: Linux 2.6.32-50-generic i386
Java Version:     1.7.0_25 Oracle Corporation

java.lang.NullPointerException
   at forge.game.player.Player.isOpponentOf(Player.java:350)
   at forge.Card.canBeShownTo(Card.java:8328)
   at forge.control.FControl.mayShowCard(FControl.java:339)
   at forge.ImageCache.getImage(ImageCache.java:108)
   at forge.view.arcane.CardPanel.setCard(CardPanel.java:638)
   at forge.view.arcane.PlayArea.updateCard(PlayArea.java:641)
   at forge.view.arcane.PlayArea.updateSingleCard(PlayArea.java:301)
   at forge.gui.match.CMatchUI.updateSingleCard(CMatchUI.java:368)
   at forge.gui.match.CMatchUI.updateCards(CMatchUI.java:360)
   at forge.control.FControlGameEventHandler$9.run(FControlGameEventHandler.java:256)
   at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
   at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)
   at java.awt.EventQueue.access$200(EventQueue.java:103)
   at java.awt.EventQueue$3.run(EventQueue.java:694)
   at java.awt.EventQueue$3.run(EventQueue.java:692)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:703)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:242)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:161)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:146)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:138)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:91)

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 03 Aug 2013, 21:40
by lazylockie
anyone else noticed a slowdown? there's like a big delay between clicking on a card and activating it.

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 03 Aug 2013, 22:43
by TastetheJace
Not too sure about this one, but had a Godhead of Awe on the battlefield and my opponent activated its Treetop Village ability, with it still becoming a 3/3 creature.

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 03 Aug 2013, 23:30
by timmermac
lazylockie wrote:anyone else noticed a slowdown? there's like a big delay between clicking on a card and activating it.
That's odd. I actually thought Forge was running slightly faster this morning when I was playing.

Re: Forge Beta: 07-31-2013 ver 1.4.5

PostPosted: 04 Aug 2013, 00:12
by drdev
lazylockie wrote:anyone else noticed a slowdown? there's like a big delay between clicking on a card and activating it.
I'm guessing this has something to do with the change to activate cards on mouse up instead of mouse down. It was a necessary change to support the new card zoomer and support drag dropping cards without activating them (previously, for example, if you tried to drag drop a land in your hand at a time when you can play a land, you'd end up playing the land by accident).