starwolfy / steam-ts Goto Github PK

npm start

[email protected] start G:\GitHub\steam-ts
node lib/launch.js

Trying to connect to the TeamSpeak server...
Logged into the query with credentials.
Using virtual server 1 now.
Changed query client name.
Succesfully launched the bot.
Admin panel available on port: 8080
GET / 302 10.081 ms - 56
GET /login 304 7.722 ms - -
GET /stylesheets/bootstrap.min.css 304 7.911 ms - -
GET /stylesheets/ie10-viewport-bug-workaround.css 304 33.177 ms - -
GET /stylesheets/signin.css 304 32.147 ms - -
GET /stylesheets/sticky-footer.css 304 33.036 ms - -
GET /stylesheets/toastr.min.css 304 33.269 ms - -
GET /javascripts/jquery.min.js 304 32.830 ms - -
GET /javascripts/ie10-viewport-bug-workaround.js 304 1.125 ms - -
GET /javascripts/socket.io-1.4.5.js 304 1.633 ms - -
GET /javascripts/toastr.min.js 304 2.674 ms - -
GET /javascripts/login.js 304 3.452 ms - -
GET /fonts/glyphicons-halflings-regular.woff2 304 0.232 ms - -
GET /index 404 3.362 ms - 887
GET /favicon.ico 404 1.287 ms - 887
Successfully queried users and updated userdata.
GET /login 304 5.209 ms - -
GET /stylesheets/bootstrap.min.css 304 19.566 ms - -
GET /stylesheets/ie10-viewport-bug-workaround.css 304 34.131 ms - -
GET /stylesheets/signin.css 304 34.506 ms - -
GET /stylesheets/sticky-footer.css 304 34.521 ms - -
GET /stylesheets/toastr.min.css 304 35.405 ms - -
GET /javascripts/jquery.min.js 304 36.515 ms - -
GET /javascripts/socket.io-1.4.5.js 304 1.586 ms - -
GET /javascripts/toastr.min.js 304 3.834 ms - -
GET /javascripts/ie10-viewport-bug-workaround.js 304 9.594 ms - -
GET /javascripts/login.js 304 21.776 ms - -
GET /fonts/glyphicons-halflings-regular.woff2 304 0.292 ms - -
GET / 302 1.783 ms - 56
GET /login 304 1.619 ms - -
Error: Can't set headers after they are sent.
at validateHeader (_http_outgoing.js:494:11)
at ServerResponse.setHeader (_http_outgoing.js:501:3)
at ServerResponse.header (G:\GitHub\steam-ts\node_modules\express\lib\response.js:767:10)
at ServerResponse.contentType (G:\GitHub\steam-ts\node_modules\express\lib\response.js:595:15)
at ServerResponse.send (G:\GitHub\steam-ts\node_modules\express\lib\response.js:145:14)
at done (G:\GitHub\steam-ts\node_modules\express\lib\response.js:1004:10)
at View.exports.renderFile [as engine] (G:\GitHub\steam-ts\node_modules\ejs\lib\ejs.js:363:10)
at View.render (G:\GitHub\steam-ts\node_modules\express\lib\view.js:135:8)
at tryRender (G:\GitHub\steam-ts\node_modules\express\lib\application.js:640:10)
at Function.render (G:\GitHub\steam-ts\node_modules\express\lib\application.js:592:3)
GET /stylesheets/bootstrap.min.css 304 13.182 ms - -
GET /stylesheets/ie10-viewport-bug-workaround.css 304 29.147 ms - -
GET /stylesheets/signin.css 304 29.761 ms - -
GET /stylesheets/sticky-footer.css 304 29.526 ms - -
GET /stylesheets/toastr.min.css 304 29.739 ms - -
GET /javascripts/jquery.min.js 304 29.072 ms - -
GET /javascripts/ie10-viewport-bug-workaround.js 304 1.444 ms - -
GET /javascripts/socket.io-1.4.5.js 304 2.026 ms - -
GET /javascripts/toastr.min.js 304 2.651 ms - -
GET /javascripts/login.js 304 3.283 ms - -
GET /fonts/glyphicons-halflings-regular.woff2 304 0.278 ms - -
GET / 302 1.086 ms - 56
GET /login 304 1.931 ms - -
Error: Can't set headers after they are sent.
at validateHeader (_http_outgoing.js:494:11)
at ServerResponse.setHeader (_http_outgoing.js:501:3)
at ServerResponse.header (G:\GitHub\steam-ts\node_modules\express\lib\response.js:767:10)
at ServerResponse.contentType (G:\GitHub\steam-ts\node_modules\express\lib\response.js:595:15)
at ServerResponse.send (G:\GitHub\steam-ts\node_modules\express\lib\response.js:145:14)
at done (G:\GitHub\steam-ts\node_modules\express\lib\response.js:1004:10)
at View.exports.renderFile [as engine] (G:\GitHub\steam-ts\node_modules\ejs\lib\ejs.js:363:10)
at View.render (G:\GitHub\steam-ts\node_modules\express\lib\view.js:135:8)
at tryRender (G:\GitHub\steam-ts\node_modules\express\lib\application.js:640:10)
at Function.render (G:\GitHub\steam-ts\node_modules\express\lib\application.js:592:3)
GET /stylesheets/bootstrap.min.css 304 0.403 ms - -
GET /stylesheets/ie10-viewport-bug-workaround.css 304 5.552 ms - -
GET /stylesheets/signin.css 304 0.595 ms - -
GET /stylesheets/sticky-footer.css 304 1.168 ms - -
GET /stylesheets/toastr.min.css 304 2.158 ms - -
GET /javascripts/jquery.min.js 304 3.184 ms - -
GET /javascripts/ie10-viewport-bug-workaround.js 304 6.441 ms - -
GET /javascripts/socket.io-1.4.5.js 304 7.447 ms - -
GET /javascripts/toastr.min.js 304 8.210 ms - -
GET /javascripts/login.js 304 9.425 ms - -
GET /fonts/glyphicons-halflings-regular.woff2 304 0.276 ms - -
GET / 302 1.053 ms - 56
GET /login 304 1.656 ms - -
Error: Can't set headers after they are sent.
at validateHeader (_http_outgoing.js:494:11)
at ServerResponse.setHeader (_http_outgoing.js:501:3)
at ServerResponse.header (G:\GitHub\steam-ts\node_modules\express\lib\response.js:767:10)
at ServerResponse.contentType (G:\GitHub\steam-ts\node_modules\express\lib\response.js:595:15)
at ServerResponse.send (G:\GitHub\steam-ts\node_modules\express\lib\response.js:145:14)
at done (G:\GitHub\steam-ts\node_modules\express\lib\response.js:1004:10)
at View.exports.renderFile [as engine] (G:\GitHub\steam-ts\node_modules\ejs\lib\ejs.js:363:10)
at View.render (G:\GitHub\steam-ts\node_modules\express\lib\view.js:135:8)
at tryRender (G:\GitHub\steam-ts\node_modules\express\lib\application.js:640:10)
at Function.render (G:\GitHub\steam-ts\node_modules\express\lib\application.js:592:3)
GET /stylesheets/bootstrap.min.css 304 14.206 ms - -
GET /stylesheets/ie10-viewport-bug-workaround.css 304 22.808 ms - -
GET /stylesheets/signin.css 304 23.886 ms - -
GET /stylesheets/sticky-footer.css 304 24.360 ms - -
GET /stylesheets/toastr.min.css 304 24.581 ms - -
GET /javascripts/jquery.min.js 304 24.849 ms - -
GET /javascripts/ie10-viewport-bug-workaround.js 304 1.475 ms - -
GET /javascripts/socket.io-1.4.5.js 304 1.993 ms - -
GET /javascripts/toastr.min.js 304 2.597 ms - -
GET /javascripts/login.js 304 3.180 ms - -
GET /fonts/glyphicons-halflings-regular.woff2 304 0.257 ms - -
Successfully queried users and updated userdata.
Successfully queried users and updated userdata.
GET / 302 0.847 ms - 56
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such file or directory, open 'G:\GitHub\steam-ts\webserver\sessions\dp2fdHLUddHI5VcN-78MSYs0WDKYZS7W.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such file or directory, open 'G:\GitHub\steam-ts\webserver\sessions\dp2fdHLUddHI5VcN-78MSYs0WDKYZS7W.json'
GET /login 200 102.486 ms - 2921
GET /stylesheets/ie10-viewport-bug-workaround.css 200 3.771 ms - 534
GET /stylesheets/signin.css 200 4.677 ms - 833
GET /stylesheets/sticky-footer.css 200 6.131 ms - 797
GET /stylesheets/bootstrap.min.css 200 5.203 ms - 121265
GET /stylesheets/toastr.min.css 200 8.207 ms - 5737
GET /javascripts/jquery.min.js 200 10.071 ms - 84384
GET /javascripts/login.js 200 2.296 ms - 3011
GET /javascripts/toastr.min.js 200 3.747 ms - 4323
GET /javascripts/ie10-viewport-bug-workaround.js 200 6.770 ms - 664
GET /javascripts/socket.io-1.4.5.js 200 7.948 ms - 97693
GET /fonts/glyphicons-halflings-regular.woff2 200 0.374 ms - 18028
GET /images/favicon.png 200 0.619 ms - 1492
GET / 302 1.353 ms - 56
Error: Can't set headers after they are sent.
at validateHeader (_http_outgoing.js:494:11)
at ServerResponse.setHeader (_http_outgoing.js:501:3)
at ServerResponse.header (G:\GitHub\steam-ts\node_modules\express\lib\response.js:767:10)
at ServerResponse.send (G:\GitHub\steam-ts\node_modules\express\lib\response.js:170:12)
at done (G:\GitHub\steam-ts\node_modules\express\lib\response.js:1004:10)
at View.exports.renderFile [as engine] (G:\GitHub\steam-ts\node_modules\ejs\lib\ejs.js:363:10)
at View.render (G:\GitHub\steam-ts\node_modules\express\lib\view.js:135:8)
at tryRender (G:\GitHub\steam-ts\node_modules\express\lib\application.js:640:10)
at Function.render (G:\GitHub\steam-ts\node_modules\express\lib\application.js:592:3)
at ServerResponse.render (G:\GitHub\steam-ts\node_modules\express\lib\response.js:1008:7)
GET /login 304 1.523 ms - -
GET /stylesheets/bootstrap.min.css 304 1.869 ms - -
GET /stylesheets/ie10-viewport-bug-workaround.css 304 2.626 ms - -
GET /stylesheets/signin.css 304 3.276 ms - -
GET /stylesheets/sticky-footer.css 304 6.127 ms - -
GET /stylesheets/toastr.min.css 304 8.349 ms - -
GET /javascripts/jquery.min.js 304 11.112 ms - -
GET /javascripts/ie10-viewport-bug-workaround.js 304 0.907 ms - -
GET /javascripts/socket.io-1.4.5.js 304 1.303 ms - -
GET /javascripts/toastr.min.js 304 2.092 ms - -
GET /javascripts/login.js 304 2.650 ms - -
GET / 302 1.076 ms - 56
GET /login 304 1.394 ms - -
Error: Can't set headers after they are sent.
at validateHeader (_http_outgoing.js:494:11)
at ServerResponse.setHeader (_http_outgoing.js:501:3)
at ServerResponse.header (G:\GitHub\steam-ts\node_modules\express\lib\response.js:767:10)
at ServerResponse.contentType (G:\GitHub\steam-ts\node_modules\express\lib\response.js:595:15)
at ServerResponse.send (G:\GitHub\steam-ts\node_modules\express\lib\response.js:145:14)
at done (G:\GitHub\steam-ts\node_modules\express\lib\response.js:1004:10)
at View.exports.renderFile [as engine] (G:\GitHub\steam-ts\node_modules\ejs\lib\ejs.js:363:10)
at View.render (G:\GitHub\steam-ts\node_modules\express\lib\view.js:135:8)
at tryRender (G:\GitHub\steam-ts\node_modules\express\lib\application.js:640:10)
at Function.render (G:\GitHub\steam-ts\node_modules\express\lib\application.js:592:3)
GET /stylesheets/bootstrap.min.css 304 1.551 ms - -
GET /stylesheets/ie10-viewport-bug-workaround.css 304 3.991 ms - -
GET /stylesheets/signin.css 304 5.553 ms - -
GET /stylesheets/sticky-footer.css 304 1.331 ms - -
GET /stylesheets/toastr.min.css 304 2.249 ms - -
GET /javascripts/jquery.min.js 304 2.948 ms - -
GET /javascripts/ie10-viewport-bug-workaround.js 304 3.797 ms - -
GET /javascripts/socket.io-1.4.5.js 304 4.177 ms - -
GET /javascripts/toastr.min.js 304 4.520 ms - -
GET /javascripts/login.js 304 3.077 ms - -
GET / 302 1.286 ms - 56
Successfully queried users and updated userdata.
GET /login 304 1.466 ms - -
GET /stylesheets/bootstrap.min.css 304 1.734 ms - -
GET /stylesheets/ie10-viewport-bug-workaround.css 304 5.226 ms - -
GET /stylesheets/signin.css 304 5.656 ms - -
GET /stylesheets/sticky-footer.css 304 6.413 ms - -
GET /stylesheets/toastr.min.css 304 7.882 ms - -
GET /javascripts/jquery.min.js 304 9.157 ms - -
GET /javascripts/ie10-viewport-bug-workaround.js 304 0.752 ms - -
GET /javascripts/socket.io-1.4.5.js 304 1.549 ms - -
GET /javascripts/toastr.min.js 304 3.393 ms - -
GET /javascripts/login.js 304 4.312 ms - -

Windows 10 1809 64 bits

Hello,

I'm getting this error message upon removing a user https://i.gyazo.com/885a564bff96f1c1d3b4ec06022e945e.png - The issue only appears when there are more than 1 people linked.

Kind Regards,
Jack Hansen

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart [email protected]
6 info start [email protected]
7 verbose unsafe-perm in lifecycle true
8 info [email protected] Failed to exec start script
9 verbose stack Error: [email protected] start: node lib/launch.js
9 verbose stack Exit status 1
9 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:217:16)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at EventEmitter.emit (events.js:172:7)
9 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at ChildProcess.emit (events.js:172:7)
9 verbose stack at maybeClose (internal/child_process.js:829:16)
9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
10 verbose pkgid [email protected]
11 verbose cwd Y:\Websites\login.dentixgaming.com
12 error Windows_NT 6.3.9600
13 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
14 error node v4.6.0
15 error npm v2.15.9
16 error code ELIFECYCLE
17 error [email protected] start: node lib/launch.js
17 error Exit status 1
18 error Failed at the [email protected] start script 'node lib/launch.js'.
18 error This is most likely a problem with the steam-ts package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error node lib/launch.js
18 error You can get information on how to open an issue for this project with:
18 error npm bugs steam-ts
18 error Or if that isn't available, you can get their info via:
18 error
18 error npm owner ls steam-ts
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]

