Add 'name' value to all CfgPatches

[commy2]

See: https://community.bistudio.com/wiki/CfgPatches

• also fixes certain objects placed in 3DEN causing the mission to require CBA due to use touching the class by adding XEH classes.
• also uses the new "name" instead of the configs classname in the help module (if present)

[commy2]

This is used in that required-addons-for-this-mission-feature (CfgPatches rework) from 1.60

Unfortunately the game uses configSourceMod to detect the origin of a class instead of units[], which means that every class where we fix for example class EventHandlers is detected as CBA-only class.
That is annoying and I'm searching for a work around, but I'm not sure I can fix that.

I'm not sure why they use that backwards method, when they have unitAddons

unitAddons "C_Driver_1_F"
-> ["A3_Characters_F"]

configSourceMod ("C_Driver_1_F" call CBA_fnc_getObjectConfig)
-> "CBA_A3"

configSourceModList ("C_Driver_1_F" call CBA_fnc_getObjectConfig)
-> ["kart","CBA_A3"]

[jonpas]

ECSTRING(Optional,Component)

[commy2]

Wouldn't that imply that "Optional" is a component?

[jonpas]

It would expand to the above. Not sure about semantics, if you are worried people might be looking for "optional" component then it might be best to leave it like that.

[commy2]

I added it everywhere I can, but there are some PBOs that don't or can't include the script_mod

[jonpas]

Make a ticket on A3 feedback tracker about it?

[commy2]

I actually found a funny way to solve this. You can add the addonRootClass which is supposed to be used in secondary configs in a component.

By adding:
addonRootClass = "A3_Characters_F"

That particular unit no longer requires "CBA - XEH". The problem is, that you can obviously only add one addonRootClass per component.

In 3DEN the unit is still shown with the CBA icon, but that has been the case before too.

[commy2]

NVM. Actually addonRootClass pushes every redefined class to the linked component. I'm going with A3_Characters_F since logic implies that at least one soldier has to exist in a mission anyway, right?