BIN (2007): Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
=Overview= | =Overview= | ||
This file is used for storing parameters and strings in pre-[[Dragon Engine]] games . | This file is used for storing parameters and strings in pre-[[Dragon Engine]] games . | ||
== Technical Information == | |||
<blockquote>0x00 - 4 bytes - Magic (0x20, 0x07, 0x03, 0x19) | |||
0x04 - int32 - Amount of parameters for every entry | |||
0x08 - int32 - Amount of entries in the file | |||
0x10 - start of parameter declaration chunk (size = parameter count * 0x40) | |||
For every parameter declaration: | |||
0x00 - Name of the parameter | |||
0x30 - Parameter type (see list later) | |||
0x34 - Amount of strings or other entries in the parameter if it fits the type | |||
0x38 - Size in bytes this parameter chunk uses up | |||
0x10 + parameter count * 0x40 (After parameter declaration) - Values chunk | |||
For every parameter, in same order as declaration, file lists every value for every entry, according to the type formatting. If there is a “table after last 0x00”, it means there’s a row of bytes (same amount as entries) that sets IDs of lines that appear in every entry.</blockquote> | |||
[[Category:File Formats]] | [[Category:File Formats]] | ||
Revision as of 06:53, 14 December 2022
20070319 .bin format was created on 19th March 2007 by Ryu Ga Gotoku Studio for the first PS3 game in the series - Ryu ga Gotoku: Kenzan! and the date 2007.03.19 is used in header to differentiate these .bin files from others.
Overview
This file is used for storing parameters and strings in pre-Dragon Engine games .
Technical Information
0x00 - 4 bytes - Magic (0x20, 0x07, 0x03, 0x19)
0x04 - int32 - Amount of parameters for every entry
0x08 - int32 - Amount of entries in the file
0x10 - start of parameter declaration chunk (size = parameter count * 0x40) For every parameter declaration:
0x00 - Name of the parameter
0x30 - Parameter type (see list later)
0x34 - Amount of strings or other entries in the parameter if it fits the type
0x38 - Size in bytes this parameter chunk uses up
0x10 + parameter count * 0x40 (After parameter declaration) - Values chunk
For every parameter, in same order as declaration, file lists every value for every entry, according to the type formatting. If there is a “table after last 0x00”, it means there’s a row of bytes (same amount as entries) that sets IDs of lines that appear in every entry.