What defines an Addon name as used in mission.sqm / config.cpp

[shinkicker 5]

Yesterday I was having issues with a missing Addon which is loaded through the mission.sqm.

I had placed the entry under the same naming used for the pbo.

So lets say the PBO is was called 'xyz_addon.pbo'

I then made a mission entry of:

class Mission

{

addOns[]=

{

"xyz_addon"

};

It then turns out that I would get the 'You cannot play/edit this mission as it depends on content that has been deleted.xyz_addon'

By luck through a Google search I found another mission file where the same addon was used and declared as follows:

{

"wxyz_addon"

};

I made the amendment and the addon loaded.

So I wanted to ask what defines the addon name as called within the mission file / config.cpp?

It seems its not based on the file name minus the extension (.pbo)

[ProfTournesol 956]

http://community.bistudio.com/wiki/Mission_Editor:_External#Mission.sqm Edited October 23, 2012 by ProfTournesol

[shinkicker 5]

http://community.bistudio.com/wiki/Mission_Editor:_External#Mission.sqm

I know what a mission file is thanks. That was not the question I was asking.

If you read my post again its quite clear. I want to know what defines the addon name, as its not the filename.

Edited October 23, 2012 by shinkicker

[HitmanFF 6]

It's the CfgPatches definition in the addon's config.cpp (or config.bin). Check Mondkalb's addon tutorial for an example.

[shinkicker 5]

It's the CfgPatches definition in the addon's config.cpp (or config.bin). Check Mondkalb's addon tutorial for an example.

Perfect, thanks

That's what the issue was, they named the addon and the main def in class CfgPatches differently.

[ProfTournesol 956]

Perfect, thanks

That's what the issue was, they named the addon and the main def in class CfgPatches differently.

If you read the link i posted instead of making smart comments, you'll have seen this :rolleyes: