Campaign, in addons/ dir, huh?

[Snake Man 407]

Some of you who have been digging around the ArmA 2 files have found out that the campaign is located in the addons\missions.pbo ... err pbo. Inside the missions.pbo there is directory "campaign" and in this dir you have the usual campaign as you've seen many times in OFP and ArmA (1).

The $PBOPREFIX$ says the missions.pbo is at ca\missions namespace\dir.

So now I'm thinking, I believe the old method of putting a campaign in "myCampaign.pbo" and placing it to armaroot\campaigns\ directory (or campaigns\ in mod dir) still works... what is the real difference of these two methods, which one "should" be used and so on?

Would it be easier for users out there to download a mission or campaign and put it into addons dir as those millions of addons available, does it take brainiac to understand that normal campaign file need to be put in campaigns\ directory?

Also, do the "missions.pbo" need the config.cpp to be detected by ArmA 2, or does it read any pbo contents automatically?

I'm asking because I honestly don't know, I'm scratching my head here which method to use :)

[.kju 3245]

You can also set the prefix to:

campaigns\MyCampaign.pbo

Should not need a config and can be moved to any addons folder.

[TeRp 1]

I think it is intended for use with mods that come with their own campaigns and missions. The benefit of putting the mod's campaign and missions into the mod's addons directory is that those missions (and campaigns) will only show up if the player has loaded the mod, too.

So you there won't be any trying to start a campaign and getting a missing addons error this way ;)

Yet, in my opinion, this is only a minor improvement.

User-made sp missions / mp missions that are not part of a mod will still go to the default ArmA mission directories instead of having own mission directories for each modfolder. Would make administrating a game server a lot easier.

Oh, and this already worked in ArmA. :)

I think warfare used a pbo file in the addons folder, too.