Background

Fortnite LobbyBot

Commands are not working

If the bot is not responding to your messages or commands, follow this guide to identify and fix the most common issues.

Updated ·

Reading time ·

4 minutes

Check that the bot is online and in your party

The bot must be online and present in your party to respond to commands. If it is offline or not in your lobby, it will ignore all messages.

Verification Steps:

  1. Make sure the bot is visible in your party
  2. Check the bot’s online status in your friends list
  3. If the bot left or disconnected, reinvite it and wait until it fully loads into the lobby
  4. Confirm that command permissions are enabled in your category configuration

Use the correct chat channel

Ensure you are sending commands in a chat channel the bot can read:

  • Party Chat Only: Commands must be typed in Fortnite party chat, not game chat
  • Platform Limitations: Website-hosted bots cannot read party chat, use the FNLB App Chat to send commands instead
  • Message Visibility: Verify that your messages appear in the FNLB chat log
  • Text Only: Voice chat is not supported; commands must be sent as text

Command syntax and spelling

Incorrect syntax is one of the most common causes of command failures:

  • Exact Keywords: Use the command or cosmetic name exactly as documented
  • No Extra Content: Do not include emojis, symbols, or unrelated text
  • Case Sensitivity: Some commands may be case-sensitive, try different capitalization if unsure
  • Proper Spacing: Use correct spacing for multi-word commands
  • Special Characters: Avoid special characters unless explicitly required

For correct usage examples, see the official commands reference.

When to contact support

If commands are still not working after following all steps above:

  1. Check Service Status: Temporary outages may affect command processing, check FNLB Status
  2. Review Documentation: Commands may have changed, recheck the command reference
  3. Ask the Community: Join the FNLB Discord to see if others are experiencing the same issue
  4. Try Another Bot: Some bots have limited or different permissions, testing another bot can help isolate the problem

Still need help?