EvoForge — Update

Thanks to TheDirtyAlien and valecant for their reports that made this update possible.

• The app wouldn’t start at all. If content.kspkg couldn’t be found, EvoForge would crash before its window even opened — a console flashing briefly and closing instantly, with no error message. It now always starts and clearly tells you what’s missing.

• content.kspkg wasn’t being detected. The detection system only checked a few hardcoded paths. It now asks Steam where its libraries are located, so any installation location works — regardless of the drive or the library name.

• The path couldn’t be set manually. The error message told you to configure it in Settings, but no such option existed. Settings now includes a Game data (content.kspkg) field that accepts the file itself, its containing folder, the game folder, or a Steam library.

• Path detection has been hardened across the board. EvoForge no longer guesses where your files live — it asks Windows and Steam directly, so unusual setups are handled instead of silently failing.

• 🐧 Native Linux build. No more Wine — just download, unzip, and run: EvoForge.