Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
11 Feb 2017, 15:26
by Agetian
imaginarynumber wrote:The intro deck in quest mode, "Forged In Battle", contains the wrong card list. It is a white/red deck but the deck includes 11 islands instead of 11 plains. It is otherwise fine. Heh!
This has been fixed upstream. Thanks for reporting!
- Agetian
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
11 Feb 2017, 15:28
by Agetian
correioalternativo wrote:Agetian wrote:I'm not sure about the exact playstyle here (didn't have time to check out the deck in the game), but assuming that the game goes long and you create a lot of game objects in the process (tokens, whatever), you may slowly be running out of Java heap space allocated for the game. You can try increasing it from the default 1024 MB to 2048 MB or above (values above 2-3 GB are only viable if you have 64-bit Java). You can, for example, try launching Forge using this one-line script:
java -Xmx2048m -jar forge-jar-file-name
(insert the forge JAR file name instead of "forge-jar-file-name", of course).
This sets Java heap space to 2 GB (2048M). Hopefully this will help.
- Agetian
I changed forge.command file:
#!/bin/sh
cd "`dirname \"$0\"`"
java -Xmx2048m -jar forge-gui-desktop-1.5.59-jar-with-dependencies.jar
Am I right? If so, it had little or no effect. In early versions, this deck worked fine.
Yes, you're right. Not sure why it's getting slow then, I'll try to play with this deck and see what's going on once I have a bit more time
- Agetian
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
11 Feb 2017, 16:14
by Agetian
gos wrote:My opponent had
Evolutionary Escalation during his upkeep in play but it had no effect. This happened regardless of whether he had a creature in play. In all occasions I had at least 1 creature in play.
This has been fixed upstream. Thanks for reporting!
- Agetian
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
11 Feb 2017, 18:00
by Hexadecimal
friarsol wrote:A public server for what?
For mtg using forge client
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
11 Feb 2017, 21:27
by friarsol
Hexadecimal wrote:friarsol wrote:A public server for what?
For mtg using forge client
We have a discord server. Anyone is welcome to join it
https://discord.gg/3v9JCVr
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
12 Feb 2017, 02:15
by Xitax
AI is redirecting damage from
Backfire to my planeswalker. Is this allowed?
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
12 Feb 2017, 02:58
by friarsol
Xitax wrote:AI is redirecting damage from
Backfire to my planeswalker. Is this allowed?
You control the creature, ai controls the backfire? That's legit. Why wouldn't it be?
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
12 Feb 2017, 14:04
by Xitax
Because of the wording. I was unsure if that effect could only be applied when "target player". Less intuitive when "creature's controller". Thanks for the explanation.
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
12 Feb 2017, 16:42
by GallantCrow
Sage-Eye Avengers says '[...] you may return target creature to its owner's hand if its power is less than
Sage-Eye Avengers's power', but it's currenty less than or equal to
Sage-Eye Avengers's power.
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
12 Feb 2017, 18:57
by Agetian
This has been fixed upstream. Thanks for reporting!
- Agetian
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
14 Feb 2017, 01:27
by abbyjaneway
The AI just played
Death's Caress, targeting my
Vampire Nighthawk, and gained 3 life.
Vampire Nighthawk isn't a human and there weren't any cards in play making it one.
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
14 Feb 2017, 04:16
by Agetian
This has been fixed upstream. Thanks for reporting!
- Agetian
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
15 Feb 2017, 20:52
by Xyx
Forge sometimes seems to queue up one too many priority passes. I like to play fast, so I don't have a lot of stops set. In fact, just one in M1. However, I've had a number of occasions where I'd hit Enter once to resolve an object on the stack and then Forge immediately passed my turn. It doesn't happen often (but still too often) and I'm not sure how to reproduce this.
I don't know if it's related but I've also had a number of occasions where the focus would disappear from the Yes/No buttons and I'd have to move the mouse over to click the Yes button rather than mashing Enter like I usually do. (And no, I'm pretty sure I did not mash Enter once too many when passing priority, but maybe one Enter keypress got saved up somehow.)
EDIT 1: Actually, it's the 1.5.60 snapshot.
EDIT 2: I had it happen to me again and this time I even had a stop set in M2. Maybe the focus was secretly on the End Turn button somehow? I was in M1 and pressed Enter to go to combat but Forge skipped through my Declare Attackers and M2 altogether.
EDIT 3: It happened again. The turn before was fine. I can't find a pattern.
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
16 Feb 2017, 04:18
by Agetian
Focusing code has been improved since both 1.5.59 and the latest posted 1.5.60 snapshot, so hopefully it should work better (at least those ClassCastExceptions reported in the other thread should be fixed). I've never had an actual "skip priority more than necessary" thing, so I can't comment on that yet, but let me know if you come up with a reliable test case for it where it would always misbehave for you.
- Agetian
Re: Forge Beta Release: 01-29-2017 ver. 1.5.59
Posted:
17 Feb 2017, 05:17
by abbyjaneway
I played
Blinding Beam on my turn and paid the entwine cost, targeted 2 of AI's creatures and AI. But on AI's turn his creatures untapped. There wasn't anything in play that would have overridden the creatures not untapping on AI's turn.