You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mods (complete and add to the following information):
Arma 3:2.14
CBA:CBA_A3 v3.16.0.231017 Make sure to reproduce the issue with only CBA on a newly created mission!
Description:
After the recent update to CBA, CBA settings for Task Force Radio Arrowhead (Beta) version 1.0.334 no longer is honored if the CBA settings for TFAR contains spaces. I believe it is related to #1581 which I believe is stripping white space to support multi line.
Steps to reproduce:
Create a Teamspeak Channel for Task Force Arrowhead Radio with Spaces in the name such as Main Operation Server
Under the CBA settings configure the TFAR settings... TFAR_Teamspeak_Channel_Name = "Main Operations Server"
Join a server.
You will not get pulled in to the channel but instead stay in the channel you were initially
Review the Server Settings and you notice that the Spaces are not honored. You must Change the Teamspeak Channel to have no spaces.
Edit the Teamspeak Channel to Match the CBA Settings but without spaces.
You will be instantly moved into the matching channel (Ignoring Spaces)
Expected behavior:
Be pulled in to the matching Task Force Teamspeak Channel that is listed in the CBA settings Configuration under user config.
Mods (complete and add to the following information):
2.14
CBA_A3 v3.16.0.231017
Make sure to reproduce the issue with only CBA on a newly created mission!
Description:
After the recent update to CBA, CBA settings for Task Force Radio Arrowhead (Beta) version 1.0.334 no longer is honored if the CBA settings for TFAR contains spaces. I believe it is related to #1581 which I believe is stripping white space to support multi line.
Steps to reproduce:
Main Operation Server
TFAR_Teamspeak_Channel_Name = "Main Operations Server"
Expected behavior:
Where did the issue occur?
Log Files:
https://gist.github.com/EagleTrooper91/597f20d60c8144271c7e225263ab42c1
Additional context:
This was working just prior to the October 17th 2023 update.
The text was updated successfully, but these errors were encountered: