Teamspeak 3 Sync

[ImportBot]

Originally Posted by Imisnew2*:

 

About

---

Author: Imisnew2

 

Teamspeak 3 Sync synchronizes your Bad Company 2 / Battlefield 3 server with a Teamspeak 3 server, moving players into their respective channels on Teamspeak 3 dependent on the player's team in Bad Company 2 / Battlefield 3. The plugin also allows you to "Message" players who are not in your Teamspeak 3 Server, yet playing on your Bad Company 2 / Battlefield 3 server.

 

All parameters for the plugin are described in the plugins details tab.

 

Current Issues:

[-] Under rare circumstances, Teamspeak 3 Sync will not re-enable itself after a layer restart.

[-] When two players whose names are extremely similar and are playing from the same IP will not be sync'd up correctly.

 

Future Plans:

[-] Add the ability to display the amount of users currently on Teamspeak into the yell feature.

[-] (Considering) Move players to Team channel (assumes squad swapping is active) while they are dead.

[-] (Considering) Move players to Penalty channel upon TKing in the game.

 

 

Setup Instructions

---

PRoCon Setup:

Teamspeak 3 Sync doesn't need any special setup out-of-the-box unless PRoCon is running in a sandbox. You can check whether PRoCon is running in a sandbox and add exceptions for Teamspeak 3 Sync by following the steps outlined below:

[-] Start PRoCon, go to Tools > Options.

[-] Under the Plugins tab, check if the drop-down is set to "Run plugins in a sandbox (recommended)."

[-] If it is, add your Teamspeak 3 Server's IP and Query Port to the Trusted Domains.

 

Teamspeak Setup:

While the Teamspeak Server doesn't require any special setup, the plugin may be banned occasionally due to sending commands too quickly. This and other setup instructions are listed below to get the information necessary for the plugin:

[-] Add your PRoCon's IP to query_ip_whitelist.txt. This is found in the root folder of your Teamspeak 3 Server. If your Teamspeak 3 Server is being hosted by a server provider, ask your provider to do this for you.

[-] Setup your ServerQuery Login through Teamspeak by going to Tools -> ServerQuery Login -> *Enter A Username* -> *Receive Auto Generated Password*. The following permissions are required for the plugin to run correctly:

Permissions:

 

 

[-] login

[-] use

[-] channellist

[-] channelfind

[-] channelinfo

[-] clientlist

[-] clientfind

[-] clientinfo

[-] clientmove

[-] clientupdate

 

 

 

 

[-]To find what port your Teamspeak 3 Server uses as its query port, look in the server.ini file. The default value is 10011. If your Teamspeak 3 Server is being hosted by a server provider, ask your provider for the query port.

 

 

Releases

---

Teamspeak Sync 1.0.3.1

Older:

 

 

[-] Teamspeak Sync 1.0.3

[-] Teamspeak Sync 1.0.2.2

[-] Teamspeak Sync 1.0.1

[-] Teamspeak Sync 1.0.0.0

[-] Teamspeak Sync 0.9.7*

[-] Teamspeak Sync 0.9.6*

[-] Teamspeak Sync 0.9.5.5*

[-] Teamspeak Sync 0.9.5*

[-] Teamspeak Sync 0.9.3*

[-] Teamspeak Sync 0.9.2*

[-] Teamspeak Sync 0.9.1*

[-] Teamspeak Sync 0.9.0*

[-] Teamspeak Sync 0.8.0*

[-] Teamspeak Sync 0.7.0*

[-] Teamspeak Sync 0.6.0*

[-] Teamspeak Sync 0.5.1*

[-] Teamspeak Sync 0.5.0*

 

 

 

 

 

 

Change Log

---

1.0.3 -> 1.0.3.1

[-] Fixed an issue where a response that included a value with an "=" sign in it would erroneously chop off the value at the "=" sign.

Older:

 

 

1.0.2.2 -> 1.0.3

[-] Fixed an issue where a player may get swapped between channels repeatedly.

1.0.1 -> 1.0.2.2

[-] Updated plugin API to use recommended PRoCon API.

[-] Added ability for other plugins to interact with and get data from Teamspeak 3 Sync.

[-] Added check to cause less erroneous swapping when two clients from the same IP join a server.

1.0.0.0 -> 1.0.1

[-] Fix intermission swapping for BFBC2.

0.9.7 -> 1.0.0.0

[-] Do not swap players from pickup channels to staging channels.

0.9.6 -> 0.9.7

