Closed jokoho48 closed 3 years ago
Stringtalbe ;)
Lets do a team speak meeting
From meeting
With restructure consider renaming:
Thoughts?
Reminder for self:
Consider implementing a mod-wide disabling of enableAttack to give us better fine control of AI attack patterns. Units with the currentCommand "ATTACK" become wildly moody and difficult to manoeuvre with.
This would be an invasive change.
https://community.bistudio.com/wiki/enableAttack https://community.bistudio.com/wiki/currentCommand
Memo to self: Possibly add a CBA setting which stops units given WP/Modules from changing ACE3 style headless locality swapping.
this setVariable ["acex_headless_blacklist", true];
Add module which give a group the vanilla guard waypoint (and whatever enhancements we can provide or add to it). Possibly adding a second module to define new guard positions.
Small bugs:
Suppression Units are currently very suppression-happy. Will consider changing brainEngage to only allow "Can Fire" to trigger doSuppression, rather than also "Enemy Near".
Have noticed AI will sometimes suppress quite happily at nothings. Though this may be related to other features.
lambs_danger_CQB The group variable "lambs_danger_CQB" is I think poorly named. A better reflection of it being a sympathetic storeroom of positions to check or suppress would be "lambs_danger_memory" or similar. Perhaps write a function which makes reading and modifying the variable easier.
Todo
Found bugs - 08.02.21
Discarded Add settings for groupMemory feature <-- will require a restructure of a host of other features for very small gains.
Internal variable name change: lambs_main_isArtillery
The Restructure is meant to clean the file/code structure and move functions that are not just used by one Module and are not module specific into the main module. while that we also should clean and move duplicated stringtable entries into main to keep the stringtables as small as possible.
Functions
Settings
Stringtable
Unify Duplicated Entrys