Forge Beta Release: 08-02-2016 ver 1.5.55
Moderators: timmermac, Blacksmith, KrazyTheFox, Agetian, friarsol, CCGHQ Admins
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by Xzarf » 12 Sep 2016, 03:38
Description: Game Startup crashes when it get to "Loading Quest"
I was 52 games into a Quest Game when this happened.
First occurred with an older version of both the game and Java. Have updated both and same crash still happens every time. Have deleted both game and Java and reinstalled.
- RuntimeException | Open
I was 52 games into a Quest Game when this happened.
First occurred with an older version of both the game and Java. Have updated both and same crash still happens every time. Have deleted both game and Java and reinstalled.
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by redsmith12 » 12 Sep 2016, 07:26
Bug Report
Description:
The abilities of Tokens which should be triggered when they leave play are not triggering when they are "championed".
Notes:
Tested with Changeling Hero, Lightning Crafter, and Changeling Berserker as champions.
Kiki-Jiki, Spitting Image, and Vitu-Ghazi Guildmage were used to make token copies.
Meadowboon, Slithermuse, Fiend Hunter, and creatures with Champion were tested for their leave the battlefield triggers.
This bug only happens when the token is championed, not when it is exiled or destroyed.
The leave the battlefield triggers on non-tokens still trigger when they are championed.
Other abilities that trigger when a creature leaves play, such as Outpost Siege or Kjeldoran Elite Guard, still trigger. Just not the token's own abilities.
I don't know when the bug was introduced, but the interaction used to work correctly.
Description:
The abilities of Tokens which should be triggered when they leave play are not triggering when they are "championed".
Notes:
Tested with Changeling Hero, Lightning Crafter, and Changeling Berserker as champions.
Kiki-Jiki, Spitting Image, and Vitu-Ghazi Guildmage were used to make token copies.
Meadowboon, Slithermuse, Fiend Hunter, and creatures with Champion were tested for their leave the battlefield triggers.
This bug only happens when the token is championed, not when it is exiled or destroyed.
The leave the battlefield triggers on non-tokens still trigger when they are championed.
Other abilities that trigger when a creature leaves play, such as Outpost Siege or Kjeldoran Elite Guard, still trigger. Just not the token's own abilities.
I don't know when the bug was introduced, but the interaction used to work correctly.
Last edited by redsmith12 on 14 Sep 2016, 01:15, edited 1 time in total.
- redsmith12
- Posts: 6
- Joined: 27 Jan 2016, 20:44
- Has thanked: 2 times
- Been thanked: 0 time
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by Hanmac » 12 Sep 2016, 07:48
@redsmith12:
Thanks for telling, I will check that out and see if it does still happen in the trunk. If yes then it might have something to do with token getting exiled.
Thanks for telling, I will check that out and see if it does still happen in the trunk. If yes then it might have something to do with token getting exiled.
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by friarsol » 12 Sep 2016, 12:35
Did you see this thread already? viewtopic.php?f=26&t=18921Xzarf wrote:Description: Game Startup crashes when it get to "Loading Quest"If anyone can help with this is would be great. I have been helplessly addicted to this game again and am suffering serious withdrawal symptoms. *Twitch twitch*
- RuntimeException | Open
I was 52 games into a Quest Game when this happened.
First occurred with an older version of both the game and Java. Have updated both and same crash still happens every time. Have deleted both game and Java and reinstalled.
Your quest file got corrupted, but there should be a backup if you can find the Forge data directory.
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by Xzarf » 12 Sep 2016, 14:14
Alrighty then, that seems to have fixed things.friarsol wrote:Xzarf wrote:Description: Game Startup crashes when it get to "Loading Quest"
Did you see this thread already? viewtopic.php?f=26&t=18921
Your quest file got corrupted, but there should be a backup if you can find the Forge data directory.
Thanks so much for the help and sending my life back off the straight and narrow to suffer the addiction once again.
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by DaniUG » 14 Sep 2016, 09:06
Description: My turn has just ended. Testing an Animar deck. There isn't anything in the stack and at the beginning of its turn the AI plays Brass Herald and the game crashes. The AI has enough cards in the deck. Noothing werid going on, no effects that are going to be applied when the cards enters the battlefield....
- UnsupportedOperationException | Open
Even the smallest spark may set a world ablaze
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by Hanmac » 14 Sep 2016, 09:21
You reported that bug more than 3 times before, and I did say it's already fixed in trunk.DaniUG wrote:Description: My turn has just ended. Testing an Animar deck. There isn't anything in the stack and at the beginning of its turn the AI plays Brass Herald and the game crashes. The AI has enough cards in the deck. Noothing werid going on, no effects that are going to be applied when the cards enters the battlefield....
- UnsupportedOperationException | Open
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by Ldcs8T4EAnj8h5ZMD8rf » 14 Sep 2016, 16:00
So I'm attempting to play Modern Scapeshift versus Modern Merfolk and I have gotten a crash that the application cannot continue from in all four attempted games. The reports, judging from memory, appear to be identical. All crashes have come after the AI has completed its actions in Main Phase 1 and I have clicked the OK button to advance to the Begin Combat Phase. In the first two games, the crash occurred after the AI resolved Master of Waves and received its Elemental tokens. In the third game, the AI played its fourth Island on its fourth turn and attempted no other actions. In this fourth game, the AI has not played a third land on its third turn and, as stated above, I have pressed OK to advance to Begin Combat. Below is the crash report for the fourth crash and a screenshot of the board with game log.
- | Open
- Attachments
-
- Ldcs8T4EAnj8h5ZMD8rf
- Posts: 36
- Joined: 13 Nov 2015, 15:36
- Has thanked: 1 time
- Been thanked: 2 times
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by NouvelleVoix » 17 Sep 2016, 01:59
Description: I had just entered a tournament in quest mode and was choosing a card (Rubbleback Rhino, I think?) when the game crashed. It was on pack 7, I think?
- NullPointerException | Open
- NouvelleVoix
- Posts: 3
- Joined: 17 Sep 2016, 01:56
- Has thanked: 0 time
- Been thanked: 0 time
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by Hib » 17 Sep 2016, 10:52
When downloading set pictures ingame, Forge doesn't download any token pictures for sets from BNG onwards.
They aren't skipped like missing pictures, rather Forge doesn't even try to download them.
The assiocated token art will be correctly displayed when the pics are manually added to the tokens folder.
They aren't skipped like missing pictures, rather Forge doesn't even try to download them.
The assiocated token art will be correctly displayed when the pics are manually added to the tokens folder.
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by cocii » 17 Sep 2016, 11:28
Bug with Conflagrate
If you cast Conflagrate from your hand for 0, the spell won't go to the stack and will neither go to the graveyard. Instead the log just says: "CAn not add Conflagrate to the stack". I suppose the spell somehow expects at least 1 target or something.
So, summary:
What I do: Cast Conflagrate for 0 from my hand.
Expected behaviour: Spell should go to the stack, resolve with 0 targets and go to the graveyard.
Actual behaviour: Spell just disappears, does not go to the stack nor to the graveyard (making flashback impossible)
If you cast Conflagrate from your hand for 0, the spell won't go to the stack and will neither go to the graveyard. Instead the log just says: "CAn not add Conflagrate to the stack". I suppose the spell somehow expects at least 1 target or something.
So, summary:
What I do: Cast Conflagrate for 0 from my hand.
Expected behaviour: Spell should go to the stack, resolve with 0 targets and go to the graveyard.
Actual behaviour: Spell just disappears, does not go to the stack nor to the graveyard (making flashback impossible)
Re: Forge Beta Release: 08-02-2016 ver 1.5.55
by friarsol » 17 Sep 2016, 16:58
Looks like this is fixed in the trunk already.cocii wrote:Bug with Conflagrate
If you cast Conflagrate from your hand for 0, the spell won't go to the stack and will neither go to the graveyard. Instead the log just says: "CAn not add Conflagrate to the stack". I suppose the spell somehow expects at least 1 target or something.
So, summary:
What I do: Cast Conflagrate for 0 from my hand.
Expected behaviour: Spell should go to the stack, resolve with 0 targets and go to the graveyard.
Actual behaviour: Spell just disappears, does not go to the stack nor to the graveyard (making flashback impossible)
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Who is online
Users browsing this forum: No registered users and 90 guests