![]() ![]() 2 instances of it actually but from what can tell from using it the last year or so it uses one install for both instances\clients but has files for two clients to cover instances so is technically 2 client installs. Thats how it works it uses a teamspeak 3 client as a bot to broadcast music on your Teamspeak server. The GUI itself works fine but without a teamspeak 3 client installed for Sinusbot to use to play music no way to know if thats working. qpkg and so on)- There is no Teamspeak 3 client installed at all for Sinusbot to use for its instances. From what I can tell (is possible I missed it if so let me know, I looked in the usual places tho- /opt, etc. Sinusbot installs and uses the client itself on a normal install (the 2 instances you can setup in the sinusbot gui) to connect to the teamspeak 3 server which is completely separate and should have no reference to your server at all. In the config.ini the TS3= line is supposed to be for a teamspeak client not the server. Stephane a couple things I noticed with this install which are likely the cause of it not working properly with the instances - 1. You also don't need to re-upload files again, as files and users will be shared between the bot instances. ![]() No need to start another instance, it can all be controlled from within the web-interface. A Bot for Everyone! Having a whole Clan, Guild or Alliance with different tastes of Music? Just create another bot and let it play for another audience. Even your friends can have their own folders. In the future the bot will also get a folder-like structure for even more organization. You can re-arrange the order by dragging
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |