Sign-ins and security codes
How the updater signs a launcher in for you, and what to do when a code is asked for.
Updated 2026-09-24
What it does#
A signed-out launcher downloads nothing. When you have stored that launcher's login on your page, the updater can type it in on the server by itself, and ask you for the security code if the launcher wants one. You reply with the code in Telegram and it carries on.
This works today for Steam, Battle.net, EA and Epic. Riot needs no login to update.
For Epic, store the email and password of the Epic account the server uses (under Accounts, as "Epic"). Epic sometimes forgets a saved sign-in even though it looks remembered; when its screen shows the sign-in page, the updater signs it back in. If Epic ever asks you to prove you are a person (a picture puzzle), the updater stops there - sign in once on the server yourself.
How to use it#
- Store the login on your dashboard, under Accounts (see Your dashboard page).
- /signin steam bob asks the updater to sign that account in now.
- When a code is needed, the bot writes to you. Reply /code 12345 with the code from your phone, email or authenticator app. It waits about five minutes.
- On Steam's mobile approval screen, approving on your phone is enough - there is no code to send.
A Steam sign-in with a code looks like this in Telegram:
Tip: Store the login once on your dashboard (Accounts) and you rarely need /signin at all - the nightly signs a launcher back in by itself and only writes to you when a code is needed.
Note: The updater tries a stored login at most once a day per launcher, on purpose: a launcher that rejects a password twice can lock the account, and a wrong password at midnight should not become twelve attempts by morning.
What the reply means#
| Message | What it means |
|---|---|
| Steam wants a Steam Guard code to finish signing 'bob' in | Reply /code with the five characters from your Steam app or email |
| Battle.net wants a security code | Reply /code with the digits from your authenticator |
| EA wants a verification code, sent to that account's email | Reply /code with it |
| Steam rejected the stored password for 'bob' | The saved password is wrong or was changed; update it on your page |
| signed in as 'bob'. Steam did not keep the credential | It worked, but the launcher will ask again next time; not a fault |
| Windows is locked on this server, so I could not type the sign-in | Nothing on the screen can be read or typed while the session is locked; unlock it, or leave it signed in |
When something needs you#
- No code arrives on your phone. Check the account is the one stored on your page, then send /signin again to start a fresh attempt.
- "tried today already". The one-attempt-a-day rule. Fix the stored password first, then ask again - a /signin you send yourself is allowed.
- A launcher that keeps signing out usually has an antivirus or a cleanup tool clearing its session. Tell your provider; they can look at the log.