-
Notifications
You must be signed in to change notification settings - Fork 65
About TeamTalkSDK #89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
As I remember we could run TTMediaBot on latest TeamTalk 5.12 and it worked normally. |
Hello. I have several modifications in the TeamTalkSDK and I would like to send them to TTMediaBot. Added the missing _DoMoveUser function and may add some others in the future. But for that, TeamTalkSDK would need to be distributed with TTMediaBot. It's a suggestion, but if you accept it I can send my changes to the SDK that you add to the BOT, since what is being used here is 5.8 and that's what looks best in my opinion. |
i believe this is a good function, and i woould be very hapy if it goes to official ttmediabot. i see in several teamtalks persons loadin 10 or 20 ttbots, and requesting to admins to move it, or create one for their channels. if this functionalty goes, the user can find for example in root channel all available bot, request one to his channel, and after using, bot returns to the root channel, not keeping to waste resources unecessary in the server or playing audio for noone. |
20 TTMediaBot's? if the bot didn't have memory leaks, it would be possible, but when you using the youtube service, memory leaks, and can go to 600 mb per bot |
it is possible if you have a server that can handle |
I was looking at the new versions of TeamTalkSDK, and the library was all refactored in version 8.12. The problem that I couldn't run it on TTMediaBOT, because of the acertion errors.
I would like to hear from the developers, if they intend to switch to this SDK or if they will continue on TeamTalkSDK 5.8.
I suggest that if they are going to continue in TeamTalk 5.8, that TTMediaBOT distributes its own TeamTalkSDK, as it has no way of implementing the missing functions of the library, such as _DoMoveUser, as they will be refused by BearWare, since they are too old.
The text was updated successfully, but these errors were encountered: