Skip to content

Release 3.0.1

Choose a tag to compare

@H1B0B0 H1B0B0 released this 16 Oct 19:07

πŸš€ KickViewerBOT β€” Stability Update & Deployment Notes

✨ Key Highlights

πŸ”₯ Stability Mode

Stability Mode remains the core of this release: it maintains long-lived WebSocket connections and emulates real browser behavior to stabilize viewer counts.

  • 🎯 Persistent connections: regular handshakes and session maintenance
  • πŸ“ˆ Stable viewer counts: periodic tracking events
  • πŸ›‘οΈ Platform-friendly behavior: ping/pong, user_event, and error handling
  • ⚑ "Set & forget" mode with monitoring and automatic reconnection

πŸ”§ Smart Port Management

We've simplified deployment: the executable no longer requires administrator privileges. We no longer use the reserved ports 80 and 443 that required elevated rights.

  • No UAC elevation required for the Windows executable
  • The bot now uses non-reserved ports and automatically discovers a free port
  • Fewer permission and firewall issues during installation and runtime

πŸ› Fixes & Improvements

  • βœ… Fixed the viewer count dropping after 1 minute (improved tracking)
  • βœ… Better handling of WebSocket messages and Kick protocol
  • βœ… Improved resilience with exponential backoff
  • βœ… Enhanced logging for easier debugging
  • βœ… Improved proxy rotation and token management
  • βœ… Frontend: correct display of "Active Connections"

πŸ“₯ Deployment Notes (Recommended Practices)

  1. The provided executable no longer needs to run as administrator on Windows: simply run KickViewerBOT.exe as a standard user.
  2. If you're behind a strict firewall or network endpoint, allow the binary to establish outbound connections on the configured ports (by default, the bot selects a non-reserved port).
  3. Check your OS/antivirus rules if the executable is blocked on first run.

πŸ“₯ Getting Started

  • For Stability Mode: download and run the executable as a standard user, enable Stability Mode in settings, and adjust thread count.
  • For Standard Mode: works as before with short-lived connections.

πŸ’‘ Why this update matters

  • Before: elevation was required to bind to reserved ports (caused deployment friction).
  • Now: simplified install and run experience, reduced friction for users.

Need help? Open an issue: https://github.com/H1B0B0/Kick-Viewerbot/issues

Thanks for your support β€” this update makes the bot easier to deploy and more robust. πŸ™