PBO File Format - Revision history

Lou Montana: Text replacement - "\[\[Category:BIS( |_)File( |_)Formats\]\]" to "Category:Real Virtuality File Formats"

2025-05-08T11:27:12Z

Text replacement - "\[\[Category:BIS( |_)File( |_)Formats\]\]" to "Category:Real Virtuality File Formats"

← Older revision		Revision as of 13:27, 8 May 2025
Line 293:		Line 293:


	[[Category:~~BIS~~ File Formats]]		[[Category:Real Virtuality File Formats]]

Lou Montana: Add arma3pbo link (Python)

2024-04-20T09:24:31Z

Add arma3pbo link (Python)

← Older revision		Revision as of 11:24, 20 April 2024
Line 278:		Line 278:
	* yapbol: {{Link\|https://github.com/overfl0/yapbol}}		* yapbol: {{Link\|https://github.com/overfl0/yapbol}}
	* pbo-fuse: {{Link\|https://github.com/Dahlgren/python-pbo-fuse/blob/master/pbo.py}}		* pbo-fuse: {{Link\|https://github.com/Dahlgren/python-pbo-fuse/blob/master/pbo.py}}
			* arma3pbo: {{Link\|https://github.com/danielgran/arma3pbo}}

	=== Rust ===		=== Rust ===

Lou Montana: Some wiki formatting

2023-09-10T15:55:21Z

Some wiki formatting

← Older revision		Revision as of 17:55, 10 September 2023
Line 4:		Line 4:

	The engine will internally expand any '''*.pbo''' back out to its original, tree-folder, form.		The engine will internally expand any '''*.pbo''' back out to its original, tree-folder, form.

	==== Pbo .ext types ====		==== Pbo .ext types ====

	generically called 'pbo' there are in fact different extension names employed, dependent on the engine being used. In all cases, the contents ultimately are identical to pbos.		generically called 'pbo' there are in fact different extension names employed, dependent on the engine being used. In all cases, the contents ultimately are identical to pbos.
	*ifa: A World War2 mod hard wired to only accept ifa files.		* ifa: A World War2 mod hard wired to only accept ifa files.
	*ebo: ~~Used~~ by ~~vbs initially~~, ~~and bis later~~, to encrypt the contents of a pbo and call it a different extension.		* ebo: initially used by VBS, then by Arma, to encrypt the contents of a pbo and call it a different extension.
	*xbo: Used by vbsLite encrypt with a different algorithm to above.		* xbo: Used by vbsLite encrypt with a different algorithm to above.
	** the encryption method used for vbslite UK and vbslite US is different.		** the encryption method used for vbslite UK and vbslite US is different.

Line 18:		Line 18:
	=== Compression ===		=== Compression ===

	In addition to simply packaging all files and folders in a tree into a single file, some, all, or none of the files within can be compressed using Apple's method of LZSS compression. Which type of files are compressed is ''entirely'' optional. Ones that won't benefit normally are not and some files in the Arma engines cannot be because bis forgot they had this code. The intent behind compression '''was''' for internet use and, in the 'good old days', simply to reduce hard disk storage requirements. The ''actual'' use of compression is becoming less 'popular' as it does represent a small load on the engine. Operation Flashpoint: Elite cannot work with ''compressed .pbo'' files - see [[#{{ofpe}} PBO\|Elite PBO]]s.		In addition to simply packaging all files and folders in a tree into a single file, some, all, or none of the files within can be compressed using Apple's method of LZSS compression.
			Which type of files are compressed is ''entirely'' optional. Ones that won't benefit normally are not and some files in the Arma engines cannot be because bis forgot they had this code.
			The intent behind compression '''was''' for internet use and, in the 'good old days', simply to reduce hard disk storage requirements.
			The ''actual'' use of compression is becoming less 'popular' as it does represent a small load on the engine. Operation Flashpoint: Elite cannot work with ''compressed .pbo'' files - see [[#{{ofpe}} PBO\|Elite PBO]]s.

	=== PboTypes ===		=== PboTypes ===

	==== Mission Versus Addon ====		==== Mission Versus Addon ====
	Across all engines there are two distinct types of pbo.		Across all engines there are two distinct types of pbo.
Line 27:		Line 31:

	==== pbo engine differences ====		==== pbo engine differences ====
	*Cold War Crisis: the very first in the series (disregarding the 'proof of concept' release a year earlier) has no pboProperties header and no checksums. It does however form the core of all other engines. It's format has never been altered		* Cold War Crisis: the very first in the series (disregarding the 'proof of concept' release a year earlier) has no pboProperties header and no checksums. It does however form the core of all other engines. It's format has never been altered
	*Resistance: ~~Added~~ a Properties header as the first 'entry' of the pbo.		* Resistance: added a Properties header as the first 'entry' of the pbo.
	*Vbs1: same as Resistance (but encrypted).		* Vbs1: same as Resistance (but encrypted).
	*Xbox Elite: ~~Added~~ a 0 plus 4 byte checksum to end of file.		* Xbox Elite: added a 0 plus 4 byte checksum to end of file.
	*Arma: ~~Changed elite~~'s checksum to a 0 plus 20 byte sha key to end of file.		* Arma: changed Elite's checksum to a 0 plus 20 byte sha key to end of file.
	*VBS2: same as ~~arma~~ (but encrypted)		* VBS2: same as Arma (but encrypted)
	*Dayz: same as ~~arma~~		* Dayz: same as Arma

	Note also that in almost all cases both the properties header and/or the sha key are optional.		Note also that in almost all cases both the properties header and/or the sha key are optional.


	== Main format ==		== Main format ==
Line 48:		Line 53:
	Because entries and data are contiguous, there is no need for an offset to the 'next' file. <u>Every</u> file, even zero-length ones, are recorded in the header.		Because entries and data are contiguous, there is no need for an offset to the 'next' file. <u>Every</u> file, even zero-length ones, are recorded in the header.

	However, note that there is no provision for, and no ability to, store empty folders. Folders as such are indicated simply by being part of the filename. There are no, folder entries, and consequently, empty folders, cannot be included in a .pbo because there is no filename associated with them. Put another way, an empty folder, if it could be stored (and it can't), would appear to be an empty filename when dePbo'd.		However, note that there is no provision for, and no ability to, store empty folders. Folders as such are indicated simply by being part of the filename.
			There are no, folder entries, and consequently, empty folders, cannot be included in a .pbo because there is no filename associated with them.
			Put another way, an empty folder, if it could be stored (and it can't), would appear to be an empty filename when dePbo'd.

	The last header 'entry' is filled with zeroes. The next byte is the beginning of the data block.		The last header 'entry' is filled with zeroes. The next byte is the beginning of the data block.
Line 137:		Line 144:
	engine="arma3"		engine="arma3"
	author=I am famous"		author=I am famous"
	anything= else that takes your fancy		anything=else that takes your fancy
	</syntaxhighlight>		</syntaxhighlight>

Line 246:		Line 253:
	== Bibliography ==		== Bibliography ==

	* DosTools: http://dev-heaven.net/projects/list_files/mikero-pbodll		* DosTools: {{Link\|http://dev-heaven.net/projects/list_files/mikero-pbodll}}
	* cpbo: http://www.kegetys.net/arma/		* cpbo: {{Link\|http://www.kegetys.net/arma/}}


Line 254:		Line 261:
	=== C ===		=== C ===

	* JAPM: https://github.com/RaJiska/JAPM		* JAPM: {{Link\|https://github.com/RaJiska/JAPM}}
	* armake: https://github.com/KoffeinFlummi/armake		* armake: {{Link\|https://github.com/KoffeinFlummi/armake}}
	* libpbo: https://github.com/Learath2/libpbo		* libpbo: {{Link\|https://github.com/Learath2/libpbo}}

	=== C++ ===		=== C++ ===

	* libpbo: https://github.com/StidOfficial/libpbo		* libpbo: {{Link\|https://github.com/StidOfficial/libpbo}}

	=== C# ===		=== C# ===

	* SwiftPbo: https://github.com/headswe/SwiftPbo		* SwiftPbo: {{Link\|https://github.com/headswe/SwiftPbo}}
	* PboSharp: https://github.com/Shix/PBOSharp		* PboSharp: {{Link\|https://github.com/Shix/PBOSharp}}

	=== Python ===		=== Python ===

	* yapbol: https://github.com/overfl0/yapbol ~~<br>~~		* yapbol: {{Link\|https://github.com/overfl0/yapbol}}
	* pbo-fuse: https://github.com/Dahlgren/python-pbo-fuse/blob/master/pbo.py		* pbo-fuse: {{Link\|https://github.com/Dahlgren/python-pbo-fuse/blob/master/pbo.py}}

	=== Rust ===		=== Rust ===

	* armake2: https://github.com/KoffeinFlummi/armake2		* armake2: {{Link\|https://github.com/KoffeinFlummi/armake2}}

	=== Java ===		=== Java ===

	* ArmaFiles: https://github.com/Krzmbrzl/ArmaFiles		* ArmaFiles: {{Link\|https://github.com/Krzmbrzl/ArmaFiles}}

	=== JavaScript ===		=== JavaScript ===

	* Pbo.js: https://github.com/eelislynne/pbo.js		* Pbo.js: {{Link\|https://github.com/eelislynne/pbo.js}}


	[[Category:BIS File Formats]]		[[Category:BIS File Formats]]

Lou Montana: Fix Wikipedia link

2023-02-24T00:11:00Z

Fix Wikipedia link

← Older revision		Revision as of 02:11, 24 February 2023
Line 113:		Line 113:
	There can be as many contiguos paired Strings as, well, as many as, a piece of string!		There can be as many contiguos paired Strings as, well, as many as, a piece of string!

	The '''LAST''' (or only!) String is a zero length {{~~Wikipedia~~\|Null-~~terminated string~~\|ASCIIZ}} string (eg. '\0').		The '''LAST''' (or only!) String is a zero length {{Link\|https://en.wikipedia.org/wiki/Null-terminated_string\|ASCIIZ}} string (eg. '\0').

	==== {{ofpr}} PBO ====		==== {{ofpr}} PBO ====

Veteran29: add armake2 to pbo tools, fix python tools not being a list

2022-06-07T21:10:10Z

add armake2 to pbo tools, fix python tools not being a list

← Older revision		Revision as of 23:10, 7 June 2022
Line 269:		Line 269:
	=== Python ===		=== Python ===

	yapbol: https://github.com/overfl0/yapbol <br>		* yapbol: https://github.com/overfl0/yapbol <br>
	pbo-fuse: https://github.com/Dahlgren/python-pbo-fuse/blob/master/pbo.py		* pbo-fuse: https://github.com/Dahlgren/python-pbo-fuse/blob/master/pbo.py

			=== Rust ===

			* armake2: https://github.com/KoffeinFlummi/armake2

	=== Java ===		=== Java ===

R3vo: category

2021-02-25T00:16:59Z

Lou Montana: Text replacement - "{{unsupported-doc}}" to "{{Feature|UnsupportedDoc}}"

2021-02-01T13:55:04Z

Text replacement - "{{unsupported-doc}}" to "{{Feature|UnsupportedDoc}}"

← Older revision		Revision as of 15:55, 1 February 2021
Line 1:		Line 1:
	{{~~unsupported-doc~~}}		{{Feature\|UnsupportedDoc}}
	{{TOC\|side}}		{{TOC\|side}}
	'''PBO''' means "'''p'''acked '''b'''ank '''o'''f files". A '''.pbo''' is identical in purpose to a zip or rar. It is a container for folder(s) and file(s).		'''PBO''' means "'''p'''acked '''b'''ank '''o'''f files". A '''.pbo''' is identical in purpose to a zip or rar. It is a container for folder(s) and file(s).

Lou Montana: Text replacement - " (={2,})([^ = ])(.)([^ = ])(={2,}) " to " $1 $2$3$4 $5 "

2021-01-31T18:12:01Z

Text replacement - " (={2,})([^ = ])(.*)([^ = ])(={2,}) * " to " $1 $2$3$4 $5 "

← Older revision		Revision as of 20:12, 31 January 2021
Line 4:		Line 4:

	The engine will internally expand any '''*.pbo''' back out to its original, tree-folder, form.		The engine will internally expand any '''*.pbo''' back out to its original, tree-folder, form.
	====Pbo .ext types====		==== Pbo .ext types ====

	generically called 'pbo' there are in fact different extension names employed, dependent on the engine being used. In all cases, the contents ultimately are identical to pbos.		generically called 'pbo' there are in fact different extension names employed, dependent on the engine being used. In all cases, the contents ultimately are identical to pbos.
Line 21:		Line 21:

	=== PboTypes ===		=== PboTypes ===
	====Mission Versus Addon====		==== Mission Versus Addon ====
	Across all engines there are two distinct types of pbo.		Across all engines there are two distinct types of pbo.
	* Mission pbos do not contain config.cpps and live in a mission folder (be it campaign, single, or multiplayer). They have no use for a pboPrefix, nor a Properties header.		* Mission pbos do not contain config.cpps and live in a mission folder (be it campaign, single, or multiplayer). They have no use for a pboPrefix, nor a Properties header.
	* Addon pbos contain a config.cpp/bin which at-the-least identifies the addon name, and, with the exception of the initial cwc engine, rely on a pbo properties header. They live in an addons\ folder.		* Addon pbos contain a config.cpp/bin which at-the-least identifies the addon name, and, with the exception of the initial cwc engine, rely on a pbo properties header. They live in an addons\ folder.

	====pbo engine differences====		==== pbo engine differences ====
	*Cold War Crisis: the very first in the series (disregarding the 'proof of concept' release a year earlier) has no pboProperties header and no checksums. It does however form the core of all other engines. It's format has never been altered		*Cold War Crisis: the very first in the series (disregarding the 'proof of concept' release a year earlier) has no pboProperties header and no checksums. It does however form the core of all other engines. It's format has never been altered
	*Resistance: Added a Properties header as the first 'entry' of the pbo.		*Resistance: Added a Properties header as the first 'entry' of the pbo.

R3vo: Text replacement - "aren't" to "are not"

2021-01-18T00:54:49Z

Text replacement - "aren't" to "are not"

← Older revision		Revision as of 02:54, 18 January 2021
Line 18:		Line 18:
	=== Compression ===		=== Compression ===

	In addition to simply packaging all files and folders in a tree into a single file, some, all, or none of the files within can be compressed using Apple's method of LZSS compression. Which type of files are compressed is ''entirely'' optional. Ones that won't benefit normally ~~aren't~~ and some files in the Arma engines cannot be because bis forgot they had this code. The intent behind compression '''was''' for internet use and, in the 'good old days', simply to reduce hard disk storage requirements. The ''actual'' use of compression is becoming less 'popular' as it does represent a small load on the engine. Operation Flashpoint: Elite cannot work with ''compressed .pbo'' files - see [[#{{ofpe}} PBO\|Elite PBO]]s.		In addition to simply packaging all files and folders in a tree into a single file, some, all, or none of the files within can be compressed using Apple's method of LZSS compression. Which type of files are compressed is ''entirely'' optional. Ones that won't benefit normally are not and some files in the Arma engines cannot be because bis forgot they had this code. The intent behind compression '''was''' for internet use and, in the 'good old days', simply to reduce hard disk storage requirements. The ''actual'' use of compression is becoming less 'popular' as it does represent a small load on the engine. Operation Flashpoint: Elite cannot work with ''compressed .pbo'' files - see [[#{{ofpe}} PBO\|Elite PBO]]s.

	=== PboTypes ===		=== PboTypes ===

Lou Montana: Text replacement - "\[\[[Cc]ategory:ArmA:[ _]?([^|]+)\]\]" to "{{GameCategory|arma1|$1}}"

2021-01-06T13:41:22Z

Text replacement - "\[\[[Cc]ategory:ArmA:[ _]?([^|]+)\]\]" to "{{GameCategory|arma1|$1}}"

← Older revision		Revision as of 15:41, 6 January 2021
Line 284:		Line 284:
	{{GameCategory\|ofpe\|Editing}}		{{GameCategory\|ofpe\|Editing}}
	{{GameCategory\|ofp\| Missions}}		{{GameCategory\|ofp\| Missions}}
	~~[[Category:ArmA:~~ File Formats]]		{{GameCategory\|arma1\| File Formats}}
	[[Category:BIS File Formats]]		[[Category:BIS File Formats]]

← Older revision		Revision as of 02:16, 25 February 2021
Line 280:		Line 280:
	* Pbo.js: https://github.com/eelislynne/pbo.js		* Pbo.js: https://github.com/eelislynne/pbo.js


	~~{{GameCategory\|ofp\| Editing}}~~
	~~{{GameCategory\|ofpe\|Editing}}~~
	~~{{GameCategory\|ofp\| Missions}}~~
	~~{{GameCategory\|arma1\| File Formats}}~~
	[[Category:BIS File Formats]]		[[Category:BIS File Formats]]