itch.io

Oh and there was no hs_err_pid1234.log file

I want to echo the stack point:

The stack is where magic is won and lost (in my opinion). I learned so much through the stack display in manabrew. I am still learning. I do find your stack very hard to use. It would be huge if the actual cards showed on the stack and you could expand them to see their order and read what they do. 

I do want to congratulate you on such an impressive app. This must have been, and continues to be, a huge effort.

Wind

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.

As another data point: coram does not have to be the commander for this bug to manifest. I tried a deck with him in it, but not the commander. Almost identical situation (except with only two bots). Game stopped again

BUG / UI: Enlarged card view can become impossible to close in deck builder

I have repeatedly run into a UI problem while building and reviewing Commander decks.

In the deck builder, opening/enlarging a card from the graphical card areas can bring up the larger card view, but I cannot find any way to dismiss it and return to what I was doing.

I have tried:

- Escape

- left-clicking

- right-clicking

- Spacebar

None of those closes the enlarged card.

I see the problem in the graphical deck-building/card-browsing area, and also in the "View the deck" screen where the deck is displayed by categories (Commander, Creatures, Spells, Artifacts, Enchantments, Lands, etc.). Clicking one of those cards can enlarge it and leave me unable to get back out of the enlarged-card view.

The text/card-name list on the right side of the normal deck-building screen does not seem to create the same problem.

The only reliable way I have found to recover is to close/restart Neo Forge. I have had to restart the program approximately 6-7 times because of this while working on one deck.

This does NOT appear to be a problem during an actual game; card viewing during gameplay has worked normally for me so far.

If there is already supposed to be a specific command for closing the enlarged card, it would be helpful to make that visible. If there is one, I have not been able to find it despite trying the normal mouse and keyboard options above.

I am using the current Windows Neo Forge download as of September 8, 2026.

BUG: Coram, the Undertaker attack causes Commander game to exit

I am playing a 4-player Commander game against 3 AI opponents using Coram, the Undertaker as my commander.

Reproduction sequence:

1. Coram, the Undertaker was on the battlefield as a 0/5.

2. I declared Coram as an attacker.

3. Coram's attack trigger resolved correctly and each player milled a card.

4. One of the milled creature cards caused Coram's power to update correctly from 0/5 to 2/5.

5. I advanced combat toward the Declare Blockers / Combat Damage portion of combat.

6. At that point Neo Forge abruptly exited the game.

There was no winner, loser, draw, or other game-ending result shown. The game simply closed/exited back out of the match.

I am not completely certain whether the exit occurred immediately upon entering Declare Blockers or when it automatically advanced through blockers because nobody blocked, but it occurred immediately after the Coram attack/mill sequence while combat was advancing.

The milling itself appeared to resolve correctly and Coram's power updated correctly before the failure.

This is particularly important for Coram because his attack trigger is a central part of how the commander functions.

I am using the current Windows Neo Forge download as of September 8, 2026.

Please let me know if there is a log file I can provide or a specific test you would like me to run to help reproduce it.