Skip to content

Allow Play to reuse a saved Battle.net login - #31

Draft
zasbu wants to merge 3 commits into
LightforgeProject:mainfrom
zasbu:zasbu/play-auto-login-7f5cbb38
Draft

zasbu wants to merge 3 commits into
LightforgeProject:mainfrom
zasbu:zasbu/play-auto-login-7f5cbb38

Conversation

@zasbu

@zasbu zasbu commented Nov 13, 2026 •

Copy link
Copy Markdown

When WoW is started directly, its Remember Account checkbox still leaves users entering a password each launch. An opt-in play_via_battle_net = true setting now routes the main Play action through the existing Battle.net handoff, allowing the client's saved sign-in to carry into the game. Existing configurations keep direct launches.

Only the Play action changes. The existing preflight, addon wait, readiness, game tracking and Stop paths are reused. Managed-game update errors give refresh/update guidance instead of inviting a repeated Play handoff. Documentation covers configuration, rollback and authentication limits.

Validation: 173 GUI tests, 45 Battle.net tests, 43 config tests and six deterministic behavior evaluations passed; release build succeeded. One independent code review passed after fixes to legacy-config coverage and update-error guidance. Installed locally and verified that the restarted process uses the built binary and the enabled setting. Live validation passed after one-time Battle.net installation reconciliation and enabling Seamless Battle.net Mode: WoW reached character selection and the user confirmed automatic login.

@simplykenny

Copy link
Copy Markdown
Member

Thanks for this. The "Launch via Battle.net" button under PLAY already does exactly this route, so I'm keeping PLAY direct for now (same answer as #22). If I make it switchable later it'll be a Settings toggle, and I won't have Battle.net update a Lightforge-managed install, so the update-error change and the doc can't go in as they are.

I will let this PR open for now, i will come back when i plan to do something like that

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.

2 participants