MJOLNIR Launcher changelog
MJOLNIR Launcherv0.8.2

The Xbox app version, found

Mod setup on the Xbox app copy of the game failed looking for a Win64 folder. That build ships in WinGDK; the launcher now finds it, and finds Xbox app installs on its own.

launcher-v0.8.2 on GitHubDocumentation

The Steam copy of Halo Campaign Evolved keeps its executable under Meteorite\Binaries\Win64. The Xbox app installs a different build of the same game, and that one lives under Meteorite\Binaries\WinGDK — inside a Content folder, inside Halo- Campaign Evolved, inside Xbox Games. The launcher only knew the Steam layout, so on an Xbox install every setup ended with Game binaries directory not found, and pointing it at the folder by hand made no difference: it found the game, then looked for Win64 anyway.

Fixed

  • Xbox app installs. UE4SS, the runtime and the mods now go into whichever binaries folder the store actually shipped — Win64 on Steam, WinGDK on the Xbox app. Everything that reads or writes there follows: install, verify, enable and disable, the mod list, and the hub's code mods.
  • Finding it. The launcher probes the Xbox app's folders on its own now, both the older XboxGames and the newer Xbox Games library names, the dashed Halo- Campaign Evolved folder, and the Content folder the game sits in. Picking any of those by hand in Settings resolves to the right root too.
  • The setup screen shows the folder the install is really going into, rather than always saying Win64.
  • Launching by executable looks for HaloCampaignEvolved.exe, the name both stores use, instead of the placeholder names it tried before.

Notes

  • Whether UE4SS itself runs against the Xbox build is a separate question this release does not answer. The signatures the runtime ships are tuned against the Steam executable; the WinGDK one is a different build. If it loads but does nothing, that is the next thing to look at, and a report with your ue4ss\UE4SS.log is the fastest way there.