There are many iterations of this code, I think this is the latest one. I forgot it even existed but since one of the old ones has been leaked I might as well release this.
Over all iterations we maybe used it like ten times back in early 2019.
On official servers these viewers push your Matchmaking game (Valve Competitive 5v5 only) to the top of the GOTV watch list. You can also boost other peoples matches by simply joining their GOTV server. Overall it takes 2-3 minutes for the viewers to first show up. Expect this to get fixed soon.
Maybe. Valve will probably community ban you or even disable your account if they catch you use it. Though a friend has been playing around and getting to very high numbers (100K+) without getting banned or anything, though now that its public this might change. As always: I am not responsible for any bans of any kind. Use at your own risk.
Your target MUST be broadcasting on Steam publicly. There are two methods of broadcasting on Steam:
To be able to broadcast you MUST be a non-limited user.
git clone --recursive https://github.com/BeepIsla/steam-viewbot.git
cd steam-viewbot
config.json
to your likingnode index.js
This version sends an HTTP request to Steam for wanting to watch a Steam Broadcast, this creates a new viewer and gives you some tokens. Viewers expire if you don't send a heatbeat after ~90 seconds (If I remember correctly), so we use a Steam connection and protobufs to send keep alives for all of our viewers. From testing this seems to max out at ~30K (Again, if I remember correctly) which doesn't really make sense according to math but whatever, bad code I guess.
The Steam connection is an anonymous Steam logon, we use Steam because sending keep alives through that is MUCH faster and more efficent than creating an entirely new HTTP request (Thank you protobufs).
I was also testing around with zipping up multiple protobuf requests and sending them as one single packet but sadly this doesn't seem to be possible, or I did something wrong.
target
: SteamID64 of your viewbot targetheartbeatInterval
: Delay in milliseconds between sending heartbeatsmaxViewers
: Maximum amount of viewers you wantworkers
: How many workers we want, a worker creates viewersdelayBetweenWorkerRequest
: Delay in milliseconds between creating a new viewermaxRequestsInFlightPerWorker
: Maximum amount of in-flight requests allowed per workerproxy
enabled
: Enable proxies or not? I don't know if I ever tested this but its irrelevant anywaysmaxErrors
: Maximum amount of errors a proxy is allowed to have before switching, if we reach the end of the proxy list it will wrap back around to the first onefiles
: Array of file locations or URLs to fetch proxies from