Jump to content

Teamspeak 3 Sync


ImportBot

Recommended Posts

  • Replies 1.2k
  • Created
  • Last Reply

Top Posters In This Topic

  • ImportBot

    1233

Originally Posted by DeadWalking*:

 

Well that is a bummer that you are having problems with getting TSSync setup properly, but since I am a novice to PROCon and any of its plugins. I would say that is completely user error since I had little to no problems getting ours setup in the first shot by reading the directions and following it to the tee.

 

I had to coordinate with the host of our TS and the box our layer is on in order to get it setup. In coordinating with those hosts I was able to get it going.

 

I would recommend starting from scratch with just using the TSSync plugin in order to get it dialed in then transfer your settings once it is working to your current PROCon.

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by QUACK-Major-Pain*:

 

Can someone help me with this. I get this and nothing happens. Thanks

[09:22:17 81] Ts3 Sync: Stopping Synchronization...

[09:22:19 48] Ts3 Sync: Attempting to establish a connection to Teamspeak. Please allow 30-60 seconds for this to complete!

[09:22:19 50] Ts3 Sync: Established connection to 66.55.131.14:9100.

[09:22:19 68] Ts3 Sync: Authenticated as SteelGluer.

[09:22:19 70] Ts3 Sync: Selected the virtual server on port 9212.

[09:22:19 89] Ts3 Sync: Found the staging channel.

[09:22:20 90] Ts3 Sync: Beginning Synchronization.

Did you change your query port?

Default query port is 10011

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by QUACK-Major-Pain*:

 

this line keeps vanishing ip_of_teamspeak query_port_of_teamspeak. in the config file. Yes the ip was added. Thanks

You can edit the file and save it, and then change the properties of the file to read only before you start ts3
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by steelgluer*:

 

You can edit the file and save it, and then change the properties of the file to read only before you start ts3

yup I did it step by step several times. Somtimes it will come on then procon freezes up.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Imisnew2*:

 

Ok guys. There are a few minor issues I am going to address before December, but I do not have the time to poke around the code, which I haven't touched for a few months, until the end of December (end of American college classes). If you feel there's another item that would take

 

  • Upping 32 player limit threshold cap to 64.
  • Removing "Team 0." - May inadvertently fix 'deleting channels' crashing issue.
  • Allow the user to specify team channels so that they can be placed anywhere.
  • Fix 'Moving from any channel' bug - Might take too long.

In December, I will attempt to address the remaining issues, mostly dealing with Connection Errors, Teamspeak Query Response Errors, and Restart Issues. At this point, I will release the plugin as a full "1.0" version, and bring it out of Beta.

I hope to release 0.9.3 later this week. I'm having trouble re-creating some of these issues, bare with me.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by nbtc971*:

 

Well some of my guys are wanting to remove the "Odin" plugin because it keeps moving them all of the time even when they just want to talk to someone, or, they can't join a channel because it's locked. One even said he doesn't get on TS anymore because of the plugin. I'm telling them to slow down that a fix is coming, but who knows. Some of them just like talking to everyone and don't care so much about team communication. I want team play and told them the plugin stays because it's being fixed.

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by DeadWalking*:

 

I ran into that same bit of thick headedness over at my community initially. Getting ti dialed in and tweaked just right can add to the enjoyment.

 

I have set my TeamThreshold to anywhere between 8-16 depending on who is on and how many. I currently just leave SquadThreshold to -1 until we start to get more pubbers joining the TS server. How anyone can say it is fun to hear 16 people all trying to talk and laugh and jabberjaw all at the same time is beyond me. I personally prefer to here the game and info from my squad mates telling me there is a guy coming up behind me, but to each his own I guess.

 

As it sits right now if they want to chat talk then they need to leave the game server and what do you know they can chat. Then if server is full ask one of your other members for a kick to a pubber so they can get in. Easy as pie really.

 

Hopefully Imisnew can get the forcing from any channel fixed and it would remove most of there problems. I havnt tested either but if it is really that necessary to chat to certain people they may want to look into creating some whisper lists.

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Imisnew2*:

 

I hope to release 0.9.3 later this week. I'm having trouble re-creating some of these issues, bare with me.

Initial results are promising. Looking to release the fix Wednesday some time if all goes well.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Imisnew2*:

 

Version 0.9.3 Released.

 

I was only able to fix the 32 player limit, removing team 0, and the 'Moving from any channel' bug. Unfortunately, allowing the user to specify team channels ended up being a little bit more complicated than I thought. I'll look into including this in the final release. To recap:

Ok guys. There are a few minor issues I am going to address before December, but I do not have the time to poke around the code, which I haven't touched for a few months, until the end of December (end of American college classes). If you feel there's another item that would take

 

  • Upping 32 player limit threshold cap to 64.
  • Removing "Team 0." - May inadvertently fix 'deleting channels' crashing issue.
  • Allow the user to specify team channels so that they can be placed anywhere.
  • Fix 'Moving from any channel' bug - Might take too long.

In December, I will attempt to address the remaining issues, mostly dealing with Connection Errors, Teamspeak Query Response Errors, and Restart Issues. At this point, I will release the plugin as a full "1.0" version, and bring it out of Beta.

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by TheDaddy2003*:

 

actually what is the point to this plugin? it just moves people channel? doesn't load teamspeak if they have it installed and force them to join ur server? because if all this plugin does is move u channel its pretty shit!

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Imisnew2*:

 

@TheDaddy2003

 

From the very first post and description in Procon:

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

If you require additional functionality, I'm afraid this plugin isn't for you.
* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by DeadWalking*:

 

Seemed to work well thru multiple rounds tonight!

 

No crashes, no errors, could leave the Staging Channel and not get drug back in! Should get a longer test session tomorrow after Turkey Dinner.

 

 

Thanks Imisnew2

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by DeadWalking*:

 

I didn't notice the delete channel bug occur in the plugin console output, but I was also running several plugins to dump debug info while I had time to look thru the day.

 

But at one point when I came back to the layer I noticed the plugin was disabled. I never got to confirm if one of the other 2 members with access to the plugins had turned it off or not.

 

Hopefully I will get a better opportunity to monitor it tomorrow/today (its late or early depends how you look at it AK Time here). Been setting up XLRStats all day on 4 servers.

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by droopie*:

 

cant figure out what this is...

[21:01:25 49] Ts3 Sync: There was an issue finding the channel =TBU= Server #1 (Mixed Mode).

[21:01:25 49] Ts3 Sync: Check your Staging Channel Name then try again.

[21:01:25 49] Ts3 Sync: A query error occurred:

[21:01:25 49] Ts3 Sync: 2568: insufficient client permissions failed_permid=8474

* Restored post. It could be that the author is no longer active.
Link to comment

Originally Posted by Imisnew2*:

 

@nbtc971 & DeadWalking

 

Remove channels should be fixed.

 

 

@droopie

 

Your teamspeak server query login does not have enough permissions... meaning, you'll have to ask your Teamspeak Server Provider to add the correct permissions to your server query login so that the plugin can operate normally.

* Restored post. It could be that the author is no longer active.
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.




×
×
  • Create New...

Important Information

Please review our Terms of Use and Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.