ARMA 3 script thread

[Bailing_Out]

I'm doing this right now.

First way in the description ext file.

class CfgRespawnInventory
{
class WEST1
{
displayName = "Officer"; // Name visible in the menu
role = "Officer";

// Loadout definition, uses same entries as CfgVehicles classes
weapons[] = {
"LIB_MP40",
"LIB_M1908",
"LIB_Binocular_GER"
};
magazines[] = {
"LIB_32Rnd_9x19",
"LIB_32Rnd_9x19",
"LIB_32Rnd_9x19",
"LIB_32Rnd_9x19",
"LIB_32Rnd_9x19",
"LIB_32Rnd_9x19",
"LIB_32Rnd_9x19",
"LIB_32Rnd_9x19",
"LIB_32Rnd_9x19",
"LIB_32Rnd_9x19"
};
items[] = {
"FirstAidKit",
"FirstAidKit"
};
linkedItems[] = {
"V_LIB_GER_FieldOfficer",
"H_LIB_GER_OfficerCap",
"ItemMap",
"ItemCompass",
"ItemWatch",
"ItemRadio"
};
uniformClass = "U_LIB_GER_Officer_camo";
vest = "V_LIB_GER_FieldOfficer";
backpack = "B_LIB_GER_A_frame_zeltbahn";
};

Second way.

class WEST2
{
displayName = "Medic"; // Name visible in the menu
role = "medic";

//comment "Remove existing items";
removeAllWeapons _unit;
removeAllItems this;
removeAllAssignedItems this;
removeUniform this;
removeVest this;
removeBackpack this;
removeHeadgear this;
removeGoggles this;

//comment "Add containers";
this forceAddUniform "U_LIB_GER_Soldier_camo";
this addItemToUniform "FirstAidKit";
for "_i" from 1 to 10 do {this addItemToUniform "LIB_5Rnd_792x57";};
this addVest "V_LIB_GER_VestKar98";
for "_i" from 1 to 9 do {this addItemToVest "FirstAidKit";};
this addItemToVest "LIB_5Rnd_792x57";
this addBackpack "B_LIB_GER_Rucksack_Vide";
this addItemToBackpack "Medikit";
for "_i" from 1 to 3 do {this addItemToBackpack "FirstAidKit";};
this addHeadgear "H_LIB_GER_HelmetCamo";

//comment "Add weapons";
this addWeapon "LIB_K98";

//comment "Add items";
this linkItem "ItemMap";
this linkItem "ItemCompass";
this linkItem "ItemWatch";
};

The game has problems with the second way if its in the same file as the first way.

[Bailing_Out]

I went another way with it, I get exactly what I want, with selectable roles, the right loadout aside from some stuff not fitting but it throws an error. I put functionary clothes on a US soldier and he had them even after I took them off of him in the editor, it executed the scripted loadout not the loadout I left him with in the editor. I'm thinking of just leaving the error an saying screw it.

EDIT: I did something, wish I knew what and the error went away.

[Bailing_Out]

I couldn't get the toolkit into the backpack until I added it to that particular unit in the init sqf. It was in there but the game threw an error so I took it out of init sqf.

Weirdly though the unit kept the toolkit through multiple saves so I killed the editor, killed the server and exited the game. Came back, still in his backpack. I had tried to add that thing 7 different ways in scripts, its still in the script but only doing that loaded it.

Half my problems come from using independent, guerrilla and resistance in the right place. Init sqf won't really recognize independent or guerrilla, throws an error but you can use them in the description ext and the loadouts worked, there was just the error because init sqf didn't like it.

The other half of my errors is I will be editing the wrong damn file in Atom because I got two windows of it open so I can borrow stuff from another file. Then I wonder why nothings changed when I play/test the scenario.

[Bailing_Out]

I finally got loadouts like I want them and they work (without errors) now I want to figure out how to make the vehicle respawn modules only work when when that side has the sector and of course the other sides work only when they own it.

I'm gonna post and example of the loadout structure later, many know how to do it but some don't and the examples that are usually posted don't go past one loadout, figuring thats enough but morons like me need to see the structure of how it is structured with multiple loadouts. Mine is simple, 3 files, but long, copy and paste helps a lot though and with Atom you can change a buttload all at once.

I think the reason that one soldier kept the toolkit (mentioned in and earlier post) after I put it in the init sqf and then took it out of the init sqf after it caused an error but still worked is because it got written into the mission sqm by the game. Thats the only file that writes itself.