Forge Beta: 10-22-2014 ver 1.5.29
Moderators: timmermac, Blacksmith, KrazyTheFox, Agetian, friarsol, CCGHQ Admins
Re: Forge Beta: 10-22-2014 ver 1.5.29
by Xitax » 05 Nov 2014, 00:57
Moving the numbers to the right of the icons in the menu column makes double digits unreadably small. Another solution would be to allow overlap, but add an opposite color border on the number text to provide contrast and separation from background items, like the card overlay text.
Re: Forge Beta: 10-22-2014 ver 1.5.29
by ndlarsen » 05 Nov 2014, 20:06
When the AI casts Taigam's Scheming appreantly it can look at the cards in my library for some reason.
Re: Forge Beta: 10-22-2014 ver 1.5.29
by Stampedo » 07 Nov 2014, 01:25
When Hero of Bladehold attacks, shouldnt the tokens benefit from Battle cry?
Whenever she attacks, the newly created tokens are still 1/1.
Radiant, Archangel still benefits from "Radiant gets +1/+1 for each other creature with flying on the battlefield" despite Humility being in play.
Intended?
Whenever she attacks, the newly created tokens are still 1/1.
Radiant, Archangel still benefits from "Radiant gets +1/+1 for each other creature with flying on the battlefield" despite Humility being in play.
Intended?
Re: Forge Beta: 10-22-2014 ver 1.5.29
by friarsol » 07 Nov 2014, 02:04
Both the Battle cry trigger and the token trigger happen at the same time. You get to choose which order they go onto the stack. To allow the tokens to gain the bonus, that trigger needs to resolve first.Stampedo wrote:When Hero of Bladehold attacks, shouldnt the tokens benefit from Battle cry?
Whenever she attacks, the newly created tokens are still 1/1.
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: Forge Beta: 10-22-2014 ver 1.5.29
by Yuriel » 07 Nov 2014, 07:53
I was playing a single KTK Draft round and out of nowhere the program crashed as soon as I played a tapland. After searching for a few minutes, I couldn't find if this had happened to anyone already so I thought I'd post it. I've been playing for about two weeks(KTK and M15 drafts exclusively, so far) and this is only the second time it's crashed, yesterday being the first, but I didn't pay it much attention since I had left the game "paused" all day so I figured it was my fault. 
EDIT: I just realised that I had forgotten one possibly key detail: the crash happened immediately after I right-clicked the tapland effect on the stack to set it to Auto-yield.
EDIT: I just realised that I had forgotten one possibly key detail: the crash happened immediately after I right-clicked the tapland effect on the stack to set it to Auto-yield.
- IllegalComponentStateException | Open
- Attachments
-
Last edited by Yuriel on 07 Nov 2014, 11:55, edited 1 time in total.
- Yuriel
- Posts: 1
- Joined: 07 Nov 2014, 07:24
- Has thanked: 0 time
- Been thanked: 0 time
Re: Forge Beta: 10-22-2014 ver 1.5.29
by mastroego » 07 Nov 2014, 08:07
Well you get a pop-up window to choose your order in case of concurrent triggersStampedo wrote:I never realized you could choose, how do you do that?
Re: Forge Beta: 10-22-2014 ver 1.5.29
by chieuduong » 07 Nov 2014, 08:17
You choose what order you want in this window, don't just jam spacebar randomly.Stampedo wrote:I never realized you could choose, how do you do that?
- Attachments
-
-
chieuduong - Posts: 37
- Joined: 30 Sep 2013, 05:09
- Has thanked: 42 times
- Been thanked: 2 times
Re: Forge Beta: 10-22-2014 ver 1.5.29
by drdev » 07 Nov 2014, 20:02
For everyone getting this IllegalComponentStateException error, this issue has to do with the stack changing while hovering over an item on it. This issue was fixed right after release, so you can take the latest snapshot build to get the fix right away. Otherwise just be aware of what causes it if you want to workaround it until 1.5.30 is released.Yuriel wrote:I was playing a single KTK Draft round and out of nowhere the program crashed as soon as I played a tapland. After searching for a few minutes, I couldn't find if this had happened to anyone already so I thought I'd post it. I've been playing for about two weeks(KTK and M15 drafts exclusively, so far) and this is only the second time it's crashed, yesterday being the first, but I didn't pay it much attention since I had left the game "paused" all day so I figured it was my fault.
EDIT: I just realised that I had forgotten one possibly key detail: the crash happened immediately after I right-clicked the tapland effect on the stack to set it to Auto-yield.
- IllegalComponentStateException | Open
- drdev
- Programmer
- Posts: 1958
- Joined: 27 Jul 2013, 02:07
- Has thanked: 189 times
- Been thanked: 565 times
Re: Forge Beta: 10-22-2014 ver 1.5.29
by Zirbert » 08 Nov 2014, 05:13
Some odd behaviour from Teferi's Puzzle Box - when it triggers for the AI, I get to see, and even arrange, the AI's cards that are put on bottom of the library. That's information that should remain hidden to me. This is still present in 1.5.30 snapshot r28141 (forge-gui-desktop-1.5.30-20141102.152810-4.tar.bz2).
Re: Forge Beta: 10-22-2014 ver 1.5.29
by Zirbert » 09 Nov 2014, 01:01
This was happening in 1.5.29, and is still present in 1.5.30 snapshot r28141 (forge-gui-desktop-1.5.30-20141102.152810-4.tar.bz2).
I hate to bring it up, since it's cool that we have this card at all, but...
Possibility Storm doesn't consistently work correctly. It generally works fine with permanents, exiling the original spell, finding a new one that goes off, then putting the original spell and revealed cards on bottom.
However, when the initially cast spell is an instant or sorcery, it tends to stay on the stack and still resolve, after the "replacement" spell (which resolves as expected). The original spell card is apparently put on bottom of the library - it definitely isn't in the graveyard or exile afterward.
Worst of all is that my testing hasn't returned 100% consistent results. Sometimes instants and sorceries get removed without resolving, although not usually. And sometimes permanents (usually enchantments) stay on the stack and still resolve after their "replacement".
I'm sure that it's not a case of the "replacement" spell PS churns up being another copy of the original triggering spell. I also haven't had any other effects going that might have interfered with the Storm's effect.
Just something to keep an eye on, unless anybody can see a method behind what's happening here. If I notice anything else that might help trace the issue, I'll post it.
I hate to bring it up, since it's cool that we have this card at all, but...
Possibility Storm doesn't consistently work correctly. It generally works fine with permanents, exiling the original spell, finding a new one that goes off, then putting the original spell and revealed cards on bottom.
However, when the initially cast spell is an instant or sorcery, it tends to stay on the stack and still resolve, after the "replacement" spell (which resolves as expected). The original spell card is apparently put on bottom of the library - it definitely isn't in the graveyard or exile afterward.
Worst of all is that my testing hasn't returned 100% consistent results. Sometimes instants and sorceries get removed without resolving, although not usually. And sometimes permanents (usually enchantments) stay on the stack and still resolve after their "replacement".
I'm sure that it's not a case of the "replacement" spell PS churns up being another copy of the original triggering spell. I also haven't had any other effects going that might have interfered with the Storm's effect.
Just something to keep an eye on, unless anybody can see a method behind what's happening here. If I notice anything else that might help trace the issue, I'll post it.
Re: Forge Beta: 10-22-2014 ver 1.5.29
by slo-moe » 09 Nov 2014, 03:08
Here's a good trick: AI cast the same Thoughtseize (131) three times in a row 
(see screenshot). In the end, it has two Thoughtseize (131 and 133) in its graveyard, and I discarded four cards.
This would be ok if it had activated Chandra, Pyromaster's ultimate, but it had not done this.
(see screenshot). In the end, it has two Thoughtseize (131 and 133) in its graveyard, and I discarded four cards.This would be ok if it had activated Chandra, Pyromaster's ultimate, but it had not done this.
- Attachments
-
Re: Forge Beta: 10-22-2014 ver 1.5.29
by Noah » 09 Nov 2014, 23:48
Got this when attacking with two 7/7 Boneyard Wurms, a Merfolk Looter, a Llanowar Elves, and seven 1/2 Reach Spiders. On OS X 10.9.
- ConcurrentModificationException | Open
Last edited by Noah on 10 Nov 2014, 22:33, edited 14 times in total.
- Noah
- Posts: 4
- Joined: 09 Nov 2014, 20:09
- Has thanked: 0 time
- Been thanked: 0 time
Who is online
Users browsing this forum: No registered users and 48 guests