Resistance with old custom AddOns

[tigeros 0]

I have an annonying problem with it:

In some custom MP Mission the Ash RealIFV.pbo is required, so I download this addon. And now when I play Kolgujev(or Novoga)\1-9_T_Conquerors it pops out a message saying that something like "missing addon: ashm2ifvreal". I checked that ASH RealIFV AddOn, that class is exactly defined in it. I don't understand why this happens by a mission which does not need that addon and even the addon is definitive there. Is there a conflict?

By the way my Resistance is using 1.96 final patch and I copied that AddOn into Res\AddOns.

Regards

[Sniperwolf572 758]

OFP is weird by itself,dont worry about it,I oftenly get "Missing BAS_Kiowa" even if it isn't in the mission,usually happens in multiplayer missions.

You can call it one of OFP's features.

Don't worry about it pal,just play the mission.

[PRiME 1]

This happens because addon makers (some of them) are using class names that are very common and cause conflicts with other addons or even standard addons,.

Its quite easy to fix for someone who is very experienced with OFP scripting and config files, the other only way would be to try ploping it in /addons folder (whichever addon might be causing the problem)

Personaly myself I just fix the addons doing weird stuff like this myself. (don't ask me to fix your addons )

[killswitch 19]

Tigeros, the symptom you are seeing is typical of many addons, especially older ones but even newer ones suffer from it.

The reason

The reason you get the error message is that Ash's RealIFV addon depends (i.e needs) the original BIS Bradley and BMP-2 addons (which you have) but doesn't declare that dependency. When one then puts such an addon into a mod folder (Res is technically a mod folder, albeit an implicitly loaded one), the "Cannot load mission, missing addons..." messages start to appear. You'll even see that message when trying to load mission that doesn't have any of Ash's IFV:s in them (such missions, however, have either the BIS Bradley or BMP-2 in them, which is why you get the odd error message. Incidentally, this is another way the lack of a proper dependency specification manifests itself)

Fixes?

The quick and dirty one that might hide the problem: put the offending addon into the base OFP\Addons folder, i.e not into OFP\Res\Addons folder. That helps somewhat.

The proper fix involves editing the config.cpp within the ASH RealIFV.pbo so as to make it correct. One has to add a requiredAddons property to it. Here's the relevant part of it for those who want to fix the addon for themselves:

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">

class CfgPatches

{

class AshM2IFVReal

{

units[]={"AshM2IFVreal","AshM113real"};

weapons[]={"AshM220TOW","AshBushmaster","AshBushmasterHE","AshBushmasterAP","AshM2Coax","Ash50calIS"};

requiredVersion=1.85;

requiredAddons[]={"Bradley"};

};

class AshBMPreal

{

units[] = {"AshBMPreal","AshBMP2real"};

weapons[] = {"Ash73mm","AshBMP30mm","AshAT3","AshAT5","AshBMPCoax"};

requiredVersion = 1.85;

requiredAddons[]={"bmp2"};

};

};

However, if you're not accustomed to messing about with the internals of an addon, I'd just move the addon into OFP\Addons (create that folder if you don't already have one) and see if it helps.

[tigeros 0]

Thanks for all your helpful tips.

Killswitch's solution maybe the perfect one for me. I tried it, it works. But I must put the modded PBO in RES\Addon, or the mission that needs this addon won't load if I put it in other directories like OFP\Test\AddOn and use -mod=Test when I start OFPRes. I can't understand this. I though Res\AddOn is loaded before any other custom addons, hehe.

But anyway, I find a good solution now, who cares wether I put it in Res\AddOn or somewhere else

P.S.: The way moving this AddOn to OFP\AddOn has also worked for me, but I thought OFPResistance does not load AddOns in OFP\AddOn, and it proved me wrong