Skip to content

Documentation versions

BGIN formats and version labels ​

The editor offers ~0.0.2, ~1.6.0, ~3.7.0 and ~5.8.0 modes. These identify BGIN wire formats represented by Asphalt 8 samples from around the release of those game versions. They are not editor versions or a required game version that every input file must match. The ~ marks an approximate reference point.

Choosing a mode ​

Opening a file detects its mode from the BGIN structure. The filename extension, shared signature or APK version alone is insufficient. The detected mode appears at the top. Normal Save and Save As preserve it. New files select a mode explicitly; use the converter to change an existing file's mode. Changing format in JSON manually is not a substitute for conversion.

LabelFormat represented
~0.0.2Early literal type/property names; verified against nine supplied BGIN files from June 2013.
~1.6.0Hashed names and the earlier directory, verified against A8 1.6.0 resources.
~3.7.0Extended two-table directory found in the studied A8 3.7.0 resources.
~5.8.0Changed property encoding, additional values and animation color channels found in the studied A8 5.8.0 resources.

Portable JSON uses a8-0.0.2, a8-1.6.0, a8-3.7.0 and a8-5.8.0. The identifier travels with the data through export and rebuilding.

Other A8 versions and other games ​

You can try opening BGIN from other Asphalt 8 releases or other games released around the same period. A shared engine may have reused a wire format across several releases. A neighboring release may therefore be detected as ~3.7.0 even though the game's version number is different.

This is an opportunity to test, not a verified compatibility range. Formats may evolve independently across games, platforms and distribution channels. The editor accepts the actual structure of the file. Ambiguous formats, unsupported records and inconsistent directories fail explicitly; unknown data must not be dropped silently to make opening or saving succeed.

Opening successfully does not establish compatibility with another game. Object types, properties, resources and engine behavior may differ too. Work on a copy first, then test the result in the target game.

Coverage checked in 0.6.3 ​

Supplied setFiles with independent rebuilding checks
Early ~0.0.29 supplied files
~1.6.0Original main A8 1.6.0 set
~3.7.070 of 74 files
~5.8.0, main GUI85 of 96 files
~5.8.0, APK minigame10 of 13 files

The remaining supplied 3.7.0 and 5.8.0 files fail explicitly: special second-table records are unsupported, and two 3.7.0 files have inconsistent directories. This is partial corpus coverage, not complete support for every game version. Unknown names in supported records are preserved as #1234ABCD; additional property values and animation color channels are preserved too. The editor does not invent semantics for unknown keys.

File format, resources and preview ​

These are separate compatibility layers:

  • The codec determines whether the BGIN wire encoding can be read and saved.
  • The converter checks whether the target format can represent the data.
  • Images and fonts come from matching game resources.
  • Preview uses a supported layout model rather than running the game.

New 5.8.0 property variants and color channels survive saving, but their selection and newer engine behavior are not reproduced by preview yet. Converting BGIN does not give an older engine support for ETC2/ASTC or LZ4/Zstd envelopes. Texture conversion is a separate operation. Loading modified newer resources in the game has not been tested.