http://alivemod.com/forum/conversation/post/22782

Statics are, uhmm, static at the moment -> https://github.com/ALiVEOS/ALiVE.OS/blob/master/addons/mil_cqb/fnc_CQB.sqf#L48

I would advice against twerking ALiVE, but we can try and update the staticData for the supported factions with more appropriate weapons:

https://github.com/ALiVEOS/ALiVE.OS/blob/master/addons/main/static/CivPop.hpp

@highhead, your old AI Dist. code ran every 10s + exec time -> https://github.com/ALiVEOS/ALiVE.OS/blob/debfc4f9abcff4c369bcee5095d9175d0f0f0725/addons/main/fnc_AI_Distributor.sqf#L78

New code is 60s + exec time. We could lower it, or add an opition with 60/45/30/15 sec. interval in the module or something.

Spawn HQ makes the module spawn a HQ, in addition to the specified custom composition entered into the module.

The message only indicates that no suitable buildings found nearby to use as a HQ.

Config for a 100/100 server, ran fine. I dont think ALiVE needs any extra tweaks a part from the normal ArmA dedicated parameters.

MinBandwidth=10000000;
MaxBandwidth=1000000000;
MaxMsgSend=1024;
MaxSizeGuaranteed=1024;
MaxSizeNonguaranteed=256;
MinErrorToSend=0.001;
MinErrorToSendNear=0.01;
MaxCustomFileSize=0;
Windowed=0;

class sockets
{
    maxPacketSize = 1452;
};

Not possible at to change module params via mission params im afraid.

Start them on different cores with the /affinity option to the start command:

https://blogs.msdn.microsoft.com/santhoshonline/2011/11/24/how-to-launch-a-process-with-cpu-affinity-set/

Had the server running on core 1 and 2, HC1 on 3, HC2 on 4. Core 0 and 5 left for OS etc. 6-core Xeon btw.

The 3rd-party checkbox is as far as i know just a placeholder for now. Normal ALiVE IEDs are configured to be detectable with a ACE minedetector, but disarming them is still just a normal interaction. Nothing is tied to ACE Explosives, yet. I will start tinkering with it and get the IEDs fully ACE compatible, soon™.

ALiVE_fnc_OPCOMToggleInstallations is the function you're looking for, check ALiVE_fnc_OPCOMdropIntel for how the Read Intel action is added to the dropped intel and the function is called. Both live in mil_opcom.