Skip to content

v0.3.3-alpha — Installer Fix (Program Files (x86))

Choose a tag to compare

View all tags
@dysmorphis-hub dysmorphis-hub released this 29 May 21:33
v0.3.3-alpha
2f6c141

EVE Combat AI v0.3.3-alpha — Installer Fix

This is an installer-only fix release. The mod itself is unchanged from v0.3.2.
If EVE already works for you, you do not need to reinstall anything.

What went wrong

The v0.3.2 installer was supposed to fix a crash for users whose Starfield lives in C:\Program Files (x86)\Steam\…. The fix was incomplete — it patched most of the install script but missed one line: the Starfield detected: message that prints your detected game path.

That one line still used immediate (%) variable expansion. In a Windows batch file, the literal ) inside Program Files (x86) was read as the end of a code block, so the installer broke apart and failed silently mid-install — exactly the bug v0.3.2 claimed to have fixed. If your Starfield was anywhere without parentheses in the path, you never saw it; if it was in the default Steam location, the installer quietly died.

What's fixed

  • Every game-path reference in both installers (install.bat and the backend installer) now uses delayed (!) expansion, which is evaluated after the batch parser has finished reading the block. The ) in your path is now harmless data.
  • Version strings bumped to 0.3.3-alpha across the installers and READMEs so you can confirm you have the fixed build.

Huge thanks to Bneezy for catching that the v0.3.2 fix hadn't actually taken, and for posting the corrected approach in the comments. This one's on us — the changelog said "fixed" when it was only half-fixed.

Downloads

  • AI Backend (GitHub — this page): grab the 0.6B build for lower-VRAM cards, or 1.7B for better tactical decisions. Run install.bat.
  • Plugin (Nexus Mods): re-uploaded at v0.3.3 to keep versions in lockstep — the plugin files are byte-identical to v0.3.2, so Vortex users don't need to do anything if already on v0.3.2.

Reminder: the quest re-bind after every update

Starfield's Papyrus engine bakes EVE's quest binding into your save, so after any EVE update you must, once:

stopquest <EveAdapterQuest FormID>  →  save  →  reload  →  startquest <FormID>  →  save

(For installer-only fixes like this one, you only need the re-bind if you actually reinstall the backend. If EVE is already running fine, leave it alone.)

Assets 4
Loading