Skip to content

Fix native onboarding and MO2 launch configuration handling - #57

Merged
nlbdotdev merged 3 commits into
mainfrom
fix/native-onboarding-and-ttw-acceptance
Oct 14, 2026
Merged

nlbdotdev merged 3 commits into
mainfrom
fix/native-onboarding-and-ttw-acceptance

Conversation

@nlbdotdev

Copy link
Copy Markdown
Owner

First-run live onboarding now opens native installation directly, with Wabbajack prerequisites explained in their own flow. Real TTW acceptance also exposed two configuration gaps: generated executables could not retain the baseline's Steam app ID, and normal MO2 plugin persistence blocked subsequent launches.

Add an optional target/store-matched Steam app ID declaration without changing legacy bytes or receipts. Limit semantic INI reading to the launch/profile sections while retaining alias, duplicate, path, executable and local-save checks. Record the full-size separate-version reconstruction and library admission, plus the unresolved Steam load error: restoring the app ID alone did not fix direct startup, and no footage or gameplay pass is claimed.

Validation: pnpm check (zero errors/warnings); full pnpm test (183 passed, one optional skip); git diff --check. The real app verified/admitted all 13,952 outputs; all 31 protected files retained their hashes. Recording preferences and the candidate-only diagnostic setting were restored. Existing portable/depot artifacts keep their original provenance.

@nlbdotdev
nlbdotdev merged commit 2ecdd68 into main Oct 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant