Forge Beta: 04-12-2013 ver 1.3.12

[Nordos]

Noticed several bugged cards/interactions, don't know if it's from this version only.
Restoration Angel - the creature he restores gets bugged on permanent summoning sickness.

Not only Restoration Angel, moreover the whole blinking is bugged.
Sometimes they become summoned sickness and all spells/abilities targeting it will fizzle. Additional, when they blink, they wouldn't untap.

[gos]

I cast a morph (Fallen Cleric). It did not trigger my opponent's Taurean Mauler.

[Karma]

I just Downloaded this version and it seems to Crash every time i go to the spell shop in the fantasy quest.and this is what it tell me:

ArrayIndexOutOfBoundsException | Open

Code: Select all

Forge Version:    1.3.12-r20962
Operating System: Windows 7 6.1 x86
Java Version:     1.6.0_25 Sun Microsystems Inc.

java.lang.ArrayIndexOutOfBoundsException: 1
   at forge.quest.io.ReadPriceList.readFile(ReadPriceList.java:91)
   at forge.quest.io.ReadPriceList.setup(ReadPriceList.java:61)
   at forge.quest.io.ReadPriceList.<init>(ReadPriceList.java:52)
   at forge.gui.deckeditor.controllers.CEditorQuestCardShop.<init>(CEditorQuestCardShop.java:107)
   at forge.gui.home.quest.SSubmenuQuestUtil.showSpellShop(SSubmenuQuestUtil.java:252)
   at forge.gui.home.quest.CSubmenuDuels$3.execute(CSubmenuDuels.java:44)
   at forge.gui.toolbox.FLabel._doMouseAction(FLabel.java:309)
   at forge.gui.toolbox.FLabel.access$5(FLabel.java:304)
   at forge.gui.toolbox.FLabel$4.mouseClicked(FLabel.java:345)
   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.dispatchEventImpl(Unknown Source)
   at java.awt.EventQueue.access$000(Unknown Source)
   at java.awt.EventQueue$1.run(Unknown Source)
   at java.awt.EventQueue$1.run(Unknown Source)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
   at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown Source)
   at java.awt.EventQueue$2.run(Unknown Source)
   at java.awt.EventQueue$2.run(Unknown Source)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.security.AccessControlContext$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)


Plz tell me whats wrong.

[lm01]

Not only Restoration Angel, moreover the whole blinking is bugged.
Sometimes they become summoned sickness and all spells/abilities targeting it will fizzle. Additional, when they blink, they wouldn't untap.

Hmmm... I see. I believe the old flickers used to work well though a bunch of versions back. Probably some changes messed it up.

On a seperate issue, I noticed a minor issue on Deck Editor.
forge-1.3.13-20130414.105556-2.tar.bz2

Details | Open

When you put same card from different sets Forge doesn't identify them after they are saved.

Part of deck, when opened on a txt editor:
...
4 Lightning Bolt|LEA
4 Lightning Bolt|M11
...
When you open the deck on Deck Editor it only shows 4 Lightning Bolts (the ones from M11) and 60 cards, although when you play with that deck it has 64 cards.
(I have the enforcement off, because often I have 1~14 cards on sideboard, and Forge forbids that deck from playing while on)

Deck Editor total card count is missleading so if you change card pics often check if everything is ok after.
As a curiosity, when you remove the 4 Lightning Bolt on the Deck Editor, another playset of Lightning Bolt shows up from LEA.

[Karma]

the spell shop is crashing anytime i try to open it.

[Karma]

"I cast a morph (Fallen Cleric). It did not trigger my opponent's Taurean Mauler."
Have you considered its a mana ability and not considered a spell?

[Chris H.]

:? the spell shop is crashing anytime i try to open it.

 
Hmmm, it might be worthwhile to use the Content Downloaders -> Download Card Prices button. This might not take care of your problem.

It might be related to the common Known Issues bug dealing with the deck editor xml file. Moving the userData/preferences/editor.xml file out of the preferences dir and then restarting forge might help. You may also need to move the editor.preferences file somewhere else.

[gos]

"I cast a morph (Fallen Cleric). It did not trigger my opponent's Taurean Mauler."
Have you considered its a mana ability and not considered a spell?

No, I hadn't considered that.

702.35a Morph is a static ability that functions in any zone from which you could play the card it's on, and the morph effect works any time the card is face down. "Morph [cost]" means "You may cast this card as a 2/2 face-down creature, with no text, no name, no subtypes, no expansion symbol, and no mana cost by paying rather than paying its mana cost." (See rule 707, "Face-Down Spells and Permanents.")

I'm fairly certain that using the morph ability counts as casting a spell (it does say "cast this card") and it interacts with other game objects in the same way as a spell (e.g. you can counter a morph being cast with a Counterspell).

Also, a "mana ability" is something completely different.

[gos]

I unmorphed my Willbender in response to my opponent resolving Dark Hatchling, when the Hatchling's etb ability was on the stack. I was not able to change the target of the ability on the stack, the Willbender's ability did not even trigger.

[friarsol]

I unmorphed my Willbender in response to my opponent resolving Dark Hatchling, when the Hatchling's etb ability was on the stack. I was not able to change the target of the ability on the stack, the Willbender's ability did not even trigger.

Willbender targets spells or abilities, not triggers.

[lm01]

Morphing does not use the stack, so you can actually respond to abilities with Split Second, let alone normal spells on stack. Thus the question on the post from Karma.

I cast a morph (Fallen Cleric). It did not trigger my opponent's Taurean Mauler.
Have you considered its a mana ability and not considered a spell?

A mana ability would bypass Split Second, like the morph, but this should only be so when you morph the card face up, not while casting a morphed card. Dropping a morphed card is like casting any usual spell.

[gos]

I unmorphed my Willbender in response to my opponent resolving Dark Hatchling, when the Hatchling's etb ability was on the stack. I was not able to change the target of the ability on the stack, the Willbender's ability did not even trigger.

Willbender targets spells or abilities, not triggers.

Do you mean this as an explanation of what's happening in forge or the way things are supposed to work?

If it's the second, I must respectfully disagree: Dark Hatchling has a triggered ability, which targets exactly 1 target, and Willbender's triggered ability should be able to change its target.

[Doomlord]

I unmorphed my Willbender in response to my opponent resolving Dark Hatchling, when the Hatchling's etb ability was on the stack. I was not able to change the target of the ability on the stack, the Willbender's ability did not even trigger.

Willbender targets spells or abilities, not triggers.

There are three types of abilities: Activated abilities, triggered abilities and static abilities. Static abilities never go on the stack, so you cannot use Willbender on them, but both the other two types are abilities that go on the stack, and thus can have their targets changed by Willbender.

[friarsol]

If it's the second, I must respectfully disagree: Dark Hatchling has a triggered ability, which targets exactly 1 target, and Willbender's triggered ability should be able to change its target.

Ah I misread Willbender to read "Activated ability" and not just ability. I'd imagine the script isn't allowing triggers to be targeted.

[MystREmo]

Thanks for the new version.

Is Flashback implented? I was not able to figure out how to cast from the graveyard (specifically with Lava Dart).

There's a flashback area underneath the graveyard symbol.