Skip to main content

​
Overview

boofstream connects to Slippi to receive live game data from your console. Connection issues typically involve incorrect port configuration, the Slippi relay not running, or network problems.

​
Common Slippi Problems

Symptoms: boofstream cannot connect to Slippi, connection fails right away.Solutions:
  1. Verify Slippi Dolphin is running with relay enabled
    • Launch Slippi Dolphin
    • Ensure the Slippi relay/broadcast feature is active
    • The console must be connected and streaming
  2. Check the port configuration
    • Default Slippi port: 53742
    • In boofstream, open Settings → Slippi Settings
    • Verify the port matches your Slippi configuration
    • Most users should use the default port 53742
  3. Confirm Slippi is listening
    • In Slippi Dolphin, check that the broadcast/relay is active
    • Look for the connection indicator showing it’s ready to stream
Symptoms: Connection fails with timeout or “connection refused” errors.How to fix:
1

Find your Slippi port

The default Slippi port is 53742. If you’ve changed this in Slippi Dolphin, note the custom port.
2

Update boofstream configuration

  1. Open boofstream
  2. Click the Settings button
  3. Navigate to Slippi Settings
  4. Update the slippi port field to match your Slippi configuration
  5. Click Save
3

Test the connection

After saving, try connecting to Slippi again from the main interface.
The port is configured in out/config.json as config.slippi.port (source: /home/daytona/workspace/source/boofstream/index.ts:64-65)
Symptoms: boofstream shows “not connected” even with correct port settings.Solutions:
  1. Start the Slippi broadcast
    • Open Slippi Dolphin
    • Make sure you’re using a version that supports broadcasting
    • Enable the broadcast/relay feature in Slippi settings
  2. Verify the console connection
    • Your Wii/GameCube must be connected to Slippi Dolphin
    • Start a game to initiate the connection
    • Check Slippi Dolphin shows an active connection
  3. Check for port conflicts
    • Only one application can use port 53742 at a time
    • Close any other applications that might be using the Slippi port
    • Restart both Slippi Dolphin and boofstream
Symptoms: Connection to Slippi drops randomly during matches.Troubleshooting steps:
  1. Check network stability
    • Ensure your console has a stable connection to your PC
    • Use a wired connection instead of WiFi when possible
    • Check for network congestion or interference
  2. Monitor Slippi Dolphin
    • Watch for disconnection messages in Slippi Dolphin
    • If Slippi disconnects, boofstream will also disconnect
    • Address console connection issues in Slippi first
  3. Review boofstream logs
    • Launch boofstream from a terminal to see console output
    • Look for disconnection events or errors
    • Errors will show connection status changes
When Slippi disconnects, boofstream automatically disconnects and clears the Slippi state. You’ll need to reconnect manually. (source: /home/daytona/workspace/source/boofstream/index.ts:343-354)
Symptoms: Connected to Slippi but character data, scores, or game results aren’t updating.Possible causes:
  1. Port matching not configured
    • boofstream needs to know which controller port belongs to which player
    • Use the port matcher interface in boofstream
    • Match controller ports to Player 1 and Player 2
  2. Game hasn’t started yet
    • Some data only appears after a game begins
    • Character detection happens when a game starts
    • Stock counts update during gameplay
  3. Automatic updates are working correctly
    • Character changes (Zelda ↔ Sheik) update automatically during games
    • Scores update when games end (unless LRAS is detected)
    • Game results are saved to the history

​
Technical Details

​
Connection Process

boofstream connects to Slippi using these steps:
  1. Creates a SlpLiveStream connection to 127.0.0.1 at the configured port
  2. Listens for game start, game end, and player frame events
  3. Automatically detects characters, stocks, and game results
  4. Updates state in real-time as games progress

​
Default Configuration

{
  "slippi": {
    "port": 53742
  }
}

​
Connection States

boofstream tracks Slippi connection status:
  • Connected: Active connection, receiving game data
  • Disconnected: No connection to Slippi relay
  • Error: Connection failed or encountered an error
The connection status is displayed in the main interface and stored in state.slippiConnected.

​
Still Having Issues?

If you’ve tried all the troubleshooting steps above:

Common Issues

General troubleshooting tips and how to report bugs

GitHub Issues

Search existing issues or report a new problem

Build docs developers (and LLMs) love

Get started for freeTalk to us