Linking a sign-in provider
Sign in to your existing Hot Spots account, then open Account → Sign-in methods.
Choose Link my Google account or Link my Discord account when the service is enabled. If Hot Spots still needs to verify your email, choose the provider account with the matching verified email.
Google or Discord can sign in to an existing account when the provider returns its matching verified email. An identity already linked to another account cannot be reassigned.
Sign in again if your session is older than ten minutes before changing linked accounts or other protected security settings.
Passwords and recovery
Email registration sets your chosen password after confirmation. Accounts created through Google or Discord can add a password under Account > Sign-in methods.
Choose Email > Forgot password? to request a reset link when email delivery is enabled.
Disconnecting one provider leaves the other provider linked. Set another usable sign-in method before disconnecting your only method.
If email delivery and provider sign-in are unavailable, ask a site administrator for help. Administrators can manually verify an account, but only after checking the account owner.
Returning after an assistant timeout
Sign-in returns to the normal game task, including when a background update detected the timeout. Aces snapshot and receipt-query URLs are not login destinations.
The assistant keeps an expired tab and its unsaved entries open. Choose Sign in again, authenticate in the new tab, then return to the original tab and choose Resume this page. Resume refreshes authorization and form protection; it does not submit a save.
Use Check earlier save for an uncertain response before manually retrying. If an ordinary refresh is already running, the requested check waits for it; the save itself is never retried automatically. Use the original account to resume its draft. Your normal Stacked or Side by side browser preference is retained.
Session inactivity
The application currently uses an eight-hour inactivity check. Your host can expire PHP session storage sooner; the hosting administrator must retain sessions for at least eight hours for that window to be effective. There is no in-app timeout setting. Credential changes and account access restrictions still invalidate sessions.
If the tabletop session expires, use Sign in again, then Resume this page to recover retained unsaved entries. Do not repeat an uncertain save automatically.