One person per event needs to set up FTA Buddy as the host. This is typically done on the FMS computer (or a laptop plugged into the FMS network) at the start of the event. Once hosted, all other volunteers can join with the event password.
Go to ftabuddy.com/manage/host to start the setup wizard.
FTA Buddy reads live field data through a Chrome browser extension that connects to FMS at 10.0.100.5.
The setup page shows two status indicators:
10.0.100.5. If red, make sure the computer is connected to the FMS network.You must have FTA permission before running this software on the FMS network.
If you don't want the extension to connect to SignalR enable Notepad Only Mode on this step. In this mode:
Every robot's Auto Tower and Endgame Tower starts unset, and FMS will not commit a match until all six have a selection. During field setup nobody is on the scoring tablets, so closing out a test match means clicking through the whole panel first.
Score Autofill sets the ones still unset to "None" when the match reaches the commit state, so you can commit straight away. It is off by default, and it only runs in a test match or a practice match - in quals and playoffs it does nothing. Test matches are recognised by their match number (999 on the primary field, 998 secondary, 997 practice), because FMS reports a test match at whatever tournament level is currently activated. Turn it on here, from Event Management > Configure Extension, or from the cog on the Scorekeeper page; they are all the same setting, and any of them changes the running extension. The Scorekeeper cog works from the scorekeeper's own laptop - it reaches the extension through the server, not through the browser it is installed in.
It needs the Field Monitor running over SignalR against real FMS. It does not appear in Notepad Only Mode, scraping mode, or Cheesy Arena mode.
Anything a ref did pick is left alone. The scoring tablets broadcast each change to every client, so FTA Buddy tracks what has been selected since prestart and only fills the gaps. A robot whose selection was made before FTA Buddy connected counts as unset and gets "None" - at worst that overwrites a selection with the value it already had, and the tablets show the change.
Once the extension is detected and FMS is connected, click Next.
Enter the event code that matches the event's key on The Blue Alliance (TBA). For example: 2026mitry.
The app validates the code against TBA.
The event code is auto-filled from FMS if the extension is connected - verify it before proceeding.
A password is auto-generated for you in a memorable two-word-plus-number format (e.g. robot-field-42). You can change it to any password you prefer. Share this password with all volunteers who need access to the event.
Once both fields are valid, click Create Event.
After creating the event, you'll land on the Event Settings page. You can return here any time at ftabuddy.com/manage/event-settings.
From here you can:
If your event runs multiple fields simultaneously (e.g. a championship with multiple fields), you can link them as a meshed event. Each field creates its own event, then one is designated as the "mesh" that aggregates the others. Go to ftabuddy.com/manage/meshed-event to configure this.
Once the event is created, share the password with:
Volunteers enter the password on the Login page to join the event.