Once i have the program launched and i go to localhost:8090 (changed the port) and i want to log in it reroutes me back to the login page.
I simply can't seem to log in....

would this be something to do with the Session file store that isn't found?

> [email protected] start F:\Steam TS\steam-ts-master
> node lib/launch.js

Trying to connect to the TeamSpeak server...
Logged into the query with credentials.
Using virtual server 16 now.
Changed query client name.
Succesfully launched the bot.
Admin panel available on port: 8090
GET / 302 15.848 ms - 56
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such f
ile or directory, open 'F:\Steam TS\steam-ts-master\webserver\sessions\ZDwVmOOHN
tZx3OPg50lmvLpqCMHHsPN9.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such f
ile or directory, open 'F:\Steam TS\steam-ts-master\webserver\sessions\ZDwVmOOHN
tZx3OPg50lmvLpqCMHHsPN9.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such f
ile or directory, open 'F:\Steam TS\steam-ts-master\webserver\sessions\ZDwVmOOHN
tZx3OPg50lmvLpqCMHHsPN9.json'
[session-file-store] will retry, error on last attempt: Error: ENOENT: no such f
ile or directory, open 'F:\Steam TS\steam-ts-master\webserver\sessions\ZDwVmOOHN
tZx3OPg50lmvLpqCMHHsPN9.json'
GET /login 200 241.413 ms - 2849
GET /stylesheets/ie10-viewport-bug-workaround.css 200 79.040 ms - 519
GET /stylesheets/signin.css 200 129.861 ms - 793
GET /stylesheets/sticky-footer.css 200 131.198 ms - 750
GET /stylesheets/toastr.min.css 200 162.860 ms - 5737
GET /stylesheets/bootstrap.min.css 200 166.511 ms - 121260
GET /images/favicon.png 200 118.240 ms - 1492
GET /javascripts/toastr.min.js 200 18.965 ms - 4321
GET /javascripts/ie10-viewport-bug-workaround.js 200 47.157 ms - 641
GET /javascripts/login.js 200 39.875 ms - 2895
GET /javascripts/socket.io-1.4.5.js 200 65.893 ms - 97690
GET /javascripts/jquery.min.js 200 159.355 ms - 84380
GET /fonts/glyphicons-halflings-regular.woff2 200 39.605 ms - 18028
GET / 302 3.336 ms - 56
GET /login 304 3.469 ms - -
GET /stylesheets/bootstrap.min.css 304 0.962 ms - -
GET /stylesheets/ie10-viewport-bug-workaround.css 304 4.606 ms - -
GET /stylesheets/signin.css 304 5.140 ms - -
GET /stylesheets/sticky-footer.css 304 2.465 ms - -
GET /stylesheets/toastr.min.css 304 6.520 ms - -
GET /javascripts/jquery.min.js 304 5.109 ms - -
GET /javascripts/ie10-viewport-bug-workaround.js 304 1.188 ms - -
GET /javascripts/socket.io-1.4.5.js 304 1.756 ms - -
GET /javascripts/toastr.min.js 304 4.326 ms - -
GET /javascripts/login.js 304 5.150 ms - -
GET /images/favicon.png 304 14.924 ms - -
Successfully queried users and updated userdata.
Successfully queried users and updated userdata.
Successfully queried users and updated userdata.

