Synchronizing your voice state between TTT server and TS3.
If you play TTT and using TS3, you can use this tool to sync death state to TS3. If set up, the players only need to set their name on TS same as ingame. No longer someone screams in TS after dead.
Client - talk power to speak, value 0
& Client - channel group rights skip, value [ ](false/empty)
docker run -d \
-e TTTHost="1.2.3.4" -e TTTRconPassword="MySecurePW" \
-e VoiceHost="2.3.4.5" \
-e VoiceChannelName="MyModeratedGameChannel" \
-e VoiceLoginName="VoiceSync" -e VoiceLoginPassword="AnotherSecurePW" \
jusito/ttt_voice_sync:latest
java -jar ttt_voice_sync.jar env
docker run -d \
jusito/ttt_voice_sync:latest \
"TTTHost" "TTTPort" "TTTRconPassword" \
"RefreshTimeMS" \
"VoiceHost" "VoiceQueryPort" "VoiceServerID" "VoiceChannelName" \
"VoiceTargetGroupName" "VoiceDefaultGroupName" \
"VoiceBotName" "VoiceLoginName" "VoiceLoginPassword"
java -jar ttt_voice_sync.jar \
"TTTHost" "TTTPort" "TTTRconPassword" \
"RefreshTimeMS" \
"VoiceHost" "VoiceQueryPort" "VoiceServerID" "VoiceChannelName" \
"VoiceTargetGroupName" "VoiceDefaultGroupName" \
"VoiceBotName" "VoiceLoginName" "VoiceLoginPassword"
Variable | Default | Description |
---|---|---|
TTTHost | IP to your TTT server | |
TTTPort | 27015 | TCP Port for RCON, most of the time game port |
TTTRconPassword | password to your RCON | |
RefreshTimeMS | 250 | Time between two syncs (if to low crashes may occur) |
VoiceHost | IP to your TS3 server | |
VoiceQueryPort | 10011 | Port to serverquery |
VoiceServerID | 1 | Virtual server id |
VoiceChannelName | Name of the channel to join | |
VoiceTargetGroupName | dead | Channelgroup for dead state |
VoiceDefaultGroupName | alive | Channelgroup for alive state(careful with Guest if you have multiple virtual server) |
VoiceBotName | VoiceSync | Name for the tool on your TS server |
VoiceLoginName | serveradmin | server query login name |
VoiceLoginPassword | server query login password |
!reset
if the tool is ok, it will set all alive and write in the channel.Write me on github. Btw I have no clue why this multi stage build is that big, will be next.