Page 2 of 10

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 26 Feb 2017, 13:35
by gos
AI attacked with a face-down Blistering Firecat into a much larger blocker. Perhaps some AI logic that should only apply if it's face-up?

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 26 Feb 2017, 13:52
by horseoftroy
Discord server !
Great news !

I suggest add a section for download latest MTG sets like
# LQ sets download

Long life for Forge , and all MTG fan games

Hope all the developers do the same

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 26 Feb 2017, 14:50
by Stampedo
Hello nice people, could someone tell me how to reset the quest.preferences?
Or share the parameters?
Thanks!

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 26 Feb 2017, 17:10
by horseoftroy
Stampedo wrote:Hello nice people, could someone tell me how to reset the quest.preferences?
Or share the parameters?
Thanks!
All the modified parameters saved inside :
Forge/data/preferences

Deleting any txt will reset all the parameters

The note you have mentioned is there , all what you need is deleting it

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 26 Feb 2017, 21:51
by Stampedo
Thanks a bunch!

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 27 Feb 2017, 02:51
by lindleya1
There's a strange bug in multiplayer commander where if I use Repay in Kind while on less than 0 hit points (I'm testing out a Lich deck), it sets the life totals of the opponents to the correct amount, but it doesn't register them losing the game. This happened in the previous game as well, but the game then correctly registered game losses after I used Wrath of God. However, in this game I have already used Wrath the previous turn, and I'm now stuck in a situation where I've won, but Forge hasn't registered my opponents losses yet.

Here is a screenshot of the board state: https://gyazo.com/fc135641fe47725b9442b9f406dad43b

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 27 Feb 2017, 14:11
by stormcat
In multiplayer game, cards like Tectonic Edge or land tax refer to wrong number.
It should be refer to an opponent cards.
But forge use the total number of all opponent's cards.
I have been reporting this bug from before.

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 27 Feb 2017, 16:19
by tjtillman
Not a bug, more of a sub-optimal AI thing, but when I play Perilous Predicament, it seems like the CPU sacrifices their best artifact and non-artifact creatures rather than their worst.

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 27 Feb 2017, 21:46
by Mrs Non-Gorilla
On turn 1 of a game, I played Aether Hub, used the autopay button to cast Oath of Nissa, and got this error message:

RuntimeException | Open
Code: Select all
Forge Version:    1.5.60-r-1
Operating System: Mac OS X 10.10.5 x86_64
Java Version:     1.8.0_31 Oracle Corporation

java.lang.RuntimeException: Cannot remove input InputPayManaOfCostPayment because it's not on top of stack. Stack = []
   at forge.match.input.InputQueue.removeInput(InputQueue.java:57)
   at forge.match.input.InputSyncronizedBase.stop(InputSyncronizedBase.java:51)
   at forge.match.input.InputPayMana.onStateChanged(InputPayMana.java:438)
   at forge.match.input.InputPayMana.showMessage(InputPayMana.java:432)
   at forge.match.input.InputBase.showMessageInitial(InputBase.java:77)
   at forge.match.input.InputProxy$1.run(InputProxy.java:73)
   at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
   at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:749)
   at java.awt.EventQueue.access$500(EventQueue.java:97)
   at java.awt.EventQueue$3.run(EventQueue.java:702)
   at java.awt.EventQueue$3.run(EventQueue.java:696)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
   at java.awt.EventQueue.dispatchEvent(EventQueue.java:719)
   at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
   at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
   at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
   at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
   at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
After clicking through, the rest of the game still seems to be working fine.

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 28 Feb 2017, 05:10
by Agetian
tjtillman wrote:Not a bug, more of a sub-optimal AI thing, but when I play Perilous Predicament, it seems like the CPU sacrifices their best artifact and non-artifact creatures rather than their worst.
This has been improved upstream. Thanks for reporting! :)

- Agetian

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 28 Feb 2017, 07:27
by Ventos
Is something wrong with the download link? Im trying about an hour but cant download.

(Edit: I dont really know if thats an issue but i finnaly managed to download Forge but when i go to the download manager it says that it will take 364 hours to download the pics O.O my net is ok here i checked and im at full 10mb)

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 28 Feb 2017, 21:40
by Ldcs8T4EAnj8h5ZMD8rf
In a game of OGW Sealed, I cast Oblivion Strike targeting the AI's Thought-Knot Seer. When Thought-Knot Seer's trigger went on the stack, the AI decided to target itself somehow, so the AI got an extra card.

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 28 Feb 2017, 22:15
by Reaper
Something wrong with the download server ??
Suggest using a different place to upload it.... According to speedtest im at arounnd 3 MB / S
but this download is going like 3.8 kb / s..

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 28 Feb 2017, 23:11
by friarsol
Amazons s3 servers were crippled all afternoon. Not sure if that's related or not

Re: Forge Beta Release: 02-20-2017 ver. 1.5.60

PostPosted: 01 Mar 2017, 00:45
by nefigah
Just dropping a note that I had this bug happen again, and I got a clearer screenshot of it this time that shows the whole board, the card detail pane, and the game log.

Agetian fixed the display problem of creatures coming out of suspend still showing the summoning sickness marker despite having haste, and indeed I haven't gotten that visual issue since his fix. But this (as in the linked post above) was a case where the creature came out of suspend definitely not having haste at all. In the screenshot, you can see the opponent only had 4 life, so I definitely wanted to finish him off with my Nihilith that had just come out of suspend that turn (see log on left). But it didn't let me attack.

Again, this bug is infrequent, and I probably played more than 20 best-of-3 matches with this deck since the last time it happened before it happened again. But at least we know it isn't a one-time fluke now!