Re: Forge Beta: 04-12-2013 ver 1.3.12
Bug: When paying colorless mana costs with Vivid lands, it uses a counter automatically and unnecessarily.
High Quality Resources for Collectible Card Games and Home of the CCGHQ Team
https://www.slightlymagic.net/forum/
https://www.slightlymagic.net/forum/viewtopic.php?f=26&t=10076
A very similiar bug related to keywords enumeration was fixed in the snapshot build published yesterday. Look at the ending of first post of this thread for a download link.Sawteeth wrote:Description: AI attacked with Dunerider Outlaw and I discarded Vengeful Pharaoh via Putrid Imp during the declare blockers step and got this on the move to combat damage.
- Code: Select all
Forge Version: 1.3.12-r20962
Operating System: Windows 7 6.1 x86
Java Version: 1.7.0_17 Oracle Corporation
java.util.NoSuchElementException
at java.util.ArrayList$Itr.next(Unknown Source)
at java.util.Collections.sort(Unknown Source)
at forge.Card.getUnhiddenKeyword(Card.java:4298)
at forge.Card.getKeyword(Card.java:4196)
at forge.Card.canBeTargetedBy(Card.java:7983)
This was fixed alreadyeruditebaboon wrote::arrow: Cloudshift also has the same problem as Ghostly Flicker - if a creature is the target of a spell before Cloudshift is cast on it, it will still be the target of that spell after it resolves.
Edit: also counters that are on the creature are not removed.
The script of Vexing Devil has been changed after the last beta. It works now.Harfenik wrote:Bug: it seems that in this version, Vex Devil doesnt damage an opponent when sacrificed.
This worked correctly when i tested it. It's possible that the labels won't update right away.lefonix wrote:Bug: I don't think Red Sun's Zenith ends up back in my library after I cast it. It's neither in the graveyard nor the exile zone, and total cards in all the zones add to 59 after casting.
The script of Vexing Devil has been changed after the last beta. It works now.Sloth wrote:Harfenik wrote:Bug: it seems that in this version, Vex Devil doesnt damage an opponent when sacrificed.
Sloth is saying that this was already fixed, but not in the version you have.Harfenik wrote:Nope, it doesnt for me