π KickViewerBOT v3.0.2 β Proxy WebSocket Support & Version System
β¨ What's New
π Proxy-Tunneled WebSocket Connections
Viewer connections now route through your proxies via SOCKS4/SOCKS5/HTTP tunnels. Each viewer appears from a unique IP address, dramatically improving viewer count accuracy and scalability.
- π― Each WebSocket connection is tunneled through a dedicated proxy
- π More stable and accurate viewer counts on Kick
- π‘οΈ Supports SOCKS4, SOCKS5, and HTTP proxies with authentication
- β‘ Automatic fallback to direct connection if a proxy fails
π₯ Stability Mode Enhancements
- π― Persistent connections with regular handshakes and session maintenance
- π Periodic tracking events to keep viewer counts stable
- π‘οΈ Full Kick protocol compliance: ping/pong, user_event, error handling
- β‘ "Set & forget" mode with monitoring and automatic reconnection
π Fixes & Improvements
- β Fixed viewer count dropping after 1 minute
- β Improved WebSocket message handling and Kick protocol compliance
- β Better resilience with exponential backoff on reconnections
- β Enhanced proxy rotation and token management
- β No admin/UAC required β uses non-reserved ports automatically
- β Frontend: correct display of active connections count
π₯ Getting Started
- Download the executable for your platform below
- Run
KickViewerBOTβ no admin privileges required - Load your proxies and enable Stability Mode for best results
Need help? Open an issue: https://github.com/H1B0B0/Kick-Viewerbot/issues
Thanks for your support! π