Crash when setting deck selection menu display parameters for generated deck options on the Constructed tab

[dracontes]

Describe the bug/To Reproduce On a fresh start and on the Constructed tab, go to the deck selection menu. There, select "Random Color Decks" and set the menu's display to "Image view". Then set "group by:" to "Color Identity" and "pile by:" to "Color". A crash ensues. Quit Forge, then start it up again. It promptly crashes starting up.

Expected behavior Plainly, that the game wouldn't crash while doing something that works elsewhere, like the Card Catalog. Though, since this seems to happen for generated decks while the described filtering applies with no issue for decks saved to file, perhaps those filtering options should be disabled on principle for generated decks since, I assume, by their nature they won't be as defined and filterable as the decks on file are.

Relevant Files Here are the crash logs: 2024-05-04-00_deckmenu.txt 2024-05-04-00_followupcrash.txt

Desktop:

• OS: Windows 11
• Version: 1.6.62-SNAPSHOT-04-18

Additional context A few years ago, this was something I found happening for the "Random Commander Card-based Decks" option, where the distinction between multicolored and otherwise monocolored commanders was relevant. Then last month, while reviewing the notes jotted down at the time, I found the bug also happened for "Random Commander Decks". Earlier today and while preparing this report, I found that the issue just that more wider in scope. An out from having Forge permanently unusable is to go into \AppData\Roaming\Forge\preferences and edit item_view.preferences to remove any instances of COLOR_IDENTITY and DECK_COLOR from <config> tags. That file can also deleted. Also, though I'm not sure how relevant this is, Forge takes about 5 and a half minutes to sort the 2000+ face commanders on "Random Commander Decks" with the "group by:" "Color Identity" filter. Maybe I'm misunderstanding things, but on the Card Catalog such sorting takes less than a second.

[github-actions[bot]]

This issue has not been updated in a while and has now been marked as stale. Stale messages will be auto closed.