Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

I found the log from the second Coram crash.


neo-anterior.log contains a full exception at the point the game exited:


java.lang.NullPointerException:

Cannot invoke "forge.game.zone.Zone.isCardAddedThisTurn(...)"

because the return value of "forge.game.card.Card.getZone()" is null


The stack then goes through CardProperty.cardHasProperty,

SpellAbilityRestriction.checkZoneRestrictions / canPlay,

Spell.canPlay,

Card.getAllPossibleAbilities,

and AvailableActions.


This was the game where Henzie was actually my commander and Coram was one of the 99. I drew Coram, put him onto the battlefield, attacked with him, his mill trigger resolved, and then the game failed as combat advanced.


That seems potentially significant because Coram specifically creates permission to play cards from graveyards that were put there from libraries that turn, and the exception is occurring while the engine is checking whether a card was added to a zone this turn and whether it can be played.


I can send you both neo.log and neo-anterior.log. The exception is in neo-anterior.log.


Can I attach files to these replies? 


In answer to your Coram question... I have attacked with him twice and it happened both times. In both cases I did look through the discards after everyone milled, then attacked, then the game exited.

Oh and there was no hs_err_pid1234.log file

Hi Wind — the new build is up.

Before you launch it: bring your stuff across.

NeoForge keeps everything of yours inside a single folder called datos, right next to NeoForge.exe. Your decks, your settings, your Ascent and Adventure saves, and all the card art it has already downloaded live in there — nothing is stored anywhere else on your PC.

So:

  1. Unzip the new version into a new folder.
  2. Open your old NeoForge folder and copy the whole datos folder into the new one.
  3. Launch the new NeoForge.exe.

That's it. Do it before the first launch and everything is exactly where you left it — same decks, same settings, and it won't re-download the card images. If you launch it first by accident, no harm done: just close the game and copy your old datos over the new one, replacing it.

Don't copy anything else across. forge.profile.properties in particular is rewritten every time the game starts, so the new build will sort itself out wherever you put the folder.

What's in this build:

  • The enlarged card in the deck builder closes properly now — Escape, or a click anywhere. No more restarts.
  • The crash that ended your Coram games is fixed. It was a bug in Forge's rules engine that took the whole game process down; the interface now catches it and plays on.
  • The stack shows the actual cards, in order, and each one expands to show what it does and what it's targeting. There's a switch in Settings if you ever want the old compact text list back — it's still the better one when fifteen triggers are chained up.
  • Card keywords are now clickable when you enlarge a card: click deathtouch, vigilance and so on to see what they actually do.
  • Plus a batch of new cards and rules fixes that came in from upstream Forge, including the Reality Fracture set.

Thanks again for both reports — the log you dug out is what made the second one findable.