I wondered about the fact the server is counting the time in seconds instead of showing me a timestamp the last user left the channel. So I checked the database for a field ‘seconds empty’ or similiar but I couldn´t find one. Last conclusion for me: Only the Teamspeak service is counting the time. I restarted the server and voilá… for every channel the server started counting again from 0.
And I think the only use case for this feature is to track the time for temporary channels, right? My problem is, that there are a bunch of channels that are no longer visited on our teamspeak server and we would like to let them automatically deleted after some time of no visitors, but if we set them all as temporary the channels are gonna all deleted on a restart of the teamspeak service. So this is no option for us.
At the moment a sinusbot is doing this job for us, but is there a chance that you will implement a feature that saves a timestamp which is recorded after the last user leaves a channel? Or did I missed something?
No, not in my mind, because the application could cache it like it is already doing. We would only need a database request for starting and closing the server, so that temporary channels would still exist on restarting a server. Usually I do restarts after teamspeak server updates or the root server requires a restart. That´s not so often, but would, like you already said, makes my calculations useless.
Yes, you are right and I´m doing it right now like you said. Is the teamspeak application really incrementing some kind of integers for the calculation of ‘seconds empty’? I think the application is saving a timestamp, too, and calculates the seconds based on this timestamp to return the ‘seconds empty’ on every api call. Why not return a timestamp straight through? <-- This is only a suggestion and I do not even had a problem with this.
That´s a good solution. At the moment a wordpress plugin connects every hour to the teamspeak server query. On this call I could download the whole channel list with it´s ‘seconds empty’ value and compare them to the existing values like you said. Thanks a lot.
I´m totally with you, but it could also be used for much more things if it´s save the calculated values at some time in the database. Even if the application would save it on restart only. That would be much appreciated and maybe even the great mass will see the advantages of this feature.