Collectible Card Game Headquarters

Hexadecimal wrote:

serrasmurf wrote:I just had opponent get a token from skeketonize.
You're sure the creature died?

Yes. Though now I've checked it in beta version and it works, so it's exclusively a snapshot bug. Generally I assume that if a card bug is presented in a snapshot, it should be presented in beta version as well. This time the assumption was incorrect.

If you see bugs in Snapshots, please report them in the snapshot thread (viewtopic.php?f=52&t=6333) along with which build/svn number.

friarsol wrote:If you see bugs in Snapshots, please report them in the snapshot thread (viewtopic.php?f=52&t=6333) along with which build/svn number.

Ok. But where do bug reports that are applicable for both beta and snapshots belong ?

On an unrelated note: player don't get the opportunity to discard lands while Lightning Storm is on the stack, since flashback zone aren't updated properly. In order to get this opportunity, some other instant effect must be resolved in response to Storm, then it will appear in the flashback zone.

Hexadecimal wrote:

friarsol wrote:If you see bugs in Snapshots, please report them in the snapshot thread (viewtopic.php?f=52&t=6333) along with which build/svn number.

Ok. But where do bug reports that are applicable for both beta and snapshots belong ?

Typically, I'd suggest posting in the forum that is the most recent (that would usually be the snapshot builds). But if it's happening in the beta and hasn't been fixed, then I wouldn't say it's not incorrect to post it in the beta. It really only matters when it happens in one and not the other that my concern for the location of the post comes from (hunting for bugs that have already been fixed in the svn, or hunting for bugs that haven't been introduced in the beta). I'd say it's very rare for people to be posting bug reports in more than one place. People are either only on beta releases, or people are on snapshot/svns, which is why I'd say just post in whichever forum your builds are for.

I'm not sure if this is more properly a bug report or a feature request, but...

When you have an Amulet of Vigor in play, and multiple permanents enter the battlefield tapped simultaneously, the trigger-ordering window gives no indication of which trigger corresponds to which permanent, making it kind of useless.

(An example of the sort of situation where this matters: playing the Modern Amulet-Bloom deck, you have two Amulets in play, and cast Primeval Titan fetching Boros Garrison and Slayers' Stronghold. If both of the Slayers' Stronghold untap triggers resolve before either of the Boros Garrison triggers, you only get to pump your Titan once. Even worse, the default ordering puts all the triggers for the same permanent together, so there's a 50% chance of being randomly screwed the first time this happens to you unless you know an awful lot about Forge's internals.)

The same thing I talked about in the last version still happens.

When playing Archenemy, the Scheme cards activate in such a way that you get the targeting/payment prompt without as much as seeing even the name of the card that activated (for example I just got a popup with "target cards in enemy graveyard" with no explanation what will happen to them).

This makes it almost impossible to actually play Archenemy, as you have no idea what effect are you targeting.

There's a bug in Necromancy. If I blink the creature it's enchanting (with, say, Cloudshift), Necromancy will kill the creature after it returns. It's a new creature as far as the game is concerned, so Necromancy should not have any effect on it (but apparently remembers the card itself rather than the creature that the card becomes).

friarsol wrote:Momir creates tokens, so nothing would be in your graveyard.

Good point, but how do I tell what happened? I suppose it could have been Wood Elemental.

Also, Forge can't figure out how to cast Baleful Strix (which costs UB) with just Underground Sea and Volcanic Island even though there is only one solution.

Synod Sanctum returns opponent's creatures that were temporarily controlled by you under your opponent's control instead of yours.

I have 2 x Doubling Season, Tamiyo, the Moon Sage (8 loyalty) and Jace, Architect of Thought (8 loyalty). I use the ultimate ability of Ugin, the Spirit Dragon. It allows me to put onto the battlefield another Tamiyo, the Moon Sage and another Jace, Architect of Thought. Forge asks me to choose the order in which to apply the Doubling Season effects, then asks me which Jace and which Tamiyo I wish to keep. Strangely enough, all four of them now have 8 loyalty. The double Doubling Season should have given the two new planeswalkers 16 loyalty each.

I just tried some 4-player games. It was awesome, but not without bugs:

All my opponents have the same portrait as player 2 despite me giving them different portraits.

Trying to quit a game proved challenging. I clicked the X in the Game tab to close it but the game kept going on without me for quite some time.

I don't understand how the turn order works. It went P4 -> P3 -> me -> P2.

Whenever one of my opponents was eliminated, their stuff stays visible instead of getting exiled. I can't interact with it anymore but it is a bit confusing.

It's hard to tell who's getting attacked by what. Arrows would be nice.

When declaring attackers, I clicked P3's portrait and then Alpha Strike, and all my dudes attacked P2.

There's some weird stuff going on with Gemstone Caverns. Whenever I tap it to make a mana payment, that mana is not spent on the cost but is instead floated into my pool (from where I can spend it). But one time I was trying to cast Dark Ritual from my graveyard (due to Yawgmoth's Will) and only had the Gemstone Caverns untapped, but it wouldn't let me pay and I had to cancel and then the Dark Ritual was exiled even though I never cast it.

There was also a 4-player game where I got to start and had a Gemstone Caverns in my opening hand but was never asked to put it onto the battlefield.

Xyx wrote:I don't understand how the turn order works. It went P4 -> P3 -> me -> P2.

Think of it like this instead of the players sitting in a circle (1,2,3,4) and choosing a starting player. All the players roll to see which seat they'll sit in, the first player geting a seat being the starting player.

Yeah, after I rearranged the player battlefield layout it turned out that I was mistaken and the turn order is working fine.

Got a real funny bug, though! Endless Whispers puts stuff into the command zone instead of onto the battlefield. Also, I could not concede that (4-player) game.

It would appear that the "only one Doubling Season gets applied" bug that I described above involves the ultimate of Ugin, the Spirit Dragon. Once again I had 2 x Doubling Season and then put some planeswalkers onto the battlefield, and they only got double instead of quadruple loyalty.

My 6/4 Phantom Centaur was double-blocked and lost two counters instead of just one. All combat damage is dealt as a single event, so it should only lose one counter.

Description: Appears after winning a commander match. I attacked with a 10/10 Korlash, Heir to Blackblade and a Geralf's Messenger. At the CD phase, this popped out. Have made a picture of it.

RuntimeException | Open

Code: Select all

Forge Version:    1.5.35-r-1
Operating System: Windows 7 6.1 amd64
Java Version:     1.8.0_31 Oracle Corporation

java.lang.RuntimeException: AbilityFactory : getAbility -- no API in
   at forge.game.ability.AbilityFactory.getAbility(AbilityFactory.java:106)
   at forge.game.replacement.ReplacementHandler.executeReplacement(ReplacementHandler.java:170)
   at forge.game.replacement.ReplacementHandler.run(ReplacementHandler.java:135)
   at forge.game.replacement.ReplacementHandler.run(ReplacementHandler.java:81)
   at forge.game.player.Player.loseConditionMet(Player.java:1546)
   at forge.game.player.Player.checkLoseCondition(Player.java:1590)
   at forge.game.GameAction.checkGameOverCondition(GameAction.java:944)
   at forge.game.GameAction.checkStateEffects(GameAction.java:799)
   at forge.game.phase.PhaseHandler.startFirstTurn(PhaseHandler.java:899)
   at forge.game.GameAction.startGame(GameAction.java:1390)
   at forge.game.Match.startGame(Match.java:71)
   at forge.match.MatchUtil$2.run(MatchUtil.java:202)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.lang.Thread.run(Unknown Source)