BOTLOBBIESFortnite Bot Friend Request Errors: Identify the Relationship State
A failed friend request is a social action failure, not automatic evidence that the bot is offline. The account may already be a friend, have a pending request, be blocked, or be subject to a restriction reported by Epic. Establish the relationship between the correct player and bot accounts before repeating the request or changing hosting settings.
Confirm which Epic accounts are involved
Compare the bot's linked Epic display name with the account visible in Fortnite. A hosting nickname is not always the same name. Also confirm the player account currently signed into the game; switching accounts can make a previously accepted relationship appear to be missing.
Search carefully rather than sending requests to several similar names. If the interface offers a confirmed account match, use that result. A request sent to the wrong account cannot be repaired by restarting the intended bot. Keep private account identifiers out of public support messages even when they are useful inside the service's authenticated panel.
Inspect the relationship before sending again
Check both the friend list and pending requests. A request can be outgoing on one account and incoming on the other. If the accounts are already friends, move on to inviting the bot from the player's party instead of creating another request. If you are comparing two screens, refresh their social lists before deciding they contradict each other. An older pending-request view can remain visible after the relationship has changed on the other account.
- Already friends: confirm the correct account, then use a party invitation.
- Incoming request: accept it through the appropriate account's supported interface.
- Outgoing request: check whether it is still pending before retrying.
- Blocked account: review the block relationship deliberately rather than repeatedly submitting requests.
Treat limits as explicit errors, not guessed numbers
If Epic or the panel reports a friendship limit or a restriction, keep the exact safe code and its time. Do not assume a universal maximum from an old guide or another account. Limits and account conditions can differ, and an error needs to be connected to the action that produced it.
A command rejection means the action was rejected or returned an error response. It does not establish which limit was reached unless the available evidence says so. An operation that expired without confirmation is different again: it may require checking the resulting friend state before any further request.
Retry deliberately and preserve a useful report
Avoid clicking Add Friend, Accept All and Remove Friend in quick succession. Those actions can change the same relationship while earlier requests are still being processed. After a failed or uncertain operation, refresh the relevant social view and inspect the actual relationship first.
If help is needed, say whether the request was incoming, outgoing, already accepted or blocked, and include the safe error code and time zone. Explain whether party invitations work once friendship is confirmed. This separates social permissions from party access and connection problems without exposing private messages or authentication data. A functioning connection does not guarantee that every social action will be accepted.