Fortnite Lobby Bot Commands and Controls: Panel Reference

Open the right session before sending a command

The panel controls the selected hosted account. Your real player remains in Fortnite, where you inspect party membership, leadership and the visible result. A connected bot can still be outside your party, so establish membership before diagnosing an outfit or readiness issue.

1. During an active guest trial, choose Continue to panel on the final tutorial step, or choose Skip tutorial to open the panel directly. For paid access, sign in to the website account that owns the bot and select it in My bots.
2. Check the selected name and current connection status. Compare the bot’s Epic display name when identifying it in Fortnite.
3. Finish any pending settings save. Keep one control tab responsible for changes to this bot.
4. Choose one action, read its response and inspect that result before sending another.

Quick actions: readiness, leadership and recovery

The action deck offers shortcuts without typing arguments. These are requests for the selected bot’s current connection and party. Fortnite can still reject an action when membership, authority or access does not permit it.

• Ready up — requests the bot’s Ready state. Keep your real player leading and make that player’s activity and Ready selections in Fortnite.
• Not ready — requests the bot’s Not Ready state. It does not cancel a subscription or bank unused trial time.
• Play emote — starts the bot’s configured emote. Choose an emote in Appearance and emotes if you want a different animation.
• Stop emote — stops the dance and disables its automatic emote preference while retaining the selected emote.
• Make me leader — requests promotion of the real player verified during setup. That player must already be in the bot’s party.
• New lobby — sends the bot’s leave action. Expect to invite it into the intended party again; it does not create a private matchmaking server.
• Accept friends — accepts pending friend requests on the bot. Inspect the Requests list first when you want to handle one person individually.
• Restart — reconnects this bot. Use it for a stuck connection, then recheck the party and send a fresh invitation if needed.

Choose cosmetics through Appearance and emotes

Select a slot, search the catalogue and choose an available item to apply it to the connected bot. The result belongs to that bot’s presentation. It does not add the item to your real player’s Locker.

• Outfits — change the bot’s character appearance.
• Back bling — choose the accessory on the bot’s back.
• Pickaxes — equip a pickaxe. The panel also requests a demonstration emote. If the animation fails, check whether the new pickaxe is already equipped.
• Emotes — select a dance and enable automatic emotes. Stop emote stops playback and keeps the chosen item.
• Kicks — choose the bot’s footwear. After selecting an item from the catalogue, check the result on the bot.

1. Open Appearance and emotes and select the intended slot.
2. Search for the item, then select its result once.
3. Read the save or command response and inspect the bot in Fortnite.
4. To clear an accessory through Commands, use backpack with Arguments set to none, or shoes with Arguments set to none. These clear the corresponding slot.

Displayed level, crowns and status

Attributes and chat contains fields for displayed level, displayed Battle Pass level, displayed crowns and Fortnite status. Use the field’s APPLY or UPDATE action to send its value. These edit presentation on the bot; they do not grant XP, crowns or competitive progression to the person playing.

• Displayed level: use a whole number from 1 to 9999. Example console fields: Command = level; Arguments = 25.
• Displayed Battle Pass level: use a whole number from 1 to 9999. Example: Command = bp-level; Arguments = 25. The controller keeps its stored level and Battle Pass level values aligned when either is changed.
• Displayed crowns: use a whole number from 0 to 9999. Example: Command = crowns; Arguments = 0.
• Fortnite status: enter a short message up to 100 characters. Example: Command = set-status; Arguments = Practice with friends. Returning to the default can display the service’s current default status.

Enter a command in the console

Open Commands and find LIVE COMMAND CONSOLE. The command name and its arguments have separate inputs. A catalogue card can fill the command name and show an argument hint. The catalogue is a discovery aid; the current panel and runtime still decide whether an operation is supported and authorized.

• Stop an emote: Command = stop-emote; Arguments = empty.
• Clear back bling: Command = backpack; Arguments = none.
• Clear shoes: Command = shoes; Arguments = none.
• Return leadership to the verified player: Command = promote-owner; Arguments = empty. Check that the intended player is present before using it.

1. Type the command name alone in Command, such as level.
2. Put its value in Arguments, such as 25. For a no-argument operation such as unready, leave Arguments empty.
3. Select RUN once and read the result shown below the inputs.
4. Confirm the visible result or current saved value before trying the next operation.

Find a friend and choose the specific social action

Open Friends and search for the Epic display name you intend to manage. Check the returned name before using its action. The player search offers add-friend, invite and block-user operations for that result. Your selected bot performs the action; entering a target does not switch which bot you control.

The friends, incoming-request and blocked lists provide the context for accepting, declining, removing or unblocking a person. A request and a party invitation are different actions. For your first session, the invitation walkthrough explains the tutorial’s automatic request attempt and manual-name fallback.

