BetaDeps v0.7.1 — PatchShield opt-out
BetaDeps v0.7.1 — PatchShield opt-out
Released 2026-05-24.
Small follow-up to v0.7.0 that adds a way to turn PatchShield off.
New
Toggle PatchShieldbutton in Mod Config. Sits next toToggle Auto-Disablein the Options → Mod Config button row. Default behavior is PatchShield ON (the v0.7.0 shipped state). Click the new button to createModules\BetaDeps\patchshield-disabled.flag; the next launch'sPatchShield.Install()then bails on every lifecycle pass and consumer-mod prefixes that throwMissingMethodException/MissingFieldException/TypeLoadExceptionpropagate unmodified. Click again to delete the flag and re-enable.- Confirmation popup explains the new state and that a restart is required.
Why
Mod authors debugging their own work want exceptions to surface unmodified instead of being swallowed and unpatched. Users who suspect PatchShield is interfering with another shim need an off-switch. PatchShield only catches managed exceptions in-memory (no LauncherData.xml edits), so the conservative default stays ON — but you can now opt out without a code change.
Note the asymmetry with Toggle Auto-Disable:
Toggle Auto-Disableis opt-IN (file presence = enabled). Off by default because it modifiesLauncherData.xml.Toggle PatchShieldis opt-OUT (file presence = disabled). On by default because it only intercepts managed exceptions.
Files in this release
BetaDeps-v0.7.1.zip— drop intoModules\(unzip →Modules\BetaDeps\)
Verifying the install
When PatchShield is on (default), Modules\BetaDeps\runtime.log shows lines like:
[BetaDeps.PatchShield] shield pass: +510 new, 0 already-shielded, 0 skipped (total shielded: 510)
After clicking Toggle PatchShield and restarting, the same log instead shows:
[BetaDeps.PatchShield] patchshield-disabled.flag present — PatchShield disabled; skipping install. Click 'Toggle PatchShield' in Mod Config to re-enable.
That confirms the opt-out took effect.