Forum

Search:

Type: Posts; User: FugiTive Legacy; Keyword(s):

Search: Search took 0.01 seconds.

  1. Yes, it appears that's whats happening. I've made...

    Yes, it appears that's whats happening. I've made some more updates to my own Fork of Steam-TS, which avoids the use of 'randomising' the bot's nickname on each connect.
  2. Ok, well this may be more down to the specific...

    Ok, well this may be more down to the specific Teamspeak 3 NodeJS Library which has been implemented in this bot. So will post an issue on their GitHub page, for their dev to look into.

    Not sure...
  3. Temporary Solution

    For now I've solved this by the following "hack-code" by changing the connection code.


    function (teamspeakClient, callback) {
    console.log("Using virtual server " +...
  4. Server Query Client Nickname is already in use error

    Hi, I've just updated my Teamspeak 3 server to version 3.7.0

    I've noticed what I think may be a bug, in this latest version.

    For context I've been using the following Teamspeak 3 NodeJS Bot -...
  5. Yes, this sounds like a solution. If for...

    Yes, this sounds like a solution.

    If for instance in the badnickname.cfg there could be for instance two groups/lists.
    • The First group - Kick if recognised of badnicknames would have the list...
  6. This bot is fantastic it was very easy to setup...

    This bot is fantastic it was very easy to setup and I've found it very reliable. Whilst it sounds like you don't have much time to work on updating and improving on this bot I was hoping if I could...
Results 1 to 6 of 6