Skip to content

Add Activate on launch feature to SS3#3

Open
gonlad-x wants to merge 2 commits into
borgCode:masterfrom
gonlad-x:activate-on-launch
Open

Add Activate on launch feature to SS3#3
gonlad-x wants to merge 2 commits into
borgCode:masterfrom
gonlad-x:activate-on-launch

Conversation

@gonlad-x

Copy link
Copy Markdown

Same implementation as TarnishedTool. Tested, all seemed to behave as expected.

SilkySouls3_73EwnDx6iM

gonlad-x added 2 commits July 20, 2026 15:46
Port TarnishedTool's Activate On Launch feature: ActivateOnLaunchManager
for persisted settings storage, per-tool feature checklist, and the
same lifecycle-driven architecture as TarnishedTool/SekiroTool - a
master enable toggle, a singleton settings window (viewmodel injected
via constructor, DataContext set internally) opened via a bound
command from SettingsViewModel with reuse/Activate() instead of
spawning duplicates, and AppStart/Attached/Loaded/OnNewGameStart state
subscriptions matching the reference implementation.
Enabling target-lock hooks conceptually belongs to when the game is
actually loaded into a session, not at tool boot before any game
state exists - matching where the rest of Loaded-gated,
session-dependent Activate On Launch options already live.
@gonlad-x

Copy link
Copy Markdown
Author

One thing I just realized is that if you close the tool without unchecking your activated options, they will remain activated until you quit the game. But from my testing this also happens with the current v2.0.0 so I don't think it's something that the Activate on launch feature is introducing?

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