PMC Editing Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== ArmA 1 Mod directory's ======

[[https://www.pmctactical.org/forum/viewforum.php?f=42|ArmA 1 Forum]], [[:arma|ArmA 1 Home]], [[arma:config|ArmA 1 Config]], [[arma:tools|ArmA 1 Tools]], [[arma:file_formats|ArmA 1 File Formats]], [[arma:missions|ArmA 1 Missions]], [[arma:modeling|ArmA 1 3D Modeling]], [[arma:terrain|ArmA 1 Terrain]], [[arma:texturing|ArmA 1 Texturing]], [[arma:scripting|ArmA 1 Scripting]]

**ArmA 1** aka Armed Assault (ArmA)

Mod directory's. Children says folder, men say dir ;)


====== Introduction ======

Custom mod dirs is a concept in Operation Flashpoint and Armed Assault that allows addon makers and players to completely change most aspects of the game. They were introduced with the release of the OFP: Resistance addon, which also became the first total conversion modification.


====== Making it Work ======

To load and use a mod dir it has to be added to the games startup parameter "-mod". This is easiest done by creating a new shortcut and editing the startup command.

If you for example are trying to load a mod named //test// the startup command might look like this:
<code>
C:\ArmA\ArmA.exe -mod=test
</code>
To load several mods separate their names with the ";" character, like this:
<code>
C:\ArmA\ArmA.exe -mod=test1;test2;test3;test4;test5
</code>

You can create batch files (.bat) to start your OFP/ArmA. Here is one good full example of our bat file:
<code>
START "" /D"%CD%" /B "%CD%\beta\arma.exe" -mod=beta;x\terrain;x\coc;x\pmc -nosplash -world=empty -profiles=d:\ArmA
</code>


====== How it Works ======

The "-mod" parameter defines a path the engine will use to load data files when loading the game. It is important to remember that the OFP: RES mod will automatically be added first to the list of mod dirs (OFP only). A mod dir can contain all the data that your OFP / ArmA install dir can contain. This includes missions, campaigns, and addons subdirs, etc. The most common use of mod dirs is to organize addon .pbo files.


====== Addon moddirs ======

Since most players today have a very large number of extra addons installed it has become a common practice to divide them into addon mod dirs. The benefit of this practice is that the engine only has to load the addons in the mod dirs specified by the player, lowering memory usage significantly. To create an addon mod dir simple pick a name and create the directories "myname\Addons\" in the Operation Flashpoint directory. Next place all addons you want in this mod dir into this directory and add "myname" to your "-mod" list when these addons are needed.

To make this easier you might wish to create several shortcuts loading different mod dirs.

The main drawback of this technique is that it's hard for other players in multiplayer games to know what kind of changes you are playing with as mod dirs can be used to make beneficial configuration changes to the game, in other words cheat.

====== Conflicting addons / addon load order ======

In ArmA, it is possible for addons to modify classes in other addons, including those in the game's core "addons". If the user installs two addons that try to modify the same property of a given class (for example, the model property of the basic soldier class), then obviously both addons can not work as intended (together in the same install, that is).

In these cases, there is almost nothing that the user can do to determine which addon takes "priority". Inside of the addons themselves is a property called "RequiredAddons", which determines addon load order, regardless of mod dir order.