Skip to content

Conversation

@DealsBeam
Copy link

Moved the account-saving logic in src/onelauncher/main_window.py to after the game has been launched. This prevents the last_used_world_name from being updated if the game launch is canceled or fails.

Also includes a fix for a Python 3.12 compatibility issue in src/onelauncher/utilities.py.

google-labs-jules bot and others added 2 commits November 1, 2025 21:55
Moved the account-saving logic in `src/onelauncher/main_window.py` to after the game has been launched. This prevents the `last_used_world_name` from being updated if the game launch is canceled or fails.

Also includes a fix for a Python 3.12 compatibility issue in `src/onelauncher/utilities.py`.
Fix: Account details saved only after successful game launch
@JuneStepp
Copy link
Owner

Moved the account-saving logic in src/onelauncher/main_window.py to after the game has been launched. This prevents the last_used_world_name from being updated if the game launch is canceled or fails.

That info is purposefully saved after the account is authenticated but before the game is launched. Can you let me know your reasoning for why you want different behavior?

Also includes a fix for a Python 3.12 compatibility issue in src/onelauncher/utilities.py.

Python 3.12 support requires quite a bit more work than that. Thanks for the thought, though.

I'd also appreciate it if in the future, you can avoid using AI for PRs or at the very least thoroughly review the code.

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