[WIP] AI Profiles #164
[WIP] AI Profiles #164
Conversation
| class LAMBS_CfgAIProfiles { | ||
| class Default { | ||
| #ifdef ISDEV | ||
| allowDemoNumberAsBool = 1; |
There was a problem hiding this comment.
All of the profile stuff is in the main component, wouldn't it be better to have the dev values in danger and the actual prod default values in main?
There was a problem hiding this comment.
I would split it into the modules where it is used
There was a problem hiding this comment.
We do need then at least in the wiki some entry with all config entries. It is confusing to look at the code and only see a fraction of possible entries. (Or we have to tell people to use the config viewer)
There was a problem hiding this comment.
originally I planned to build a tool that shows and allows you to create and modify profiles in the editor in the release after the profiles where introduced. but writing a small export for the wiki is also fairly easy
| */ | ||
| params [["_target", objNull, [objNull, grpNull]], ["_tactic", "unkown", [""]]]; | ||
|
|
||
| private _profile = _target getVariable [QGVAR(AIProfile), "default"]; |
There was a problem hiding this comment.
Kind of a QoL thing. Have a cba setting which profile should be used as default
the CBA setting is a list of available profiles
There was a problem hiding this comment.
a dropdown would be impossible because they can be saved in the description and created via scripted modules. and parsing that while in the editor is from my knowledge not possible. the only thing for CBA setting we could do is a normal text box.
There was a problem hiding this comment.
The way I see it, is, a drop down is doable, but only account for config and missionconfig profiles. If someone adds them in editor OR via script it is in their authority to set the default correctly.
profiles created via editor can be used as default
Start Working on UI
rename doesProfileAllow to getProfileValue
No description provided.