CPP File Format: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
(One intermediate revision by the same user not shown)
Line 5: Line 5:
The binarised (raPified) equivalent of any .cpp file is .bin.
The binarised (raPified) equivalent of any .cpp file is .bin.


There are currently three cpp/bin files used by bis.
There are currently several cpp/bin files used by bis.


*[[Config.cpp/bin File Format|Config.cpp/bin]]
*[[Config.cpp/bin File Format|Config.cpp/bin]]
*[[Mod.cpp/bin File Format|Mod.cpp/bin]]
*[[Mod.cpp/bin File Format|Mod.cpp/bin]]
*[[Product.cpp/bin]]
*[[Product.cpp/bin File Format|Product.cpp/bin]]
*[[Resource.cpp/bin]] // OFP only


In all circumstances, a .cpp, if present in the same folder, takes precedence. (the .bin is ignored).
In all circumstances, a .cpp, if present in the same folder, takes precedence. (the .bin is ignored).


[[Category:BIS_File_Formats]]
[[Category:BIS_File_Formats]]

Revision as of 11:48, 7 July 2011

Template:unsupported-doc

FileExtension .cpp is a generic identifier that indicates the contents contain pre-raPified text and can be raPified (binarised). This is by-convention-only. The actual contents could be binarised already. The engine doesn't care.

The binarised (raPified) equivalent of any .cpp file is .bin.

There are currently several cpp/bin files used by bis.

In all circumstances, a .cpp, if present in the same folder, takes precedence. (the .bin is ignored).