Fox3 ServersFox3 Servers
Home
BlogGroupsDCS Mission CreatorMissionRX (Mission Tuner)PilotRXDCS LiveriesFox3 Mod ManagerPartnersSponsor ProgramAboutHelpContactStatsMy Account
Get Your Server
Fox3 ServersFox3 Servers

Turn-key dedicated DCS World and IL-2 Sturmovik game server hosting. Built by pilots, for pilots.

Ready to Fly!

Quick Links

  • DCS Servers
  • IL-2 Servers
  • Dedicated Servers
  • DCS Mission Creator
  • DCS Liveries
  • Blog
  • Groups
  • Sponsor Program
  • About
  • Contact
  • FAQ
  • Help Center
  • Partners
  • Fox3 vs Nitrado
  • Fox3 vs Host Havoc
  • Fox3 vs GTXGaming
  • Data Privacy

Connect With Us

Email: [email protected]

Support: 10:00am – 10:00pm EST, Mon–Sat

Join our Discord

© 2026 Fox3 Servers. All rights reserved.

Skin In The GameFX
All help topics

Fox3 Discord Bot

Run your Fox3 DCS server from your own Discord: restart or reboot it, switch missions, message or kick players, broadcast over SRS, watch live stats, and keep a Foothold campaign card up to date. Every command starts with /f3 and answers privately, so only the person who typed it sees the reply.

What it does

The Fox3 Discord Bot is an add-on for Fox3 DCS servers. Once it is linked to your Discord, your admins control the server with slash commands instead of logging into anything. Restarts, mission changes, player management, SRS announcements, live server stats and Foothold campaign status are all one command away, and every action is checked against your subscription, so only your own Discord can control your own servers.

You add it at checkout or later from the server upgrades page. It is also included in the Works Package.

Setting it up

  1. Invite the bot to your Discord server. You need the Manage Server permission there.
  2. Create a channel for bot commands, for example #server-control, and restrict it to the people who should be allowed to control the server. The bot only accepts commands in that channel.
  3. In that channel, run /f3setup. This tells the bot which channel to listen in.
  4. Run /f3servers. If your server is listed, you are done. If the bot says Not Registered, open a support ticket with your Discord server ID and your Fox3 server number and we link them for you.

Most commands take a server_num option, which is the Fox3 server number shown in your welcome email and on your account page (for example A2-1692). The Foothold commands skip it when you have a single server.

Server control

  • /f3status: online or offline, current mission, map, player count, paused or running, mission uptime.
  • /f3restart: restart DCS. Reloads the mission; players are disconnected for about a minute.
  • /f3reboot: reboot the whole server. Two to five minutes of downtime; use it when a restart does not fix things. Servers with Real Weather pick up fresh weather on reboot.
  • /f3pause and /f3unpause: pause or resume the simulation while players stay connected.
  • /f3autorestart set, disable, status: schedule an automatic mission restart or full reboot every 1 to 48 hours, with in-game warnings at 10, 5 and 1 minute.

Missions

  • /f3missioninfo: the mission name, file and in-mission date and time.
  • /f3nextmission: load the next mission in your rotation.
  • /f3runmission: load a specific mission by file name from your cloud Missions folder.

Talking to players

  • /f3chat: send a chat message to everyone on the server.
  • /f3announce: show a large on-screen message to every player for up to 60 seconds.
  • /f3srs broadcast: speak a text-to-speech message over your SRS radio. Pick the frequency, coalition and voice if you like.
  • /f3srs announce: the same, for long briefings, typed into a pop-up editor.
  • /f3srs play and /f3srs files: play an audio file over SRS. Drop your own MP3, OGG or WAV files into an SRS folder inside your cloud Missions folder and they show up in the list.

Players

  • /f3players: who is connected right now, with player IDs.
  • /f3kick: remove a player; they can rejoin.
  • /f3ban and /f3banbyname: ban by UCID or by in-game name, for a set number of seconds or permanently.
  • /f3unban and /f3banlist: lift a ban, or list active bans.

Live stats

These read live events from the running mission and need no setup. Tracking starts on the first call.

  • /f3stats: player versus player kill and death leaderboard for the current mission.
  • /f3statsplayer: one player's kills, deaths, crashes, ejections and favourite weapons.
  • /f3fps: server simulation frame rate, current and averaged.
  • /f3session: mission uptime, unique players, peak and current player counts.
  • /f3chatlog: the last twenty in-game chat messages.
  • /f3lastsummary: the leaderboard from the mission that just ended.

Foothold campaigns

If your server runs a Foothold mission, on any map, the bot turns the campaign's own save data into cards. Nothing is installed in the mission and nothing on the server changes.

  • /f3foothold status: which side owns each zone, each zone's upgrade slots shown as filled or destroyed, a blue versus red balance bar, both credit balances, the active missions and who was in a slot at the last save.
  • /f3foothold pilots: the pilot leaderboard by career rank, using Foothold's own ranks from Recruit up to General of the Air Force. Add sort:campaign for points earned in the current campaign, with kills by class and deaths.
  • /f3foothold me: your own card. Rank and credits to the next rank, fixed wing and helicopter hours, takeoffs, landings and carrier traps, kills by class, ejections, best air to air streak, and your points this campaign. Add pilot: with your in-game name if it differs from your Discord name.
  • /f3foothold autopost set: pick a channel and the bot keeps one public status card there, edited in place every 15 minutes to 4 hours. The card also lists the top 10 pilots by career rank with their credits and campaign points, so the leaderboard stays in view without anyone running a command./f3foothold autopost off removes it.

Every card shows when the save it was built from was written, and marks itself STALE when Foothold has not saved for a while, so an old snapshot is never mistaken for live occupancy. The auto-post card is visible to everyone who can read the channel you choose, including pilot names, ranks and points.

Recording and voice

  • /f3tacview recording and /f3tacview mode: turn Tacview recording on or off and choose one combined file or one file per pilot. Both restart DCS.
  • /f3voiceattach register: link your DCS account so VoiceAttack voice commands work in-game.

Good to know

  • Replies are private. Only the person who ran the command sees the answer, so your command channel stays readable. The Foothold auto-post card is the one exception, by design.
  • The bot works in the channel you chose with /f3setup and nowhere else. Run /f3setup again to move it.
  • Who may control the server is decided by Discord itself: give your officers access to the command channel and keep everyone else out, and the bot follows. A role with no special Discord permissions is enough.
  • SRS and Foothold commands need a server that has rebooted at least once since it was provisioned. If you see Server Not on Mesh, run /f3reboot, wait five minutes and try again.
  • Dense (shared host) plans support the bot too; the same commands work with your server number.

If something does not work

  • Not Registered: your Discord is not linked to your Fox3 account yet. Open a support ticket with your Discord server ID and Fox3 server number.
  • Authorization Failed: that server number does not belong to this Discord. Check the number with /f3servers.
  • Wrong Channel: use the channel you configured with /f3setup.
  • No Foothold save found: the running mission is not Foothold, or it has not written its first save yet. Wait a few minutes after the mission loads.
  • Foothold auto-post stopped: run /f3foothold autopost status; if it shows disabled, run /f3foothold autopost set again and make sure the bot can still see and post in that channel.

Anything else, open a ticket in our support Discord and include the server number and the exact command you ran.