enemies assigned to FFE's RydFFE_FOClass list within Init.sqf so that they can spot players and BLUFOR.
enemy artillery defined within FFE's RydFFE_Add_Other list so it knows what weapons FFE can use.
If this isn't done, FFE simply doesn't function.
Suggested change:
Ideally we would check the enemy preset case defined in KPLIB_preset_opfor and then pull from the arrays in KPLIB_o_militiaInfantry, KPLIB_o_militiaVehicles, KPLIB_o_armyVehicles, KPLIB_o_armyVehiclesLight, KPLIB_o_battleGrpVehicles, KPLIB_o_battleGrpVehiclesLight, KPLIB_o_troopTransports, KPLIB_o_helicopters. On top of this, we should also use the listed classes near the beginning of the file, which are:
KPLIB_o_officer
KPLIB_o_squadLeader
KPLIB_o_teamLeader
KPLIB_o_sentry
KPLIB_o_rifleman
KPLIB_o_riflemanLAT
KPLIB_o_grenadier
KPLIB_o_machinegunner
KPLIB_o_heavyGunner
KPLIB_o_marksman
KPLIB_o_sharpshooter
KPLIB_o_sniper
KPLIB_o_atSpecialist
KPLIB_o_aaSpecialist
KPLIB_o_medic
KPLIB_o_engineer
KPLIB_o_paratrooper
Do note that the preset directories for the cases are defined differently now.
Arsenals are in fn_initArsenal.sqf.
Enemies are still defined in init_presets.sqf
This pulls from preset files, like this example in custom.sqf.
In doing this, we could automate FFE implementation and make it more compatible.
Challenges:
FFE requires all listed enemies and enemy artillery to be in lowercase.
Anything can be converted to lower case with toLowerANSI. It supports underscores and quotation marks.
As of Chongo campaign, enemies needed to be listed in a long vertical list as opposed to a compact and neat array. Not sure if this is user error or if it's actually required. Will test.
How does the SAM site implementation differ from FFE? I assume FFE is a better choice still due to the sheer amount of settings.
Current State:
Every campaign needs to have:
RydFFE_FOClass
list within Init.sqf so that they can spot players and BLUFOR.RydFFE_Add_Other
list so it knows what weapons FFE can use.If this isn't done, FFE simply doesn't function.
Suggested change:
Ideally we would check the enemy preset case defined in
KPLIB_preset_opfor
and then pull from the arrays inKPLIB_o_militiaInfantry
,KPLIB_o_militiaVehicles
,KPLIB_o_armyVehicles
,KPLIB_o_armyVehiclesLight
,KPLIB_o_battleGrpVehicles
,KPLIB_o_battleGrpVehiclesLight
,KPLIB_o_troopTransports
,KPLIB_o_helicopters
. On top of this, we should also use the listed classes near the beginning of the file, which are:KPLIB_o_officer
KPLIB_o_squadLeader
KPLIB_o_teamLeader
KPLIB_o_sentry
KPLIB_o_rifleman
KPLIB_o_riflemanLAT
KPLIB_o_grenadier
KPLIB_o_machinegunner
KPLIB_o_heavyGunner
KPLIB_o_marksman
KPLIB_o_sharpshooter
KPLIB_o_sniper
KPLIB_o_atSpecialist
KPLIB_o_aaSpecialist
KPLIB_o_medic
KPLIB_o_engineer
KPLIB_o_paratrooper
Do note that the preset directories for the cases are defined differently now. Arsenals are in
fn_initArsenal.sqf
. Enemies are still defined ininit_presets.sqf
We can perhaps look at the recent SAM site implementation located in SAM_turret_manager.sqf and fn_getOpforSpawnPointSAM.sqf.
This pulls from preset files, like this example in custom.sqf.
In doing this, we could automate FFE implementation and make it more compatible.
Challenges: