ugen_Data
In the new directory create of course $PBOPREFIX$ and config.cpp with just the cfgPatches. In our case these are:
$PBOPREFIX$
<code>
pmc\pmc_rugen_data
</code>
config.cpp
<co... ory called <TerrainName>_Data_Layers\ and create $PBOPREFIX$ and config.cpp as mentioned earlier with _Data d... c_rugen_data_layers_00 >pmc_rugen_data_layers_00\$PBOPREFIX$
echo pmc\pmc_rugen_data_layers_01 >pmc_rugen_dat
l_terrain\source\
</code>
Now create file name "$PBOPREFIX$" in this directory, so it will become:
<code>
\tut\tut_tutorial_terrain\$PBOPREFIX$
</code>
Now open $PBOPREFIX$ in text editor and write the following line there:
<code>
tut\tut_tutorial_ter... e>
This is your namespace \ addon name directory, pboprefix file tells arma3_x64.exe where this addon's files
a pbo wysiwig
-P PrefixName this will over-ride $PBOPREFIX$ and use a direct over-ride
</code>
Notes:
rapif... only. They are not, 'binarized'
Note that if a $PBOPREFIX$ file is detected in the pbo folder. It takes pre... mply by stating ArmA, or Elite as an option. The $PBOPREFIX$ is intended to over-ride the prefix names that t... official addon names IF, -a is selected (and no $PBOPREFIX$ detected).
Note that there is no provision for
), the prefix is accounted for in two ways
1) a $PBOPREFIX$ file is added to the output.\\
A $PBOPREFIX$ file if detected in the pbo itself, is NEVER extracted.\\
2) t
