Re: Forge Beta: 05-25-2014 ver 1.5.18
Description: I had 3 Locust Miser s and 2 Gnat Miser s in play. This error happened when my opponent was supposed to discard at the end of turn.
- NullPointerException | Open
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=14517
This error remains in 1.5.18.The classic Project X combo (i.e. Crypt Champion and Saffi Eriksdotter) doesn't work. Once you have activated Saffi's ability once, targeting the Champion, the Champion keeps returning from the graveyard repeatedly, with no way to break the loop.
It should only return once, at which point it becomes a new object, with no memory of being targeted by Saffi.
I also observed this error with Adarkar Valkyrie, one activation of her ability returned the "same" creature (actually just the same card) twice from the graveyard in the same round.gos wrote:This error remains in 1.5.18.The classic Project X combo (i.e. Crypt Champion and Saffi Eriksdotter) doesn't work. Once you have activated Saffi's ability once, targeting the Champion, the Champion keeps returning from the graveyard repeatedly, with no way to break the loop.
It should only return once, at which point it becomes a new object, with no memory of being targeted by Saffi.
I'll look at it in a few minutes. What are your quest settings (format/sets/etc)?Lotus347 wrote:Description: Whenever I end a game (win or lose) in Quest Mode, I get this. Happened every time, 20 times in a row, of which 18 I conceded to speed up to the end of the game.
- IndexOutOfBoundsException | Open
Quest Settings:KrazyTheFox wrote:I'll look at it in a few minutes. What are your quest settings (format/sets/etc)?Lotus347 wrote:Description: Whenever I end a game (win or lose) in Quest Mode, I get this. Happened every time, 20 times in a row, of which 18 I conceded to speed up to the end of the game.
- IndexOutOfBoundsException | Open
Edit: Try this build out.[/url] It should prevent the error from occurring, though it'd still be helpful to know more about your quest setup to create a better fix. I can't replicate the bug on my end, so the fix isn't tested.
That's correct. The bug that prevented Forge from running if you hadn't run a previous version before needed fixing, which puts it at a very early 1.5.19 snapshot. It's still technically 1.5.18 with a couple small, but very important, bug fixes.