[-] Fixed an issue when disabling/re-enabling the plugin related to other pool channels.

[-] Plugin can now be disabled if it is attempting to reconnect.

[-] Plugin now attempts to reconnect upon initial connection failure.

0.9.5.5 -> 0.9.6

[-] Fixed some issues concerning new Teamspeak 3 server releases.

[-] Added some logic to attempt to fix a swapping issue.

[-] Added the ability to allow Teamspeak 3 Sync to pull clients from channels other than the Staging channel into the Plugin's Team and Squad channels.

[-] Added the ability to leave a player in the team channel (versus a squad channel) if there is less than a specified amount of players in the player's squad that are also on Teamspeak.

[-] Added the ability to move players to the staging channels between rounds for inter-team chat.

0.9.5 -> 0.9.5.5

[-] Fixed an issue where, after a re-connection due to an error has successfully occurred, Procon may crash.

0.9.4 -> 0.9.5

[-] Added the ability to delay queries being sent to the Teamspeak 3 server.

[-] Broke up and renamed several settings - This will probably cause you to have to re-do your settings, sorry.

[-] Removed channel creation upon plugin start.

[-] Made channel removal more robust, removing all empty channels when checked.

[-] Fixed a bug where sometimes PRoCon would still require a start after the plugin was disabled from an error.

[-] Fixed a bug where sometimes the plugin would not disable itself after a fatal error.

[-] Fixed a bug where enabling/disabling the plugin during an error might cause unwanted behavior.

[-] Major code overhaul - It just looks prettier now .

0.9.3 -> 0.9.4

[-] Added the ability to have Team Channels exist under the root channel.

[-] Added the ability to specify the Server Query Nickname.

[-] Added the ability to control the password attached to channels the plugin creates (or none at all).

[-] Broke up debugging information into 5 categories.

[-] Revamped event processing system - No longer requires PRoCon to be restarted if plugin is disabled.

[-] Revamped error processing system - Provides error messages upon being banned from the server, among other things.

[-] Revamped re-connection system - Now it actually works (will not be able to disable plugin while it is attempting to reconnect).

[-] Changed the squad threshold to be per-team, so players are only broken up into squad channels if there are enough players for that team.

[-] Fixed a bug where removing channels would cause the plugin to crash.

[-] Removed Matching Threshold due to issues - Names must have a 100% match to be matched on name.

[-] Removed moving players to the staging channel if their team was Team 0 - it simply ignores Team 0 now.

0.9.2 -> 0.9.3

[-] Fixed an issue where (for Battlefield 3) a 'Team 0' channel would be created.

[-] Fixed an issue where no matter which channel a client was in, they would be moved.

[-] Fixed an issue where Teamspeak Sync would throw an error when attempting to remove channels.

0.9.1 -> 0.9.2

[-] Fixed an issue where Procon would crash when attempting to remove squad channels.

[-] Fixed an issue where Procon would crash when attempting to create channels.

[-] Renamed "Serveradmin from ip xxx.xxx.xxx.xxx" to "Odin".

0.9 -> 0.9.1

[-] Fixed an issue with items on the action queue trying to be removed when there were none.

0.8 -> 0.9

[-] Channels are dynamically created/found aside from the staging channel.

[-] Supports all game-modes/types.

[-] Supports removing channels when the last player has left them.

[-] Supports single channel, team channels, and squad channels based on set thresholds.

[-] Added robust debug logging (on demand).

[-] Beefed up connection error handling more.

[-] Even better insta swapping.

[-] Fixed the infamous super-random "Reference to null object" error_!

[-] Fixed a issue where custom query server connection messages could cause the initial connection to fail.

[-] Fixed the triple swap issue occurring in 0.8.

0.7 -> 0.8

[-] Fixed a huge CPU usage issue in 0.7. This may have been the cause of the "infinite crash loop", especially if your PRoCon host forced PRoCon to a single core.

[-] Possible fix to the "Reference to null object" error.

[-] Fixed Reconnect on error... I think...