hello, i need help because it won't work.....

that's all folks.....

ts3 is located on the same machine, it's an ubuntu 18.04, node is v12.10.0, npm is 6.11.3, ts is 3.13.3....
config.json looks like
{
"main": {
"ts_ip": "212.227.###.###",
"q_port": 10011,
"q_username": "serveradmin",
"q_password": "#####",
"bot_username": "Senior_Bot",
"bot_password": "#####",
"q_vserverid": 1,
"minlevel": 1,
"wantedrankid": 9,
"editdescription": false,
"clanabbreviation": "",
"queryinterval": 30000,
"useHttps": false
},
"twofactor": {
"enabled": false
},
"webserver": {
"enabled": true,
"port": "8080",
"webminUsername": "whatever",
"webminPassword": "#####",
"timeOut": 300000
},
"doNotEdit": {
"sessionSecret": ""
}
}

i've installed the whole server multiple times and tried any possible config (web true/false, https true/false, twofactor true/false, other steam acc)..... everytime it looks like shown.......

can someone help me please?????

but - be patient, i'm not very experienced with linux.......

my installtion routine looks like:
sudo apt install nodejs -y
sudo apt install npm -y
apt install git -y
git clone https://github.com/nikitavondel/steam-ts.git
cd steam-ts/
pico config.json
--edit config