• To add one person, use their search result’s add-friend action and wait for the relationship to update.
• To accept one request, use that entry’s accept-friend action. Accept friends or ACCEPT ALL handles the pending list instead.
• To invite a known friend into the bot’s party, use invite for the intended result and check the resulting party. For the usual player-led setup, invite the bot from your player’s Fortnite friends list.
• Removing, blocking or declining affects a different relationship state. Choose the action for the exact person you intended; repeated requests do not resolve a block or an Epic restriction.

Party privacy, member management and custom settings

Attributes and chat exposes LOBBY PRIVACY with Public and Private choices. Select the intended option and CHANGE, then inspect the current party. In the console, privacy accepts public or private; friends is not an accepted privacy value in this panel.

Member management offers MAKE LEADER and KICK for a specified party member. Those actions depend on the bot’s authority in that party. Epic documents that only the party leader can remove members. If a human player leads, use that player’s Fortnite controls for decisions the bot cannot authorize.

GAME MODE (PLAYLIST) and CUSTOM KEY are separate advanced inputs. A playlist value must be accepted by the game, and setting a key does not grant custom-match hosting access. Epic restricts custom matchmaking to eligible accounts and modes. Choose the activity from your real player’s game screen for the normal setup; use an event’s official instructions when joining an authorized custom match.

Guest trial and paid access use different authorization

An active standard guest trial can open these bot controls without a website registration or a PRO session. The guest panel is restricted to its own linked Epic account, trial bot and valid execution session. Its original 30-minute expiry continues while you configure or reconnect.

Paid control requires the website account that owns the bot and currently confirmed subscription access. Sharing a Fortnite party does not give a friend that website access. A payment receipt, an open browser tab or a familiar nickname alone does not select or authorize the correct bot.

• Guest mode hides subscription management, bot deletion, DeviceAuth replacement and the separate Connection status view.
• Lobby rules is offered in the guest interface; the paid interface hides that tab. This is not a way to increase a Fortnite playlist’s playable team size.
• When trial control access ends, follow the state and any eligible offer actually shown. Continued bot presence does not establish continued permission to issue commands.
• Restarting or stopping the bot does not cancel a paid subscription. Use the subscription’s management process for renewal changes.

Recognize fixed settings and unsupported commands

The bot’s reported platform is fixed to Android in this setup. That is the hosted account’s platform setting, not a requirement to play Fortnite on an Android device. There is also no separate website matchmaking-region selector; inspect the real player’s Fortnite region settings when a region warning appears.

Commands found on another provider’s website can have different aliases, roles or coverage. Use the controls and spellings in this reference. For example, the console accepts stop-emote and clear accessory values as described above; a similarly named command from a larger engine catalogue is not automatically a panel operation.

Global restarts, cross-bot broadcasts and mass-management operations are not customer panel controls. A displayed command card does not grant those privileges. Choose the action for your own selected bot rather than attempting to repair an unsupported operation by adding prefixes or repeatedly submitting it.

Read pending, conflict and recovery messages

The client waits for pending settings saves before sending a command and prevents another command from overlapping on the same bot. A saved preference, a confirmed command and an effect visible in Fortnite are distinct checkpoints.

• Asked to finish the previous command: let it settle before another action. Repeated RUN clicks do not make it complete sooner.
• Settings conflict: another tab or request changed the saved version. Read the latest values and keep one editing tab.
• Action applied but preferences conflicted: inspect the live result and saved choice before repeating it. The action may already have reached the bot.
• Command confirmed but saved-preference synchronization pending: a later synchronization warning does not mean the confirmed action should be sent again.
• Connection recovering: wait for a fresh connection before retrying the party action. If access has ended, address access rather than restarting repeatedly.
• Request limited: wait for the page’s retry guidance. Do not switch accounts or flood requests to bypass the restriction.

A small control check you can repeat

After the bot joins your player-led party, verify a single appearance change and its response. Then try a presentation value you can easily compare. This gives you a useful result without depending on opponent difficulty or a particular match outcome.

1. Choose an available outfit and confirm it on the correct party member.
2. In Commands, enter level and 25 in the separate fields, select RUN and inspect the displayed result.
3. Use Play emote, then Stop emote, and check that the dance stops.
4. If you changed party membership or restarted, recheck the leader and current members before pressing Ready in Fortnite.

What these controls can establish

A successful action can establish that the selected bot changed a presentation value, updated a relationship or completed a supported party request. It does not establish an all-AI match, a private server, rewards, wins or approval from Epic. Use the linked focused guides when the problem is joining, saved settings or leadership, and consult Epic’s own rules for party permissions and custom matchmaking.