Attantion: CFX team implemented a NUI blacklist and blocked local (127.0.0.1 and localhost) WebSocket connections.
If the clientside can't connect to the WebSocket, make sure that you can resolve lh.v10.network:
Open Windows Command Prompt by searching cmd
Execute nslookup lh.v10.network
If it resolved to 127.0.0.1 then your issue is probably somewhere else, if not then you can use e.g. Google DNS servers.
Config
Variable
Type
Description
VoiceRanges
float[]
Array of possible voice ranges
EnableVoiceRangeNotification
bool
Enables/disables a notification when chaning the voice range
VoiceRangeNotification
string
Text of the notification when changing the voice range, {voicerange} will be replaced by the voice range
Limits some radio functions like using the radio while swimming/diving and allows only one sender at a time
UltraShortRangeDistance
float
Maximum range of USR radio mode
ShortRangeDistance
float
Maximum range of SR radio mode
LongRangeDistace
float
Maximum range of LR radio mode
MegaphoneRange
float
Range of the megaphone (only available while driving a police car)
NamePattern
string
Naming schema of TeamSpeak clients, {serverid} will be replaced by the RedM server ID of the client, {playername} by the name of the client and {guid} by a generated GUID
I seem to be having some troubles /w getting other players who connect to the RedM server /w Teamspeak open to automatically change channels. It works for me, but will not work for them. No errors are produced in the console. It works for 1 player, but not another. Any Suggestions?
We noticed salty chat changed their port from 8088 to 38088 via the resource.
This caused issues for a lot of our clients, as their AppData\Roaming\TS3Client\plugins\SaltyChat\settings.json was keeping 8088 port as default even after an update to salty chat tsplugin 2.0
We've asked our users to delete the settings.json file and restart teamspeak so that it recreates the settings file with the correct new default port 38088.
Please fix the plugin so that it automatically changes the users port from 8088 to 38088 regardless of what their current settings.json says.
Actually we use Saltychat for FiveM and also for RedM. Both works very fine.
A few days ago RedM released an "Alpha" Stage for RedM Onesync. We updated our Server for it and Start test.
Now we found an issue with Saltychat. The Players can hear other Players over the Map. Its very weird and confusing.
Player 1 can hear Player 2, Player 3 can hear Player 4 but nothing else. Player 2 can hear Player 1, idk how to explain it correctly.
One time i walk to Player 1 and can hear Player 3. I walked out of Range and both gets muted.. it was very strange but we must stop the Test-Phase because with this issue its hard to make "Roleplay".
Is there any Update planned for the Onesync Compatibility?
Can we get a tutorial on how to instal the onesync build please.
Cause when i build and instal the pulgin on a onesync redm serveur it doenst detect the player near each other