ALiVE_SYS_LOGISTICS_CARRYABLE - Review

[trapw0w]

Opening a ticket to review the ability to Whitelist carryable items. At the moment, Whitelist is defined but cannot be set as no module represents ALiVE_SYS_LOGISTICS & this cannot be directly modified from within the mission file due to current order of operations.

Possible Solutions:

• Relax default allow list (e.g. include "Object" or something similar)
• Add a custom suffix (e.g. ALiVE_SYS_LOGISTICS_CARRYABLE_CUST) that is appended to ALiVE_SYS_LOGISTICS_CARRYABLE on the addAction case.
• Add a whitelist input onto an ALiVE Module, similarly to how the Blacklist is currently done.

Points of interest:

ALiVE.OS/addons/sys_logistics/fnc_logistics.sqf

Line 140 in e21133f

GVAR(CARRYABLE) = [["Man"],["Reammobox_F","Static","StaticWeapon","ThingX","NonStrategic"] + (_logic getvariable ["WHITELIST",[]]),["House"] + (_logic getvariable ["BLACKLIST",[]])];

ALiVE.OS/addons/sys_logistics/fnc_logistics.sqf

Line 693 in e21133f

case ("carryObject") : {

[friznit]

Relaxing the default allow list may have unintended consequences unless it's possible to target specific groups of items by size or weight?

The current player log module is by exclusion - place module and sync items you want to exclude from logistics. We could add a separate logistics enabler module - sync objects to it that you want to include in player logistics.

And include the equivalent var to ALiVE_SYS_LOGISTICS_DISABLE, so you could put this setvariable ["ALiVE_SYS_LOGISTICS_ENABLE",true] in an editor object.

[trapw0w]

@friznit Happy with that. Only question I'd have is which list (blacklist/whitelist) do you treat as priority? E.g. If I have a class set in the whitelist that is also defined in the blacklist, which would we favour?

Similar issue with specifics, e.g. typeOf "House" is in the blacklist by default, what If I want to add a classname to the whitelist that would also return true for typeOf "House", e.g: Land_PortableLight_double_F?