screen -S steam-ts3-integration
npm install
npm start
ctrl a d

Hi, how do I get it to connect to my server, we're on 164.132.70.25:9988 (Def is 9987)

Thanks.

I just wondered if will the bot auto remove people from Steam friends list after some amount of time

I keep getting this message in the steam chat at the last step of verification; "bot (1.3.3): Something went wrong, either retry !verify or contact an admin please!"

I can't seem to find a log from the Bot to see whats going wrong...

I have given it Server Admin Perms

Hi,

Love using this Node.js plugin

just a question how do I change the name of my bots steam name I change via steam but when I start it. it gets renamed

to be able to pick what channel the query client sits in on the ts3 server. also any way to relay a steam group chat?

This is not an issue but more of a request.
Is it possible to have this (damn amazing and awesome) script check for specific steam member groups to determine in which permission group the user is placed?

I only tested the script today, and it works like a charm (will do a how-to video to help support this!).
Im looking for methods on how to use this script, and one of them came to mind:
Let Steam memberships help determine what sort of rights a user is going to get on Teamspeak.

Would that be possible?

Hello, I am receiving an issue with logging into the admin panel, I have set up the user/password and when I go to enter them it nothing happens.

I've set up the bot, and it's running (I see activity in the console).
When I open up a chat with the bot and type any command (!verify) I see the command coming in on the bot (Received message from [U:1:1xxxxx]: !verify) but it doesn't send anything back...

