626 Mod Launcher v0.5.0
Two things this release fixes that the launcher used to get wrong on your files.
Break free from Vortex
Moving off Vortex used to leave you stuck. Vortex drops ownership markers in the folders it deployed into, and the launcher — playing it safe — treated those folders as read-only, hands-off. So mods the launcher installed itself could end up unmanageable, with the uninstall button hidden, just because Vortex's old marker was still sitting there.
Now you can take a folder over. When the launcher sees a Vortex-managed folder, it offers to take it over: a banner above your mods, and a prompt the moment you try to manage one. Take it over and the launcher archives Vortex's marker out of the way (moved, never deleted — fully reversible) and manages the folder normally from then on. If Vortex later re-deploys into a folder you took over, the launcher notices and says so instead of silently fighting it. Game-scoped, consent-gated, never touches a game the launcher doesn't support.
Play vanilla actually means vanilla
"Play vanilla" used to be a label that lied. On games where mods load by file presence — pak mods, UE4SS — a plain launch runs with your mods, so the button was telling you something that wasn't true.
Now it's a real two-mode launch:
- Play vanilla steps every active loader aside — your pak mods, the UE4SS loader, direct-inject DLLs — so the game runs genuinely clean. They stay aside until you switch back; nothing's guessed from when the game closes.
- Play modded puts back exactly what you had — if you had eight of twelve mods on, you get those eight back, not all twelve.
The button tells you which mode you're in and how it launches (Play vanilla (Steam) / Play modded (Steam)). Everything moves to a holding folder and comes back on demand — a failed step-aside never strands your mods.
Updating from 0.4.4 is a small delta — the launcher pulls it on its next check, or grab the Setup.exe below.