(which you have if you have traveled)Īct IV only has 3 quests, so the struct has 6 empty bytes here.

Set to 1 if you have been introduced to Act IV. Set to 1 if you have been introduced to Hratli. Set to 1 if you have traveled to Act III. Set to 1 if you have been introduced to Jerhyn. Set to 1 if you have been introduced to Warriv in Act I. The offset is the offset into the quest struct. This structure repeats it self 3 times, once for Normal, Nightmare and Hell. Prison of Ice is the only quest I bothered to implement, because I needed to know if the character has increased resistances from the scroll or not. For example if you've consumed the Scroll of Resistance from the quest 'Prison of Ice' or not.

Each quest has a lot of unique bits set depending on different milestones of the quest. Header OffsetĪ quest is 2 byte long, I've created a general quest struct that holds the most important data of a quest, if it's completed or not. The quests struct is 298 byte section that describes all quests in the game but also contains data about act traveling and NPC introductions. If no skill is assigned the value is 0x00. Assigned skillsĪssigned skills section is a an array of 16 skill ids, each a 4 byte integer (uint32). Last played is saved as a unit32 unix timestamp e.g 1495882861. Classic ValueĬharacter class is a byte where different values represent a class.

The value is incremented every time you kill an act boss. Still haven't figured them all out, but here's the most important ones. The name can be 16 characters long, and a name that's shorter will have padded 0x00's behind the name until we reach 16 bytes.Ĭharacter status is a byte where different bits will be set, depending on the status of the character. OffsetĬharacter names are storted as a byte which will contain the name, one letter per byte. The header is 765 byte long struct containing most of the character meta data.

Character file may be bad diablo 2