M1ke_SK

any plans to continue in linux support ?

what object are you referring to ? box1 or supply_pos ? You can create them both in editor and them move supply_pos to your designated area ( mid game ) with setPos command or just move it with zeus.

you can place an invisible helipad or any object, name it "supply_pos", then use command distance in trigger for condition write: ( box1 distance supply_pos ) < 5 where 5 is distance ( in meters ) from supply_pos object

https://community.bistudio.com/wiki/Arma_3:_ORBAT_Viewer#ORBAT_Group_Module

create file initPlayerLocal.sqf in your mission root, and add this line to it // initPlayerLocal.sqf player addEventHandler ["HandleRating", {0}];

private _isZeus = not isNull ( getAssignedCuratorLogic _unit );

anybody got link ? original link and armaholic is dead

I will take a look at that "no damage" issue. I mostly test script on singleplayer and dedicated server. At this time I am in process of rewriting script with new commands.

so in order to disable "+" button, you also need to disable event link to it added by BIS. you can find this event in file \a3\functions_f_bootcamp\Inventory\fn_arsenal.sqf code: _ctrlArrowRight = _display displayctrl IDC_RSCDISPLAYARSENAL_ARROWRIGHT; _ctrlArrowRight ctrladdeventhandler ["buttonclick","with uinamespace do {['buttonCargo',[ctrlparent (_this select 0),+1]] call bis_fnc_arsenal;};"]; here is final solution how to disable "+" button private _enabled = false; // your switch to enable/disable button private _display = findDisplay -1; private _button = _display displayCtrl 993; _button ctrlEnable _enabled; _button ctrlRemoveAllEventHandlers "ButtonClick"; if ( _enabled ) then { _button ctrlAddEventHandler ["ButtonClick", "with uinamespace do { ['buttonCargo', [ctrlparent ( _this select 0 ), +1]] call BIS_fnc_arsenal; };"]; };

so I figured how to disable "+" button, but there is still something missing, as when I click on button, it does action regardless _control is disabled { private _ctrl = _display displayCtrl _x; _ctrl ctrlAddEventHandler ["LBSelChanged", { params ["_control", "_selectedIndex"]; private _enabled = false; // set to false for debug purposes if ( _selectedIndex isNotEqualTo -1 ) then { private _display = findDisplay -1; private _plusButtonCtrl = _display displayCtrl 993; _plusButtonCtrl ctrlEnable _enabled; // this does not work }; }]; } forEach [ 984, // misc 983, // explosives 982, // grenades 986, // magazines 981 // magazine ];

I checked ace3 arsenal and they do handle this problem with disabling "+" button for blacklisted items

I have whitelisted arsenal like this ( executed in addAction ) _box setVariable ["bis_addVirtualWeaponCargo_cargo", nil, true]; [_box, _items, false, false] call BIS_fnc_addVirtualItemCargo; [_box, _weapons, false, false] call BIS_fnc_addVirtualWeaponCargo; [_box, _magazines, false, false] call BIS_fnc_addVirtualMagazineCargo; [_box, _backpacks, false, false] call BIS_fnc_addVirtualBackpackCargo; ["Open", [false, _box, _player]] call BIS_fnc_arsenal; I have declared whitelisted items in arsenal like this _items = ["FirstAidKit"]; Problem: when player pick up restricted item from enemy / ground and put it in inventory, then he go to whitelisted virtual arsenal, he can duplicate/multiply this restricted items ( for example: "Medikit" ) with "+" button Expected result - player should not be able to increase number of restricted items in loadout Given: - virtual arsenal is whitelisted with BIS_fnc_addVirtualItemCargo When: - player pick restricted item and enters whitelisted arsenal Then: - item should not be increased ( disabled + button ) for adding more Possible solutions: - disable "+" button in arsenal UI for restricted items ( I did not find yet _control IDC of arsenal _display yet ) private _plusButton = _display displayCtrl 993; - remove restricted item from players inventory when open arsenal - I tried to disable item with this command, but problem still occurs [_box, ["Medikit"], false] call BIS_fnc_removeVirtualItemCargo;

you can use git hooks

@daniellarusso any update on issue ?

I mentioned this already. I have a fix ready, but testing on dedicated server. Just have a patience.