Google Chrome
Open chrome://extensions, enable Developer mode, then choose Load unpacked.
Manifest V3 · ZIP packageFor match processors
The Tracker Companion opens queued match pages in the background, reads the rendered scoreboard, and returns the result to SpikeSync. Choose your browser package, then connect it with the credentials from your tournament operator.
You only need this if your tournament operator asked you to process matches. Players and spectators do not need to install anything.
Desktop browsers only. Keep the computer and browser running while processing matches. These packages do not support mobile installation.
Each package contains the same companion, prepared for that browser's extension system.
Open chrome://extensions, enable Developer mode, then choose Load unpacked.
Manifest V3 · ZIP packageOpen edge://extensions, enable Developer mode, then choose Load unpacked.
Manifest V3 · ZIP packageOpen about:debugging#/runtime/this-firefox and choose Load Temporary Add-on.
Firefox 128 or newer · ZIP packageThese packages are installed locally, so your browser will ask you to use its extension developer tools. Firefox's temporary installation must be repeated after Firefox closes.
Choose your browser above, download the ZIP, and extract it somewhere you will not move or delete.
Open your browser's extension tools and select the extracted folder or its manifest.json file.
Open the companion settings and enter the SpikeSync backend URL and companion token supplied by your tournament operator.
Select Save and test, leave automatic processing enabled, and keep the browser running when matches need processing.
If the connection test fails, check the backend URL and token with your tournament operator. Never post the token in public chat. Firefox temporary add-ons must be loaded again after closing Firefox.