Webpage is setup, but when I log in, no entries are there. What am I missing? :(

pm ERR! Linux 2.6.32-573.22.1.el6.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! node v0.10.46
npm ERR! npm v2.15.1
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: node lib/launch.js
npm ERR! Exit status 8
npm ERR!
npm ERR! Failed at the [email protected] start script 'node lib/launch.js'.
npm ERR! This is most likely a problem with the steam-ts package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node lib/launch.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs steam-ts
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls steam-ts
npm ERR! There is likely additional logging output above.

Just want to double check whether having the config file location within node_modules will causes the config to be re-written on an update. Unless I've missed something.

As my config-file seems to be empty after I ran npm install.

Might want to consider requiring these to be paled outside of node_modules?

join channel other than default

Hi,

New to using Linux was wondering how could I make the Steam Verify Bot start up with Linux

did try using #! bin/bash
cd /my bot location/
./$npm start

Any help is appreciated :)

So i was able to set up everything the Steam part is working fine and typing !verify also works but after i give the bot my name it says this in chat " Something went wrong, either retry !verify or contact an admin please!" and this in my console "{"id":2568,"msg":"insufficient client permissions","failed_permid":28}" it also says this every once in a while in the console "Error while querying users: [object Object]" and idea on how to fix it?

Hello, I have tried to open it in linux and in windows and in both i get the same error.
config.json is configured.
I have followed the npm installation as indicated.
I don't have much knowledge with npm but I think so far I did the steps indicated well.
This is a log from my windows vm with nodejs v16.17.0 installed.

App started.

[email protected] start
node lib/launch.js

node:internal/modules/cjs/loader:959
throw err;
^

Error: Cannot find module 'steam-user'
Require stack:

• C:\Users\rdr2server\Desktop\steam-ts-master\lib\launch.js
  at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
  at Function.Module._load (node:internal/modules/cjs/loader:804:27)
  at Module.require (node:internal/modules/cjs/loader:1028:19)
  at require (node:internal/modules/cjs/helpers:102:18)
  at Object. (C:\Users\rdr2server\Desktop\steam-ts-master\lib\launch.js:2:17)
  at Module._compile (node:internal/modules/cjs/loader:1126:14)
  at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
  at Module.load (node:internal/modules/cjs/loader:1004:32)
  at Function.Module._load (node:internal/modules/cjs/loader:839:12)
  at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 'C:\Users\rdr2server\Desktop\steam-ts-master\lib\launch.js' ]
  }

WARNING: App closed or crashed, restarting.

Nickname error

I've just updated my Teamspeak 3 to version 3.7.0
I can no longer get Steam-TS to start. Each time I get the following error:

{ id: 513, msg: 'nickname is already in use' }

I'm currently having to rename the bot in the launchteamspeak.js file each time, i.e: Steam-Bot1, Steam-Bot2.

This works, but only as long as the bot does not crash. As as soon as it does, and PM2 restarts it, it gets the above error that the bot's nickname is already in use.

Unfortunately, the Steam-TS bot crashes quite a lot, hence why I launch it via PM2. The cause of the crashing appears to be:

Random Crashes

Seeing the same error as above, even after the fix #9b3a358

Error: Callback was already called.
    at /home/ts3bot/steam-ts/node_modules/async/dist/async.js:837:34
    at Object.cb (/home/ts3bot/steam-ts/lib/queryusers.js:49:29)
    at LineInputStream.<anonymous> (/home/ts3bot/steam-ts/node_modules/node-teamspeak/index.js:170:35)
    at LineInputStream.emit (events.js:182:13)
    at LineInputStream.line (/home/ts3bot/steam-ts/node_modules/line-input-stream/lib/line-input-stream.js:8:8)
    at Array.forEach (<anonymous>)
    at Socket.<anonymous> (/home/ts3bot/steam-ts/node_modules/line-input-stream/lib/line-input-stream.js:36:9)
    at Socket.emit (events.js:182:13)
    at addChunk (_stream_readable.js:283:12)
    at readableAddChunk (_stream_readable.js:264:11)

PM2 lists this error 7 times, and also shows it's restarted the steam-ts bot 7 times, so concluding that this error is causing it to crash.

@nikitavondel
Hey, after firing the application after about one minute, the application automatically falls

• Trying to connect to the TeamSpeak server...
• Logged into the query with credentials.
• Using virtual server 1 now.
• Changed query client name.
• Succesfully launched the bot.
• Admin panel available on port: 8080
• Port 8080 is already in use
• npm ERR! code ELIFECYCLE
• npm ERR! errno 1
• npm ERR! [email protected] start: node lib/launch.js
• npm ERR! Exit status 1
• npm ERR!
• npm ERR! Failed at the [email protected] start script.
• npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm-debug.log.txt

