StreamLinkr Setup Guide

Everything you need to know about installing and running StreamLinkr

📦 EXE Distribution Model

One-Click Installation

StreamLinkr is compiled into a standalone executable (.exe) file, making installation incredibly simple. No need to worry about Node.js versions, dependency conflicts, or complex setup procedures!

Key Benefits:
  • No Node.js installation required
  • All dependencies bundled together
  • Single file distribution
  • Cross-platform compatibility
  • Automatic updates capability
Compiled with
pkg Node.js Bundled

📋 System Requirements

Minimum Requirements
  • OS: Windows 10/11, macOS 10.15+, Linux
  • RAM: 512MB minimum, 1GB recommended
  • Storage: 100MB free space
  • Network: Internet connection required
Required Dependencies
XAMPP (MySQL Database)

StreamLinkr requires a MySQL database to store user data, chat history, and bot memory.

Download XAMPP

🚀 3-Step Setup Process

1
Install XAMPP

Download and install XAMPP for your operating system. Start the MySQL service from the XAMPP control panel.

5 minutes
2
Configure Settings

Use our web-based configuration tool to generate your .env file with all necessary settings.

3
Run StreamLinkr

Place your .env file next to the StreamLinkr.exe and double-click to run. That's it!

Ready to go!
File Structure
📁 StreamLinkr/
├── 📄 StreamLinkr.exe
├── 📄 .env (your configuration)
├── 📁 logs/ (auto-created)
└── 📄 README.txt
Pro Tip: The bot will automatically create necessary folders and files on first run.

🛠️ Troubleshooting

  • Ensure XAMPP MySQL service is running
  • Check if port 3306 is available
  • Verify database credentials in .env file
  • Try restarting XAMPP services

  • Verify Streamer.bot WebSocket server is enabled
  • Check host and port settings (default: 127.0.0.1:8080)
  • Ensure the password matches your .env configuration
  • Try restarting Streamer.bot application

  • Check if .env file exists in the same folder
  • Run as Administrator if needed
  • Temporarily disable antivirus (false positive detection)
  • Check Log files generated by the application
  • Check Windows Event Viewer for error details

Need Help?

If you're still having issues, don't hesitate to reach out for support!