Updated Classic BlockDB draft (markdown)

Unkie 2016-04-25 16:40:55 +10:00
parent 63a2f6cd7f
commit 7a8a095f33

@ -1,11 +1,11 @@
The Classic BlockDB format is relatively simple, with the format consisting of a sequence of 16 byte blocks.<br/> The Classic BlockDB format is relatively simple, with the format just consisting of a sequence of 16 byte blocks.<br/>
The blocks are in the order: _BlockDB header_, then _BlockDB metadata_, then a variable number of _BlockDB entry_. The blocks are in the order: _BlockDB header_, then _BlockDB metadata_, then a variable number of _BlockDB entry_.
##### BlockDB header block ##### BlockDB header block
``` ```
4 | Format identifier "cbdb" 4 | Format identifier "cbdb"
1 | Format version, currently '1' 1 | Format version, currently '1'
1 | Years offset (unsigned). Reference point = first second of year (1970 + offset) 1 | Years offset (unsigned). Reference point = 1st second of year (1970 + offset)
2 | Width of the map 2 | Width of the map
2 | Height of the map (vertical) 2 | Height of the map (vertical)
2 | Length of the map 2 | Length of the map
@ -158,7 +158,7 @@ namespace ClassicBlockDB {
// bit 0 set: old block is a physics block, not an ext tile. // bit 0 set: old block is a physics block, not an ext tile.
// bit 1 set: new block is a physics block, not an ext tile. // bit 1 set: new block is a physics block, not an ext tile.
// TODO: should we be using uint16 bitflags for context, with 4 bits leftover for the software? // TODO: 12 bits for context, with 4 bits leftover for the software?
public const int Size = 16; public const int Size = 16;
} }