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

Issue with the Callsign attribute #1470

Closed
R3voA3 opened this issue Jun 28, 2021 · 1 comment · Fixed by #1471
Closed

Issue with the Callsign attribute #1470

R3voA3 opened this issue Jun 28, 2021 · 1 comment · Fixed by #1471
Labels
Milestone

Comments

@R3voA3
Copy link
Contributor

R3voA3 commented Jun 28, 2021

Mods

  • Arma 3: 2.05 [e.g. 1.00 stable, rc, dev]
  • CBA: 3.15.1

Description:
When creating a scenario with CBA and setting the Callsign attribute it will replace the default expression with
expression="[_this, _value] call CBA_fnc_setCallsign";

This will not create a dependency but if the mission is then played without CBA the attribute will do nothing since the function is not available.

Steps to reproduce:

  • Place a group
  • Set the callsign attribute with CBA loaded
  • Export the mission to SP
  • Play the mission without CBA
  • Check the callsign

Where did the issue occur?

  • Editor (Singleplayer) / Editor (Multiplayer)
@R3voA3 R3voA3 added the Bug label Jun 28, 2021
@commy2 commy2 added this to the 3.15.4 milestone Jun 28, 2021
@commy2
Copy link
Contributor

commy2 commented Jun 28, 2021

https://github.com/CBATeam/CBA_A3/blob/master/addons/common/Cfg3DEN.hpp#L30

->

                        expression = "\
                            if (isNil 'CBA_fnc_setCallsign') then {\
                                _this setGroupID [_value];\
                            } else {\
                                [_this, _value] call CBA_fnc_setCallsign;\
                            };\
                        ";

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants