Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest CBA version does not honor white space in the CBA settings Configuration File for Task Force Arrowhead Radio (BETA) #1619

Closed
EagleTrooper91 opened this issue Oct 19, 2023 · 2 comments
Labels
Milestone

Comments

@EagleTrooper91
Copy link

EagleTrooper91 commented Oct 19, 2023

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.

Where did the issue occur?

  • Dedicated & Self-Hosted Multiplayer

Log Files:
https://gist.github.com/EagleTrooper91/597f20d60c8144271c7e225263ab42c1

Additional context:
This was working just prior to the October 17th 2023 update.

image

image

image

@johnb432
Copy link
Contributor

@jonpas
Copy link
Member

jonpas commented Oct 24, 2023

Fixed by #1622.

@jonpas jonpas closed this as completed Oct 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants