Magitex

Here's my custom version of Liberation with ACE3 and ALiVE integration and a bunch of other random modifications. Change log is below. This mission was designed to give smaller groups some AI support and commandable assets. The developer offers no support for custom versions of Liberation so if you have an issue you should PM me rather than ask the developers here. The save should not interfere with the ordinary Liberation save, but you should keep in mind it is a highly experimental version. The mission was briefly tested in multiplayer both with and without dedicated. (based on Liberation 0.902) http://www.mediafire.com?t6jyz7843l3ddsu Changes: edit: updated for 0.902

zbug, where would the best place to add static opfor mortars be? I added mobile artillery to spawn_battlegroups but I'm not sure where to add static defenses in your code.

I already set it so that it does not affect the dedicated spawner, as I figured that would often be the case. I never really thought about adding another actual helicopter however, that's a much more predictable solution. The mere sight of the Huron had me in tears :P

Just a word about the Huron, being a DLC chopper it poses both a significant annoyance and a lot of confusion for anyone who didn't start with a FOB already built. In my version I alter the FOB mass to <4t for anyone who is not using the DLC so that the UH-80 is able to lift FOB containers. startgame.sqf [ [_fobbox, 3999] , "setMass2"] call BIS_fnc_MP; dobuild.sqf if ( _classname == FOB_box_typename ) then//Magitex: experimental MP code, only setting mass of fob on client if they lack helicopter DLC { if (!(288520 in (getDLCs 1))) then { [ [_vehicle, 3999] , "setMass2"] call BIS_fnc_MP; //_vehicle setMass 3999.0; //diag_log format ["Creator does not own Helicopter DLC, reducing fob box mass."]; }; }; init.sqf //Magitex: fix for remote execution disallowed setMass2 = { private ["_veh", "_mass"]; _veh = _this select 0; _mass = _this select 1; _veh setMass _mass; }; It's probably safe to just set the FOB container to 3.999t regardless of who spawns it, I don't think it makes a particularly large difference. I also use the DLC code on the server if it is not dedicated to spawn a UH-80 instead of a Huron.

You probably already found this but: Liberation 0.89 alpha-2 \scripts\fob_templates\template2.sqf line 62: [ "Land_Pod_Heli_Transport_04_ammo_F", [6.23, 10, 0], 270.25 ], The trailing comma needs to be removed. I'm currently working on an ACE3/ALiVE version of Liberation with working AI mortars. So far everything is working correctly, but I haven't done sufficient multiplayer testing. Changelog (personal version, not related to official development of Liberation): It's mostly for lower population coop, so that players have ammo logistics, the ability to command AI squads, CAS support, smart mortars (both player and opfor) etc. I'll post it here once I've verified MP compatibility.