Skip to content

BFHP / HPFS · map containers

File volume identified by HPFS, used in saved maps and content packs. Some files have an LZIS wrapper.

Documented edition: Imperivm HD · Partial documentation

BFHP is the container file; the file volume is identified by the ASCII signature HPFS. It is a different format from PAK.

A saved map combines metadata, objects and terrain grids with other game-context files. It should therefore not be treated as a single XML file or terrain image.

  • HPFS at the start identifies a volume without that compression wrapper.
  • LZIS at the start requires interpreting the compressed stream first, then identifying its decoded logical contents.
  • The library Packs/RandomMapSettlements.bfhp is a documented example of LZIS containing an HPFS volume.

This tree describes files observed in editor-saved maps; it is not a universal list of required files. The volume root can also contain game.xml, env.42, itemsCustom.xml and player0.xml through player15.xml.

Related pages describe map.xml, map.obj.xml and .grid layers separately.

Maps/1/
map.xml
map.obj.xml
Terrain.terrain.grid
Terrain.height.grid
Terrain.light.grid
Terrain.trans.grid
Terrain.decor.grid
Terrain.pass.grid
Notes.xml
warehouse.rle
Sequences/sequences.xml
  • Identify the actual signature before selecting an extraction tool.
  • Work on a copy and preserve both the folder hierarchy and the files associated with the map.
  • Distinguish the volume holding the files from the individual formats inside it.
  • Verify extraction, editing and saving separately; the ability to read a volume does not establish that it can be repacked correctly.

This entry does not provide a complete HPFS directory, sector-allocation or writing specification. It does not assume equivalence with .mmp or compatibility across all game editions.

Editor saves can retain free sectors containing earlier data. Extracting accessible files and copying every byte of the volume are different operations.

Suggest a better description

Write how you would explain this entry. Your proposal will be held in a private inbox for review.

Controller: José Luis de la Torre Reyes. Proposals are processed to review documentation improvements on the basis of legitimate interests. You can request access, correction, erasure or object by writing to seluedita@gmail.com. Opening this form uses a first-party security cookie for one hour. Submitting stores the proposal and an IP-derived security identifier in the private inbox; omitting your name does not make the submission technically anonymous. Privacy information · Cookies and browser storage.

0 / 4000

Proposals are not published automatically. Do not include personal information in your description.