Search results

this isn't command based, but rather channel based https://forum.sinusbot.com/resources/channel-servergroup-assigner.93/

That should be self explanatory for you to be able to fix

That won't work, he's running it on linux, that method is for the windows version ./sinusbot --pwreset=newpassword This should work, but since you're saying it doesn't, I suggest clearing everything and reinstalling the bot.

Radio streams play constantly, using !qyt makes no sense as it will only play after the radio station ends which that won't happen. That is why you must use !yt. Or to be more complicated, use !qyt, then !next.

Yup. Windows marked my home network as public oddly, so firewall blocked others from accessing it.

I'm not supposed to jealous of the windows version, but I am. :eek: What I love Ability to configure scripts without having to enable, configure, save, disable them. Ability to download and install scripts without having to restart the bot (<--best feature) Launching the interface from a...

Wow lot's of insiders. i'm a linux person, but I wouldn't mind testing out the windows version.

The latest beta version of sinusbot (0.9.12.3-5b7c0cd) generates a random password for the admin account on its initial startup. This only applies to the first time setup. It outputs in the console the credentials, so if you missed that and have no way of going back, then I suggest to start...

You should try the latest beta version with the latest teamspeak client, so far the bot has responded every time.

As a quick fix for this issue, you could create a crontab to have the bots auto restart every 6 hours (since that's where it seems to stop responding). **This only works for those who have sinusbot running as a server** Login as root/sudo and enter paste these commands. crontab -e 0 0,6,12,18 *...

Same issue happens for me, the bot stops responding to commands after around 6-7 hours. Nothing shows in the logs, but I don't have to restart the entire sinusbot. I just have to restart a single instance (pressing the power on/off button in the web panel). So maybe it's a teamspeak client...

Latest version of sinusbot solves the RAM issue

You have to set the server that the bot will connect too by changing the options in the panel. Connect by going to http://<ip>:8087 and login with username: admin, password: foobar. Then go to instance settings and change those settings.

Permabanning on the first connect is pretty harsh. It should go like this: 1st connect on proxy: kick with reason 2nd connect on proxy: 1 min ban with reason 3rd connect on proxy: Permaban Then the script can have an option to set ignored client ids or ignored teamspeak group ids, so trusted...

I hate bumping old threads, but another request is to enable Xenforo's Image/Link proxy, so everything proxies through the site for full SSL. This thread for example has 2 images both of which are non https, so there isn't a full green SSL on the url bar. Mixed content basically.