rfbomb/twitch-watcher

Automatic watching the twitch to get Valorant drop

Twitch watcher

This is a fork that utilizes the HELIX API to determine who to watch

Features

• 🎥 True HTTP Live Streaming support (Forget the #4000 error code)
• 🔐 Cookie-based login
• 📜 Auto accept cookie policy
• 👨‍💻 The choice of a random streamer with drop-enabled tag
• 🤐 Unmuted stream
• 🛠 Detect mature content-based stream and interact with it
• 🛡 Proxy option
• 📽 Automatic lowest possible resolution settings
• 🧰 Highly customizable codebase
• 📦 Deployable to VPS by docker
• 🏳️ Helpful support community
• 💬 Multi language readme: 🇫🇷 README 🇧🇷 README 🇷🇺 README 🇸🇰 README

Grab your Login Token

1. Login to your twitch account
2. Open inspector(F12 or Ctrl+Shift+I) on main site
3. Find the stored cookie section
4. Copy auth-token -- This is your LoginToken

Getting your API Authorization Token

1. Login to your twitch account
2. go to this page I have set up: https://rfbomb.github.io/DockerWatcherAuthPage.io/
3. Click the 'Authorize' button. This will send a request to the Twitch authorization server, which will provide a unique key, similar to the LoginToken keys above.
4. Copy ApiToken once is it displayed on the page. This token will be used for the 'ApiAuthToken' variable.

Requirements

• Windows or Linux OS
• Network connection (Should be obvious...)
• Nodejs and NPM

Installation

1. Grab your Login & API Auth Tokens
2. Clone this repo
3. Install Chromium
   • Linux TUTORIAL 🤗
4. Locate Chromium executable:
   • Linux -> whereis chromium or whereis chromium-browser
   • Windows -> Usually the path to the Chromium executable is: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
5. Navigate your command prompt / terminal into this the folder you downloaded the repo into
6. Install the dependencies with npm install
7. Start the program with npm start

Docker

Docker is a set of platform as a service (PaaS) products that uses OS-level virtualization to deliver software in packages called containers. Containers are isolated from one another and bundle their own software, libraries and configuration files. All containers are run by a single operating system kernel and therefore use fewer resources than virtual machines.

Requirements

• Docker
• Docker-Compose

Usage

1. Download docker-compose-example.yml
2. Rename docker-compose.yml
3. Customize Environment Variables
   • LoginToken environment variable
   • ApiAuthToken environment variable
   • streamersUrl environment variable
4. Run with docker-compose up -d command

Dependencies

Troubleshooting

What do the tokens look like?

auth-token: rxk38rh5qtyw95fkvm7kgfceh4mh6u

---

Streamers.json is empty?

Try again with higher delay. Default delay:

const scrollDelay = 2000;

Go to code

---

Something went wrong?

Try non-headless mode. Set headless value to true, like this:

const showBrowser = true;

Go to code

---

Proxy?

Yes, of course:

const proxy = ""; // "ip:port" By https://github.com/Jan710

Go to code

OR

With Docker env:

proxy=PROXY_IP_ADDRESS:PROXY_PORT

---

Screenshot without non-headless mode

const browserScreenshot = false;

Go to code

Donation

Please donate to keep alive this project!

My Fork that uses the Helix API:

Original Source:

Support

• Keybase at https://keybase.io/d3v_
• Discord at https://discord.gg/s8AH4aZ

Disclaimer

This code is for educational and research purposes only. Do not attempt to violate the law with anything contained here. I will not be responsible for any illegal actions. Reproduction and copy is authorised, provided the source is acknowledged.

twitch-watcher's Issues

[Docker] ChannelName_3 is interpreted as UserTimezone

In the app.js at line 102 you are initializing the var UserTimeZone with the Enviroment Variable ChannelName_3:
UserTimeZone = (process.env.ChannelName_3 || 'America/New_York');

So if the ChannelName_3 Var is used in e.g. the docker-compose.yml, the twitch-watcher will not start: "Error: RangeError: Invalid time zone specified: warframe"

This only affects Docker-Container, because normally the code in Line 119 would be executed:
UserTimeZone = (await UserSettings.ReadConfigSetting('UserTimeZone') || 'America/New_York');

UserTimeZone could then also be mentioned in the docker-compose-example.yml file :)

[Docker] Request to https://api.twitch.tv/helix/streams failed

=========================
🔎 Checking config file...
✅ Env config found

=========================
📱 Launching browser...
🔧 Setting User-Agent...
🔧 Setting auth token...
⏰Setting timeouts...
----------- Loaded Variables ------------
ChannelName_1 - nmplol
ChannelName_2 -
ChannelName_3 -
streamersUrl - https://www.twitch.tv/directory/game/iRacing
TimeZone - America/New_York
minWatching - 15
maxWatching - 30
IgnoreRandomChannels - true
----------- End of Loaded Variables ------------
🤬 Error: FetchError: request to https://api.twitch.tv/helix/streams failed, reason: getaddrinfo EAI_AGAIN api.twitch.tv
at ClientRequest. (/usr/src/app/node_modules/node-fetch/lib/index.js:1461:11)
at ClientRequest.emit (events.js:315:20)
at TLSSocket.socketErrorListener (_http_client.js:432:9)
at TLSSocket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:84:8)
at processTicksAndRejections (internal/process/task_queues.js:84:21) {
message: 'request to https://api.twitch.tv/helix/streams failed, reason: getaddrinfo EAI_AGAIN api.twitch.tv',
type: 'system',
errno: 'EAI_AGAIN',
code: 'EAI_AGAIN'
}
(node:25) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'error' of undefined
at Object.TestAPIToken (/usr/src/app/HelixAPI.js:98:14)
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async SetupVariables (/usr/src/app/app.js:156:9)
at async main (/usr/src/app/app.js:644:3)
(node:25) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:25) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.