[-] The Plugin does slightly more logging in the console (didn't do any at all before, after setup, really) to help troubleshoot errors. Non-fatal errors are logged in orange. For the most part, you can ignore these.

[-] Re-implemented super-fast swapping and insta-swaps on join/team-swap/leave.

[-] Fixed a server query permissions issue. Might cause other errors, I just need people to keep me posted, so I can implement a hot-fix if this solution doesn't work.

[-] Other minor tweaks to prepare for 0.9 release.

0.6 -> 0.7

[-] Completely re-coded and thoroughly tested the Teamspeak API. Hopefully this fixes some errors that have been rising up lately (See: NEXSO's posts around pages 7-9). (For the record, I made the TS API completely asynchronous, go me!)

[-] Completely re-coded the way updates are requested from the Bad Company 2 server. This cuts down nearly all extra traffic between the Bad Company 2 server that the plugin initially created.

[-] Completely re-coded the matching scheme between clients to account for multiple IP's and no IP's. Also, implemented the levinshtein distance algorithm for a fall-back with matching on names.

[-] Fixed various issues where player's would not match up correctly, leaving them in the staging channel.

[-] Allowed Reconnect On Error Settings, Synchronization, and Yell Settings to be modified on the fly. Any changes you make to these variables will have an instantaneous effect. Changes to the Teamspeak 3 Server variables still require the plugin to be disabled/enabled to take affect.

[-] To reduce complications, I've made the plugin solely based on the "Update Interval". This means players who swap teams will not be swapped in teamspeak until the next interval rolls around. I plan on re-implementing swapping players right when they swap teams in one of several "smaller releases" planned for v0.7.

[-] I can't remember what else I changed, but this version is basically a ground-up remake of the original plugin, as to try and eliminate as many errors as possible.

0.5.1 -> 0.6

[-] You no longer have to specify your Virtual Server ID. Instead, you must specify your Teamspeak 3 Port.

[-] Fixed several little bugs that would cause the plugin to freeze on rare occasions.

[-] Made the plugin more "crash proof".

[-] Went mad with threading, allowing a more "fluid" looking response from PRoCon at all times. I.e., it doesn't look like it freezes anymore when trying to crunch a lot of information.

[-] Made IP matching more robust, so that if a players IP could not be obtained (e.g. EA's servers are down), it defaults back to matching based on Name.

[-] Re-implemented swapping players as soon as they swap teams (slightly longer delay than v0.4).

[-] Fixed an issue where the plugin would not start correctly if already enabled when PRoCon was started. (More of a work-around. May still fail in some rare cases.)

[-] Allows for "custom responses" from query servers upon connection. This means everyone who was having problems with the plugin and using a Teamspeak 3 server from Gameservers (or another provider) will now be able to use the plugin. - Thanks for the help powerbits.

0.5 -> 0.5.1

[-] Applied hot-fix to correct crashing issue if a player disconnected from teamspeak at just the right time.

0.4 -> 0.5

[-] Fixed some threading issues that caused crashes in extremely rare occasions.

[-] Made error messages more... helpful.

[-] Matching based off of IP, not name.

[-] For this release, the actual time it takes for the plugin to realize you joined the server/swapped teams is dependent on the update interval. It will return to being instantaneous in the next release.

 

[ImportBot]

Originally Posted by Phogue*:

 

Epic.

 

Again I'm *really* sorry I accidentally deleted this =\

[ImportBot]

Originally Posted by micovery*:

 

I just tried it, and it works. Very cool!

 

It took me some tinkering before it would actually say it was syncing. There is not any useful feedback when it does not work, all it says is:

 

01:05:22 01] Could not connect to the teamspeak 3 server.

[01:05:22 01] Please fix your settings and then re-enable the plugin to restart.

 

 

Would be good if you could say why it's not working. Like invalid ip/port, username/password, or cannot find channel ... etc.

 

Also a bug I found, was that if the channel has a backslash in the name "\", it would not work.

[ImportBot]

Originally Posted by CoreSyntax*:

 

I just tried it, and it works. Very cool!

 

It took me some tinkering before it would actually say it was syncing. There is not any useful feedback when it does not work, all it says is:

How did you get yours working?

[ImportBot]

Originally Posted by Imisnew2*:

 

The error messages are a little cryptic, but I don't have the time right now to post up a "translation". Give me 5-6 hrs from this post, and they should be up.

 

The first one, however, that you posted mico, has to deal with the connection to the TS3 server. It means either the IP/Port was wrong, the TS3 server was down, the IP/Port wasn't to the Query server of the TS3 server... etc, many things.

 

Failed Login would be a different message.

Failed virtual server ID would be a different message.

Failed Finding of channels would be a different message, and so on.

 

This is the first public release, so expect some programmerpublic miscommunication issues .

 

And now I'm out of time.

[ImportBot]

Originally Posted by Imisnew2*:

 

Error messages are posted. And CoreSyntax, if you could let me know what errors you're receiving, I might be able to help.

[ImportBot]

Originally Posted by Imisnew2*:

 

Also a bug I found, was that if the channel has a backslash in the name "\", it would not work.

I could not reproduce this.

I created a channel "TestChannel/TestChannel" and "TestChannel\TestChannel"; both worked.

[ImportBot]

Originally Posted by captinwizard*:

 

This is very cool.... Can this be used for Ventrilo or maybe someone could develop plugin like this for Ventrilo?

[ImportBot]

Originally Posted by Imisnew2*:

 

This is very cool.... Can this be used for Ventrilo or maybe someone could develop plugin like this for Ventrilo?

It might be possible, however, I would have to check out Ventrillo to see if there is any API for it. Otherwise, it wouldn't be fun to write that plugin, lol.

[ImportBot]

Originally Posted by blactionhero*:

 

Wow, very nice work! Your code looks great too - heavily commented.

[ImportBot]

Originally Posted by micovery*:

 

I just tried it, and it works. Very cool!

 

It took me some tinkering before it would actually say it was syncing. There is not any useful feedback when it does not work, all it says is:

How did you get yours working?

This is how I tested it. Setting up TS3 Sync Plugin for ProCon (5 mins)

[ImportBot]

Originally Posted by firefighter19*:

 

Hey guys i get this error

 

Code:

[13:45:47 97] Could not select the virtual server specified.

My server is hosted through Gameservers any idea where i found out what my Virtual Id is?

 

Regards Ash

[ImportBot]

Originally Posted by Imisnew2*:

 

Hey guys i get this error

 

Code:

[13:45:47 97] Could not select the virtual server specified.

My server is hosted through Gameservers any idea where i found out what my Virtual Id is?

 

Regards Ash

If you don't have direct access to the server, then you'll have you ask whoever is providing the service for you (Gameservers) to give you the virtual ID.

 

However.... There can only be ID's 1-10. So, I suppose you might be able to figure it out eventually .

[ImportBot]

Originally Posted by CaptainSilver*:

 

We are a fun-clan and at the most time all players mess around in the same Ts-channel. It would be nice, if this plugin has a "simple" mode:

 

the players can connect to TS by an in-game command (@teamspeak) - no automatic action.

[ImportBot]

Originally Posted by Imisnew2*:

 

We are a fun-clan and at the most time all players mess around in the same Ts-channel. It would be nice, if this plugin has a "simple" mode:

 

the players can connect to TS by an in-game command (@teamspeak) - no automatic action.

I'm not sure I understand you, can you elaborate?

[ImportBot]

Originally Posted by micovery*:

 

For VirtualIDs ... deoes each virtual server have to have a separate port? If that's the case, you should be able to just probe internally 1 through 10 until finding the virtual server ... instead of asking the user for it.

[ImportBot]

Originally Posted by CaptainSilver*:

 

We are a fun-clan and at the most time all players mess around in the same Ts-channel. It would be nice, if this plugin has a "simple" mode:

 

the players can connect to TS by an in-game command (@teamspeak) - no automatic action.

I'm not sure I understand you, can you elaborate?

In TS we just use one channel. All players whatever team or squad are in the channel (We are just a fun-clan).

It would be nice, if a player wants to join this channel just writes "@teamspeak" in the ingame chat. Then the plugin connects him with our teamspeak.

[ImportBot]

Originally Posted by blactionhero*:

 

It would be nice, if a player wants to join this channel just writes "@teamspeak" in the ingame chat. Then the plugin connects him with our teamspeak.

For that to work, every player would have to download and install Procon, then download and install this addon, then have both working and running before joining your server. X; That is unless I'm missing something.

[ImportBot]

Originally Posted by CoreSyntax*:

 

...And CoreSyntax, if you could let me know what errors you're receiving, I might be able to help.

Sorry, my bad.

I did not setup tool/server query login.

[ImportBot]

Originally Posted by Imisnew2*:

 

We are a fun-clan and at the most time all players mess around in the same Ts-channel. It would be nice, if this plugin has a "simple" mode:

 

the players can connect to TS by an in-game command (@teamspeak) - no automatic action.

I'm not sure I understand you, can you elaborate?

In TS we just use one channel. All players whatever team or squad are in the channel (We are just a fun-clan).

It would be nice, if a player wants to join this channel just writes "@teamspeak" in the ingame chat. Then the plugin connects him with our teamspeak.

I don't think that's possible, because that would require the person who writes "@teamspeak" to have teamspeak installed. Also, I can't control what programs on a player's computer does.

 

So, sorry.

[ImportBot]

Originally Posted by Imisnew2*:

 

For VirtualIDs ... deoes each virtual server have to have a separate port? If that's the case, you should be able to just probe internally 1 through 10 until finding the virtual server ... instead of asking the user for it.

Can't do that, because several virtual servers may exist.

I.e. - A single website may host several BC2 servers, and just create different TS virtual servers for all of them.

 

Note: While each Virtual server has a separate port, (default 9988, counting up from there, so 9989, 9990), the query server port remains the same.

[ImportBot]

Originally Posted by micovery*:

 

For VirtualIDs ... deoes each virtual server have to have a separate port? If that's the case, you should be able to just probe internally 1 through 10 until finding the virtual server ... instead of asking the user for it.

Can't do that, because several virtual servers may exist.

I.e. - A single website may host several BC2 servers, and just create different TS virtual servers for all of them.

 

Note: While each Virtual server has a separate port, (default 9988, counting up from there, so 9989, 9990), the query server port remains the same.

I see. You can still do it though, if the SerqueryQuery API allows you to find out what the voice port number is.

Once you get a positive connection, request and compare the server voice port. It's a bit more complex, but people will always know what their server voice port is, as opposed to VirtualID. Anyway, you saw where I was trying to get to.

[ImportBot]

Originally Posted by Imisnew2*:

 

For VirtualIDs ... deoes each virtual server have to have a separate port? If that's the case, you should be able to just probe internally 1 through 10 until finding the virtual server ... instead of asking the user for it.

Can't do that, because several virtual servers may exist.

I.e. - A single website may host several BC2 servers, and just create different TS virtual servers for all of them.

 

Note: While each Virtual server has a separate port, (default 9988, counting up from there, so 9989, 9990), the query server port remains the same.

I see. You can still do it though, if the SerqueryQuery API allows you to find out what the voice port number is.

Once you get a positive connection, request and compare the server voice port. It's a bit more complex, but people will always know what their server voice port is, as opposed to VirtualID. Anyway, you saw where I was trying to get to.

I actually checked this out briefly before I replied earlier about the whole virtual ID thing, but didn't find anything. However, I'll take another look.

 

As for a brief update on the development of the plugin, it should now match based off of IP, which means your TS3 name and BC2 name are irrelevant. (huzzah_) I'll post a full change-log when I release it sometime next week.

[ImportBot]

Originally Posted by Imisnew2*:

 

Version 0.5 has been released.

The Major changes are matching based on IP and some crash fixes.

[ImportBot]

Originally Posted by Imisnew2*:

 

Apparently and issue has risen, where the plugin will crash when a player leaves teamspeak under special conditions...

I'm sorry, but for now, use v0.4.

A hotfix should be deployed some time tomorrow.

[ImportBot]

Originally Posted by CaptainSilver*:

 

I don't think that's possible, because that would require the person who writes "@teamspeak" to have teamspeak installed. Also, I can't control what programs on a player's computer does.

Hi Imisnew2,

 

I expect, that the person who writes @teamspeak has TS installed already and maybe even running but not connected our TS-Server. Would it be possible to connect to our TS then? Which conditions does it need?

[ImportBot]

Originally Posted by Imisnew2*:

 

I don't think that's possible, because that would require the person who writes "@teamspeak" to have teamspeak installed. Also, I can't control what programs on a player's computer does.

Hi Imisnew2,

 

I expect, that the person who writes @teamspeak has TS installed already and maybe even running but not connected our TS-Server. Would it be possible to connect to our TS then? Which conditions does it need?

As much as I'd like to help, it's really not possible.

It would be much less complicated for the player to just join your teamspeak themselves.

[ImportBot]

Originally Posted by CaptainSilver*:

 

Ok, never mind I thought it might be possible.

[ImportBot]

Originally Posted by gazzac*:

 

hi guys im having big probs trying to set this up i carnt even get it to connect i have ts3 and a gameserver could some1 plz talk me through it if possible ts is 212.187.247.41:9130 many thanks

[ImportBot]

Originally Posted by Imisnew2*:

 

hi guys im having big probs trying to set this up i carnt even get it to connect i have ts3 and a gameserver could some1 plz talk me through it if possible ts is 212.187.247.41:9130 many thanks

You need to make sure that "TS3 Server Port" is the server's query port.

By default, this is 10011.

You also need to make sure the Username and Password is the server's query username and password. Or whatever you want to call it.

First post of the second page of this thread shows how to get the information (if you have direct access to the server). Let me know how it goes, or if you need anything else clarified.