BOTLOBBIESLink an Epic Account Safely for Your Bot Session
Account linking deserves a quiet moment before party setup. You need to understand which Epic account a flow is using and which website account will manage the resulting session. The useful outcome is a recognizable, correctly associated bot, not a screenshot of sensitive login information. Keep passwords, device authorizations, and tokens private throughout the process.
Check the account context before continuing
A browser may already be signed in to an Epic account from an earlier visit. Before approving a link, check the account identity presented by the flow. Do not assume it is the account you intended simply because the browser continued without asking you to sign in again. This matters especially on shared devices or when you manage more than one account.
Also distinguish the real player you use in Fortnite from the bot account being connected. Party invitations and ownership checks become confusing when those roles are mixed together. If the account shown is wrong, stop before completing the association and return through the normal account-selection process. Repeating the flow quickly is less useful than confirming the identity once.
Keep the authorization inside the intended flow
Follow the linking process reached from your own session in the service. Treat a login or approval request from an unrelated message as a separate request that needs checking. A person offering help does not need your Epic password, browser cookies, refresh token, or device authorization to explain how to invite a bot.
Authentication material can remain sensitive even when it looks like a random identifier instead of a password. Avoid copying a whole browser response, debug object, or authorization screen into a public channel. If a page displays private account data, keep that page out of screen sharing and recordings until you have moved past it.
- Do not share passwords, recovery codes, cookies, or authentication tokens.
- Review the account and requested approval before accepting it.
- Use a browser session and device you control when possible.
- Describe errors by their visible message and action rather than by posting credentials.
Verify the result before spending trial time
After linking, look at the account or bot identity shown in your panel. Compare it with the bot you intend to invite in Fortnite. If the association is unexpected, resolve that mismatch before starting a timed session or sending invitations to several similarly named accounts.
For a first trial, prepare your player and browser before starting the 30-minute period. A completed account link is not proof that the bot has already joined a party. The bot connects automatically when its session can start; you then invite it from your real player's party and keep that player as leader.
Ask for help without exposing the account
A useful problem report says which stage failed: selecting an account, approving the link, seeing the bot in the panel, or receiving a party invitation. Include the visible error and approximate time if available, with personal information removed from screenshots. If you believe private authorization material has been exposed, use the account provider's own security and session controls. Do not keep circulating the material while trying to diagnose the original linking issue.