PBOPREFIX: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
Line 36: Line 36:
  myMod\myAddon
  myMod\myAddon


== Benefits ==


$PBOPREFIX$ is used by the following 3rd party tools.
The namespace is saved as part of the PBO file itself.<br>
BinPBO does not expose the namespace. It is set in the app settings.<br>
BinBPO requires a two layer subfolder structure to work.<br>
 
The following 3rd party tools allow and require a namespace definition in the $PBOPREFIX$ file.


* [http://dev-heaven.net/projects/list_files/mikero-pbodll MakePbo]
* [http://dev-heaven.net/projects/list_files/mikero-pbodll MakePbo]
Line 44: Line 47:
* [http://www.kegetys.net/arma cpbo]
* [http://www.kegetys.net/arma cpbo]


BinBPO requires a two layer subfolder structure to work.<br>
 
== Benefits ==


You can name your PBO file anyway you like it, like adding a version tag. <br>
You can name your PBO file anyway you like it, like adding a version tag. <br>

Revision as of 14:18, 11 January 2010

$PBOPREFIX$

$PBOPREFIX$ is the name of a text file that sits in the root folder of an addon.

.\myAddon\$PBOPREFIX$

It has no file extension.

File format

The file contains only a namespace definition. A namespace is practically a path definition.

Examples:

myAddon
myMod\myAddon
x\myMod\addons\myAddon
  • It only contains one line.
  • There is no new line at the end of line one.
  • There is no whitespace before or after the text.

Background

Mod development happens on the p drive.
It is good design to use your own namespace, aka subfolder, for your development work.
The main reason is to keep your workspace clean and to avoid conflicts with other addons.

The folder structure you define translates into the namespace.

p:\myMod\myAddon

results in the namespace

myMod\myAddon


The namespace is saved as part of the PBO file itself.
BinPBO does not expose the namespace. It is set in the app settings.
BinBPO requires a two layer subfolder structure to work.

The following 3rd party tools allow and require a namespace definition in the $PBOPREFIX$ file.


Benefits

You can name your PBO file anyway you like it, like adding a version tag.
At the same time the internal path structure remains the same as defined by the PBOPREFIX file.

Further reading