Teamspeak 3 Spam Bot For Discord
Adocilesloth submitted a new resource: Formerly known as TS3 Recording Notifier A community I play in requires users to have *R* in front of their name in Teamspeak if they are recording or streaming. I made this plugin to add the prefix when streaming then remove it when not streaming. As of 2013-12-20, the plugin has been updated to allow users to mute and/or deafen themselves as well as switch channels while streaming/recording. They will be unmuted/undeafened and moved back to the original channel when recording/streaming stops.
I replaced skype with discord because of spam friend requests, performance and security issues in skype. If discord is mainly used for voice in a bigger community I prefer teamspeak as you can't manage the channels in discord like you can in teamspeak. Make sure the windows service 'TeamSpeak 3 Bot' is running, if you choosed the Setup variant. Open the Configuration in the 'Configuration' folder, which is in the Installation folder (default is 'C: Program Files Dirk Sarodnick TeamSpeak 3 Bot Configuration ') Copy one of the example Configurations.
As of 2014-08-20, it also adds a TS3 overlay that can be added as a source for OBS. This overlay was created from a modified version of the Text source.
Marks head bobbers and hand jobbers jessica. It wasn't long before he was standing in front of her while she jerked his cock off hard and fast with two hands. ( Jessica Rayne). Now that's a bad roommate. She was just to sexy for him to hold back and he unloaded a massive wad of jizz on her cute little face.
Downloads: Zip file contains TS3Plugin.dll and README.txt files Before streaming, open the TeamSpeak 3 Plugin config. First box allows you to set the IP of the PC running your TS3 client if you record and play on different computers. In the second box add your TS3 Unique ID (Settings -> Identities -> Unique ID) The next two checkboxes pick whether to use a prefix or suffix. The third sets whether the pre/suffix is added to all servers or the active server. Change *R* in the third box to what ever you want the prefix to be (must be 10 characters or less) The next two checkboxes are self explanatory. The third sets whether the mute/deafen is added to all servers or the active server. If the 'Change Channel' checkbox is ticked, the 'Set Channel' button and 'Channel Password' boxes are activated.
Move to the streaming/recording channel and press 'Set Channel' to set that channel in OBS. Then add the channel password if necessary. Only works in the active server.
The overlay config. The prefix is set to 10 as the max character limit for a name in TS is 30. The plugin has to remove characters at the end of the name to add the preifx so long prefixes start to shorten the name. I have added the ability to mute/deafen yourself and change channel while streaming. I was looking at disconnecting from TS while streaming but there isn't a nice way to do it; you have to kick yourself and you can't reconnect from within the plugin. If people want it, I can add it but at the moment it seems a bit pointless due to the no reconnect option. NOTE: If you used the old version of this plugin, please search for%appdata%/OBS/pluginData and delete ts3.ini or OBS will crash when you open the TS3 Recording Notifier config.
Click on plugins. In the list that appears, select TS3 Recording Notifier. Then click on Configure If TS3 Recording Notifier isn't in the list of plugins, make sure you have the correct version of the plugin for your version of OBS.
As a note, the shortcut that gets placed on your desktop when you install OBS directs you to the 32bit version of OBS. If you installed the 64bit version of the plugin into the 64bit OBS directory and you can't find the plugin when you launch OBS from the shortcut, that may be the problem. A friend was having this problem yesterday and knowing that fixed it for him. El peligro de la verdad pdf pdf. The cause of that crash is proving to be slightly illusive. I know that it's due to the overlay.
As for the text file not changing, it was kind of by design. When you start streaming, the plugin checks for a teamspeak client. If it can't find one, it doesn't run the thread that handles the overlay. I assumed that people would have teamspeak up and running before streaming which, looking at it now, was a bad assumption to make. I'll work on finding a fix for the crash and then the text file thing but it may be a while.