Opened 11 years ago

Last modified 10 years ago

#77 confirmed task

Identify purpose of unknown parts of Army Builder .ab files

Reported by: ibboard Owned by:
Priority: major Milestone: Army Builder file support plugin 0.2
Component: ArmyBuilder-Support-API Version: Unknown or N/A
Keywords: Cc:
Blocked By: Blocking:

Description

Some parts of the .ab files are either stored as "unknowns" or are given a guessed value. Where possible we need to identify what the values actually are (since they must do something) and update the API.

Change History (6)

comment:1 Changed 11 years ago by ibboard

(In r107) Re #77 - Identify fields in .ab files

  • Rename "UnknownNumber" to "UniqueID" based on data in "update XML" files

comment:2 Changed 11 years ago by ibboard

Owner: ibboard deleted

Remove owner so that the team can more easily see bugs. Using default owners seems good at first but is bad practice when a team can be working on any part of the project.

comment:3 Changed 10 years ago by ibboard

Milestone: → Army Builder plugin 0.1

comment:4 Changed 10 years ago by ibboard

Milestone: Army Builder plugin 0.1 → Army Builder plugin 0.2

Move .ab file tickets to v0.2 to leave pre-extracted file handling in v0.1

comment:5 Changed 10 years ago by ibboard

Status: new → confirmed

Move tickets to new "confirmed" status to show that they've been checked

comment:6 Changed 10 years ago by ibboard

released: → no
Version: → Unknown or N/A

All "first bytes" seen appear to be identical and may relate to compression and decompression (4 bytes each), if the ​brochure provides an accurate structure.

All "end bytes" seem to start 00 00 and end 00 08, which could also be constants.

Somewhere in there each file should have a crc32 number (middle bytes or mid-chunk of end bytes?)

Note: See TracTickets for help on using tickets.