v1.12.0

Fixed

Store logins appeared to be lost after a Steam update — Epic, GOG and Amazon
alike. You could sign in, the sign-in would succeed, and the store would still
say you were not connected.

SkullKey keeps each store's session under the active Steam account, so that two
people sharing a console do not inherit each other's libraries. Finding that
account relied on two things Steam has since changed:

• registry.vdf no longer publishes a numeric ActiveUser
• loginusers.vdf no longer carries MostRecent

Both probes came back empty, so SkullKey fell back to a generic profile — an
empty one — while your real session sat untouched in the folder belonging to your
actual account.

Epic showed it worst, because its configuration is reached through a symlink that
was being repointed at the empty profile on every run: a fresh login was written
to one folder and read back from another. GOG and Amazon receive their paths
directly, so they were simply looked up in the wrong place.

The active account is now resolved from AutoLoginUser, matched by account name,
then from AutoLogin, then from the most recent Timestamp. The older
ActiveUser and MostRecent keys are still tried first, so an older Steam
behaves exactly as it did before.

Nothing was lost. Your sessions are still in the account folder they were
written to, and become visible again as soon as the account is detected properly.
If you signed in several times while this was happening, the most recent session
is the one to keep — the others are simply idle copies under other profiles.