626 Mod Launcher v0.5.1

Mod managers for games that don't use a mod loader.

Some Unreal games — Witchfire is the one that prompted this — have no UE4SS or script loader. Their mods are content paks that you drop straight into Content/Paks, right next to the game's own files. The launcher didn't know how to manage those, and adding such a game turned up no mods at all.

What's new in v0.5.1

• Loader-less Unreal-pak games are first-class now. Add a game like Witchfire and the launcher manages the mods that live directly in Content/Paks — listing your mods and never the base game. The 4GB game paks are recognized as the game (by name and size) and can never be listed as a mod or moved by a toggle, so you can't accidentally disable the game itself.
• Metadata fetches for more games. Witchfire's mods now pull their real title, author, and links from Nexus on install. (A game needs to be in the launcher's Nexus-domain map for this; Witchfire's now is.)
• Honest dependency chips. A plain content pak no longer claims it "needs UE4SS" — that warning now shows only on the mods that actually need it (Lua scripts and Blueprint LogicMods paks). If your game's mods are content paks, you'll see no false framework warning.

Reversibility holds throughout: the base game is protected on both the disable and uninstall paths, and nothing here changes how your existing games are managed.

Updating from 0.5.0 is a small delta — the launcher pulls it on its next check, or grab the Setup.exe below.