After the patch I noticed the radio supports stopped working in my custom missions, I troubleshooted the problem and found out that if I put
cost_variable = ""; to anything other than blank (infinite) I cannot choose payload on any support that has any cost. I have the cost variable at 150 and most supports cost around 10. I can call in supports that have their costs set to 0 but no others.
Description
Description
Details
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Category
- General
Steps To Reproduce
Make a custom mission, copy the info from https://pastebin.com/embed_iframe/Nx1eWuX3 to your description.ext and then put anything other than a blank space in cost_variable = ""; . When trying to use the radio support it is not possible to select any payload for that support unless it's cost is 0.
Additional Information
Worked fine before the patch!
Event Timeline
Comment Actions
Unable to reproduce the issue, make sure your variable contains number not some other type.
- Used example config from wiki
- Added score variable to config
- Called "Rambler" callsign with cluster munitions
- Score was properly deducted and plane was called
See example mission:
Comment Actions
Setting the cost_variable to "arty_score" and then adding "arty_score = 150;" to the init.sqf worked, before I was able to do it by just setting "arty_score" to "150" in the description.ext but I suppose that isn't possible anymore? Or else I was dreaming before..
Comment Actions
To be more specific I uploaded my description.ext that worked before the patch (unless I'm crazy) but stopped working after the patch. Switching out "150" to "arty_score" and adding "arty_score = 150;" to the init.sqf worked like I said so I'm gonna go with that from now on.
edit: did a double check and I'm 99% sure that using a number as arty_score in description.ext worked before the patch (or at least a couple of months ago)
edit: did a double check and I'm 99% sure that using a number as arty_score in description.ext worked before the patch (or at least a couple of months ago)
Comment Actions
It probably worked but not exactly as intended as you weren't able to adjust the score that way. It was always intended to be NAME of VARIABLE that holds the score. Not the score value, as per comment in config/wiki documentation.