Feature Request | Client Online

[DrWarpMan]

I'm doing by UID so I get the Client if he is on or offline. But removing/adding only works if he is online

So, you can not use ID, because you have only UID, right?

 

[Kamikaze]

So, you can not use ID, right?

Using UID cuz thats what you have to write into the script config. > https://i.imgur.com/itjHWyk.png

 

[DrWarpMan]

Using UID cuz thats what you have to write into the script config. > https://i.imgur.com/itjHWyk.png

Yeah, then you can use my method I guess.

 

[Kamikaze]

For adding we have a function called addClientByDatabaseId(client) on the server group object.
See ref. https://sinusbot.github.io/scripting-docs/#servergroup

I'll try to summon flyth to check if remove is just not in the documentation....

Yea but ppl have to write it into the script config. and I think databaseId is only visible with extended Teamspeak Design. UID is easier to get and unique too

 

[TwentyFour]

Using @DrWarpMan's method as well. Works like a charm.

I just check if the servergroup is present. When the client is offline, the return is different, to when its not existing. So you basically don't really need a true online check at all imho.

 

[Tuetchen]

well the user has to be online at some time anyway - so you can then store the db id for every UID in your config as it will never change

 

[Kamikaze]

Using @DrWarpMan's method as well. Works like a charm.

I just check if the servergroup is present. When the client is offline, the return is different, to when its not existing. So you basically don't really need a true online check at all imho.

Yea would also work Will test both of it

 

[DrWarpMan]

well the user has to be online at some time anyway - so you can then store the db id for every UID in your config as it will never change

I do not think that it is needed to have thousands of keys instead of having few, that are removed later.

 

[Kamikaze]

So thanks to all, will try all those options

But still hoping you can add something to check if user is online like i mentioned before "client.isOnline()" to make some things easier

 

[Tuetchen]

I do not think that it is needed to have thousands of keys instead of having few, that are removed later.

Well you can still just get the client by backend.getClientByUID() and then retrieve the db id there - should work even for offline clients