BOTLOBBIESUsing a Hosted Fortnite Lobby Bot from a Console
A hosted bot runs away from your console. Your console remains the device you use to play Fortnite, while a browser gives you access to the bot's panel. You can keep those roles separate on two screens: your own player in the game and the bot's session controls on a phone or computer. That arrangement avoids treating the bot as another local controller or console profile.
Prepare the browser before entering the timed session
Sign in to your website account on the device you plan to use for controls. Identify the bot that belongs to the session and check the access information. For a free trial, the session lasts 30 minutes, so it is useful to finish the ordinary console setup before starting it. Have your player ready in Fortnite rather than spending the first part of the trial signing in or updating the game.
Use a device you control for the panel. A shared phone or public computer adds account-management work after the session, including signing out and checking that the browser has not retained your access. You never need to give another player your Epic password or copy authentication tokens to let them join a party.
Build the party on the console
Keep your own console player as party leader and invite the correct bot through Fortnite's social controls. The website account you use to manage the bot is not itself a party member. Watch the console's party list to confirm the bot actually joined; an available website panel alone does not prove party membership.
- Open Fortnite on the console with the player account you intend to use.
- Create the party with that player as leader and check the party's invitation permissions.
- Find the assigned bot in the game's social interface and send its invitation.
- Wait for the bot to appear in the party before continuing with your player's activity and Ready selections.
Use the second screen for deliberate changes
Choose one customization in the browser, apply it, and look at the bot on the console. This gives you a visible check that the change reached the party. Sending several different outfits or emotes while switching screens makes a delayed update harder to interpret. If a change is still pending, wait before sending the same request again.
The bot connects automatically, so a large Connect button is not part of the routine. If valid access remains but the connection is stuck, the Restart control provides a recovery action. A restart can remove the bot from the current party temporarily; after it reconnects, check whether another invitation is needed.
Separate console issues from hosted availability
When your player cannot access Fortnite normally, investigate the console or game connection first. When your player is fine but the bot is unavailable, check the bot's current session and access in the browser. For region warnings, use Fortnite's own region settings; the website has no region selector. Before handing the controller to somebody else, explain which player leads and which browser is controlling the bot so those roles remain clear.