Admits having this deployed a created its own query login.
I have another bot accessing the querry. Via its own query login also.
I have no idea if this is relational but steam bot crashes after a day or so.

`/home/ubuntu/steam-ts/node_modules/async/dist/async.js:837
if (fn === null) throw new Error("Callback was already called.");
^

Error: Callback was already called.
at /home/ubuntu/steam-ts/node_modules/async/dist/async.js:837:34
at Object.cb (/home/ubuntu/steam-ts/lib/queryusers.js:43:29)
at LineInputStream. (/home/ubuntu/steam-ts/node_modules/node-teamspeak/index.js:170:35)
at emitOne (events.js:96:13)
at LineInputStream.emit (events.js:188:7)
at LineInputStream.line (/home/ubuntu/steam-ts/node_modules/node-teamspeak/node_modules/line-input-stream/lib/line-input-stream.js:8:8)
at Array.forEach (native)
at Socket. (/home/ubuntu/steam-ts/node_modules/node-teamspeak/node_modules/line-input-stream/lib/line-input-stream.js:36:9)
at emitOne (events.js:96:13)
at Socket.emit (events.js:188:7)

npm ERR! Linux 3.13.0-92-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v6.10.2
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: node lib/launch.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'node lib/launch.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the steam-ts package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node lib/launch.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs steam-ts
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls steam-ts
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! /home/ubuntu/steam-ts/npm-debug.log`

Hey,
would it be possible to add these two features to the bot:

1. Send a message to the steam user if the friend request was accepted
2. Set different groups based on Ownership of different games, e.g. if the User owns ARK: Survival Evolved he would be added to the normal verify group and additionaly to an ARK group on TS (detecting of Game maybe via Steam AppID?)

Aware of this bug, I am currently a bit busy so it might take a few weeks to fix.

Failure on connection with InvalidPassword error:

[ts3bot@vps ~]$ node index.js
Trying to connect to the TeamSpeak server...
Logged into the query with credentials.
Using virtual server 1 now.
Changed query client name.
{ [Error: InvalidPassword] eresult: 5 }
[ts3bot@vps ~]$

However as can be seen here Telnet into TS3 server with ServerQuery username and password works fine:

Any ideas on what is causing this?

PS: I'm an idiot, did not realize this required me to actually login to a valid steam-account. Kinda use to anonymous login. And initially thought the bot login and password, were custom commands to be used directly in TeamSpeak3.

Please close!

Since this week Steam-TS gets an error on start.

SyntaxError: Unexpected end of JSON input at JSON.parse (<anonymous>) at D:\Scripts\Steam TS\Steam TS\steam-ts-master\lib\launch.js:63:29 at D:\Scripts\Steam TS\Steam TS\steam-ts-master\node_modules\async\dist\async.js:3575:11 at replenish (D:\Scripts\Steam TS\Steam TS\steam-ts-master\node_modules\async\dist\async.js:872:19) at D:\Scripts\Steam TS\Steam TS\steam-ts-master\node_modules\async\dist\async.js:878:27 at D:\Scripts\Steam TS\Steam TS\steam-ts-master\node_modules\async\dist\async.js:840:18 at D:\Scripts\Steam TS\Steam TS\steam-ts-master\node_modules\async\dist\async.js:3580:15 at D:\Scripts\Steam TS\Steam TS\steam-ts-master\node_modules\async\dist\async.js:339:29 at D:\Scripts\Steam TS\Steam TS\steam-ts-master\lib\launch.js:42:9 at D:\Scripts\Steam TS\Steam TS\steam-ts-master\node_modules\async\dist\async.js:3575:11 npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start: node lib/launch.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Striker\AppData\Roaming\npm-cache_logs\2019-01-22T07_51_30_707Z-debug.log`

Ive recently moved the script from a physical Server 2012 R2 installation to a virtual one on Server 2016, it has run fine for multiple weeks.
Ive also tried restarting the installation on the 2012 R2 machine (migration isn't complete yet :) ) - and i get the exact same error there.
It seems that something has changed with Steam that causes this issue, but I can't see what for the life of me.

Any help is appreciated.
I tried updating it with the latest fixes, still the same error.