tmi.js | 💬 Javascript library for the Twitch Messaging Interface | Chat library

Try this:

Instead of checking if the message is a command, you can check if the message contains a command, strip the command away and keep the command arguments.

You have a typo in option object, instead of option.indentity should be option.identity. Try with

It doesn't look like channel metadata is available over the Twitch WebSocket API. If you want to get that information, you'll need to go through the "New Twitch API" and use the /streams endpoint.

You will also need to have a Client-ID to make requests to this endpoint. You can get one by following the instructions here: Apps & Authentication Guide.

Once you have a Client-ID, you can make a request. I'm using the node-fetch module to make requests easier. This example will get the 2 most active streams. You can adjust the query string parameters to get the appropriate stream.

You can store function in var and call that query function inside it so that whenever you want it you can use it. But it needed to be handled asynchronously.

for example

There is no "best" way. That's pretty much a matter of opinion which will vary according to experiences, requirements and just personal preference. There are dozens of different good ways for two processes to communicate. Any of them can work just fine for the relatively simple situation you describe. I'll offer a couple of ideas.

First off, is there any reason you don't just add a web UI directly to the bot? Then, you just have one program. You can add a web interface to the bot that exposes a control panel interface. node.js makes it pretty easy to add a web interface (probably use Express and your favorite template sub-system). Then the web interface has direct access to the bot and can control it directly.

Second, if you have some compelling reason that the control panel should be a separate program, it could also be written in node.js using something like electron.

Third, if you insist on C# for the control program, then you just have to decide what TCP-based scheme you want to use for the two program to talk to one another. For one way communication (control panel sending requests to the bot), you can expose a simple http interface on the bot and just send http requests to that interface from the C# control program. One can create an http interface with a few control methods in your node.js program in literally about 5 minutes. You'd then use whatever library C# gives you for sending http requests to another server.

If you want/need two way communication between bot and control panel so the bot can regularly send information to the control panel, then you could connect the two with a socket.io connection and then you'd have a continuous bi-directional communication channel open between the two. You'd add a socket.io server to your node.js app and use a socket.io library in your C# application. The C# application would then create the socket.io connection to your bot and you can then send data/commands either way over that connection.

The problem with your code is that you are using fs.readFile which is of asynchronous in nature. that means the script won't wait for the json read operation to complete, it will continue executing line by line. So after readFile your code then directly executes the client.on event. Here is an interesting read about asynchronous javascript

Solutions to your problems is that you either handle async nature of code or use readFileSync(documentation) which is the synchronous version of readFile.

You can create .env file and add it to .gitignore file.

in the .env file insert your variable like that:

If you take the following line: var code = message.split(' ')[1];

...and change it to the following, it should help: var code = message.split(' ')[1];

You had two spaces as the separator argument to split() where you should have only had one.

See here for documentation for String.prototype.split()