Added all the TODOs needed up to item code. Modified a bunch of functions to be …

…safer and do more sanity checks

Added all the TODOs needed up to item code. Modified a bunch of functions to be …
…safer and do more sanity checks
Imanol-Mikel Barba Sabariego
1 parent 67c0083b
Showing 23 changed files with 6586 additions and 162 deletions
TODO
d2char.c
d2char.h
d2mercs.c
d2mercs.h
d2quest.c
d2quest.h
d2skills.c
d2skills.h
d2strings.h
d2waypoints.c
d2waypoints.h
docs/d2s_110_format_table.txt
docs/d2s_mercenaries_1.09.html
docs/d2s_notes.txt
docs/d2s_save_file_format_1.13d.html
docs/d2s_save_file_format_1.13d.txt
docs/d2s_save_item_format_1.13d.html
docs/d2s_save_item_format_1.13d.txt
docs/d2s_save_skills_format_1.13d.txt
+// TODO: Error codes
+// TODO: Func documentation
 \ No newline at end of file
@@ -28,19 +28,35 @@ int isHardcore(D2CharHeader* c) {
     return c->charStatus & D2S_CHARSTATUS_HARDCORE;
 }
+void setHardcore(D2CharHeader* c) {
+
+}
+
 int hasDied(D2CharHeader* c) {
     return c->charStatus & D2S_CHARSTATUS_DIED;
 }
+void setDied(D2CharHeader* c) {
+
+}
+
 int isExpansion(D2CharHeader* c) {
     return c->charStatus & D2S_CHARSTATUS_EXPANSION;
 }
+void setExpansion(D2CharHeader* c) {
+
+}
+
 int isLadder(D2CharHeader* c) {
     return c->charStatus & D2S_CHARSTATUS_LADDER;
 }
-int getCurrentAct(D2CharHeader* c) {
+void setLadder(D2CharHeader* c) {
+
+}
+
+D2S_ACT getCurrentAct(D2CharHeader* c) {
     if(isExpansion(c)) {
         return c->charProgress % 5;
     } else {
@@ -135,15 +151,7 @@ size_t getLastPlayed(D2CharHeader* c, char* buf, size_t bufLen) {
     return ret;
 }
-const char* getSkillName(int skillID) {
-    if(skillID > D2S_SKILL_NUMSKILLS) {
-        fprintf(stderr,"libd2char error: skillID %d doesn't exist\n",skillID);
-        return NULL;
-    }
-    return skills[skillID];
-}
-
-int getCurrentDifficulty(D2CharHeader* c) {
+D2S_DIFFICULTY getCurrentDifficulty(D2CharHeader* c) {
     for(int i = D2S_DIFFICULTY_NORMAL; i <= D2S_DIFFICULTY_HELL; ++i) {
         if(c->difficulty[i] & D2S_DIFFICULTY_ACTIVE) {
             return i;
@@ -152,10 +160,18 @@ int getCurrentDifficulty(D2CharHeader* c) {
     return D2S_DIFFICULTY_UNKNOWN;
 }
-const char* getMercName(D2CharHeader* c) {
-    return _getMercName(c->mercenaryType, c->mercenaryNameID);
+int setProgress(D2S_ACT act, D2S_DIFFICULTY difficulty) {
+    // TODO
+    // set c->difficulty and c->progress?
+    return 0;
+}
+
+int getAttribute(D2S_STAT attr) {
+    // TODO
+    return 0;
 }
-const char* getMercType(D2CharHeader* c) {
-    return mercTypes[c->mercenaryType];
+int setAttribute(D2S_STAT attr, unsigned int value) {
+    // TODO
+    return 0;
 }
 \ No newline at end of file
@@ -8,6 +8,7 @@
 #include "d2quest.h"
 #include "d2strings.h"
+#include "d2waypoints.h"
 #define D2S_HEADER_LENGTH 765
 #define D2S_SIGNATURE 0xAA55AA55
@@ -26,21 +27,24 @@
 #define D2S_CHARSTATUS_LADDER 0x40
 #define D2S_DIFFICULTY_ACTIVE 0x80
-#define D2S_DIFFICULTY_NORMAL 0
-#define D2S_DIFFICULTY_NIGHTMARE 1
-#define D2S_DIFFICULTY_HELL 2
-#define D2S_DIFFICULTY_UNKNOWN -1
-enum D2S_VERSION {
+typedef enum D2S_DIFFICULTY {
+    D2S_DIFFICULTY_UNKNOWN = -1,
+    D2S_DIFFICULTY_NORMAL = 0,
+    D2S_DIFFICULTY_NIGHTMARE = 1,
+    D2S_DIFFICULTY_HELL = 2
+} D2S_DIFFICULTY;
+
+typedef enum D2S_VERSION {
     VER_106 = 71,
     VER_107 = 87,
     VER_108XP = 87,
     VER_108 = 89,
     VER_109 = 92,
     VER_110 = 96
-};
+} D2S_VERSION;
-enum D2S_CHARCLASS {
+typedef enum D2S_CHARCLASS {
     D2S_CHARCLASS_AMAZON = 0,
     D2S_CHARCLASS_SORCERESS = 1,
     D2S_CHARCLASS_NECROMANCER = 2,
@@ -48,15 +52,34 @@ enum D2S_CHARCLASS {
     D2S_CHARCLASS_BARBARIAN = 4,
     D2S_CHARCLASS_DRUID = 5,
     D2S_CHARCLASS_ASSASSIN = 6
-};
-
-enum D2S_ACT {
+} D2S_CHARCLASS;
+
+typedef enum D2S_STAT {
+    D2S_STAT_STRENGTH = 0x00,
+    D2S_STAT_ENERGY = 0x01,
+    D2S_STAT_DEXTERITY = 0x02,
+    D2S_STAT_VITALITY = 0x03,
+    D2S_STAT_STATPTS = 0x04,
+    D2S_STAT_SKILLPTS = 0x05,
+    D2S_STAT_LIFE = 0x06,
+    D2S_STAT_MAXLIFE = 0x07,
+    D2S_STAT_MANA = 0x08,
+    D2S_STAT_MAXMANA = 0x09,
+    D2S_STAT_STAMINA = 0x0a,
+    D2S_STAT_MAXSTAMINA = 0x0b,
+    D2S_STAT_LEVEL = 0x0c,
+    D2S_STAT_EXPERIENCE = 0x0d,
+    D2S_STAT_GOLD = 0x0e,
+    D2S_STAT_GOLDSTASH = 0x0f,
+} D2S_STAT;
+
+typedef enum D2S_ACT {
     D2S_ACT1 = 0,
     D2S_ACT2,
     D2S_ACT3,
     D2S_ACT4,
     D2S_ACT5
-};
+} D2S_ACT;
 // TODO: Add file hex offsets for each field
 typedef struct __attribute__((packed)){
@@ -91,12 +114,14 @@ typedef struct __attribute__((packed)){
     uint32_t mercenaryExp;
     uint8_t unknown6[144]; // TODO
     D2QuestData questData;
-    uint8_t waypointData[D2S_WAYPOINTS_LENGTH];
+    D2WaypointsData waypointsData;
     uint8_t unknown7; // TODO. Apparently this is always 0x01
     uint8_t NPCIntroductions[D2S_NPCDATA_LENGTH]; // TODO: Not implemented
+    // TODO Add stats
+    // TODO Add skills
 } D2CharHeader;
-// TODO: All setX functions
+
 // TODO: Load from file.
 // int loadD2CharFromFile(const char* file, D2CharHeader** header, void** data);
@@ -107,12 +132,16 @@ typedef struct __attribute__((packed)){
 uint32_t calcChecksum(D2CharHeader* c, void* charData);
 int checkChecksum(D2CharHeader* c, void* charData);
 int isHardcore(D2CharHeader* c);
+void setHardcore(D2CharHeader* c);
 int hasDied(D2CharHeader* c);
+void setDied(D2CharHeader* c);
 int isExpansion(D2CharHeader* c);
+void setExpansion(D2CharHeader* c);
 int isLadder(D2CharHeader* c);
+void setLadder(D2CharHeader* c);
 // 0 = Act I, 4 = Act V (Expansion)
-int getCurrentAct(D2CharHeader* c);
+D2S_ACT getCurrentAct(D2CharHeader* c);
 int isFemale(D2CharHeader* c);
@@ -122,16 +151,12 @@ const char* getCharacterTitle(D2CharHeader* c);
 // Writes to user-allocated string. Format is default locale's time representation
 size_t getLastPlayed(D2CharHeader* c, char* buf, size_t bufLen);
-// Returns static string from library memory, no need to free
-const char* getSkillName(int skillID);
-
 // 0 = Normal, 2 = Hell
-int getCurrentDifficulty(D2CharHeader* c);
+D2S_DIFFICULTY getCurrentDifficulty(D2CharHeader* c);
-// Returns static string from library memory, no need to free
-const char* getMercName(D2CharHeader* c);
+int setProgress(D2S_ACT act, D2S_DIFFICULTY difficulty);
-// Returns static string from library memory, no need to free
-const char* getMercType(D2CharHeader* c);
+int getAttribute(D2S_STAT attr);
+int setAttribute(D2S_STAT attr, unsigned int value);
 #endif
 \ No newline at end of file
 #include "d2mercs.h"
+#include <stdio.h>
 #include <stdlib.h>
-int _getMercType(int mercID) {
+const char* getMercName(uint16_t mercID, uint16_t mercNameID) {
+    int offset = getMercType(mercID);
+    if(offset == D2S_MERCTYPE_UNKNOWN) {
+        fprintf(stderr,"libd2char error: Unable to retrieve name for mercID %d, mercNameID %d\n",mercID, mercNameID);
+        return NULL;
+    }
+    return mercNames[mercNameID + offset];
+}
+
+D2S_MERCTYPE getMercType(uint16_t mercID) {
     if(mercID >= 0 && mercID <= 5) {
         return D2S_MERCTYPE_ROGUE;
     } else if(mercID >= 6 && mercID <= 14) {
@@ -16,10 +26,14 @@ int _getMercType(int mercID) {
     }
 }
-const char* _getMercName(int mercID, int mercNameID) {
-    int offset = _getMercType(mercID);
-    if(offset == D2S_MERCTYPE_UNKNOWN) {
-        return NULL;
-    }
-    return mercNames[mercNameID + offset];
+D2S_MERCSUBTYPE getMercSubType(uint16_t mercID) {
+    // TODO
+}
+
+D2S_DIFFICULTY getMercDifficulty(uint16_t mercID) {
+    // TODO
+}
+
+int setMerc(D2S_MERCTYPE type, D2S_MERCSUBTYPE subtype, D2S_DIFFICULTY difficulty) {
+    // TODO
 }
 \ No newline at end of file
 #ifndef D2MERCS_H
 #define D2MERCS_H
+#include "d2char.h"
 #include "d2strings.h"
-// TODO: return compound data (type, subtype, difficulty, not just a string)
-
 // The values here are the offsets of each merc's names in the table.
 // i.e: Merc names from pos 41 to 61 are Desert mercs
 //
 // We use these values as offsets later to get the correct name using the relative ID the game provides
-enum D2S_MERCTYPES {
+typedef enum D2S_MERCTYPE {
     D2S_MERCTYPE_UNKNOWN = -1,
     D2S_MERCTYPE_ROGUE = 0,
     D2S_MERCTYPE_DESERT = 41,
     D2S_MERCTYPE_SORCEROR = 62,
     D2S_MERCTYPE_BARBARIAN = 82
-};
+} D2S_MERCTYPE;
-const char* const mercTypes[] = {
-    D2S_MERC_ID_0,
-    D2S_MERC_ID_1,
-    D2S_MERC_ID_2,
-    D2S_MERC_ID_3,
-    D2S_MERC_ID_4,
-    D2S_MERC_ID_5,
-    D2S_MERC_ID_6,
-    D2S_MERC_ID_7,
-    D2S_MERC_ID_8,
-    D2S_MERC_ID_9,
-    D2S_MERC_ID_10,
-    D2S_MERC_ID_11,
-    D2S_MERC_ID_12,
-    D2S_MERC_ID_13,
-    D2S_MERC_ID_14,
-    D2S_MERC_ID_15,
-    D2S_MERC_ID_16,
-    D2S_MERC_ID_17,
-    D2S_MERC_ID_18,
-    D2S_MERC_ID_19,
-    D2S_MERC_ID_20,
-    D2S_MERC_ID_21,
-    D2S_MERC_ID_22,
-    D2S_MERC_ID_23,
-    D2S_MERC_ID_24,
-    D2S_MERC_ID_25,
-    D2S_MERC_ID_26,
-    D2S_MERC_ID_27,
-    D2S_MERC_ID_28,
-    D2S_MERC_ID_29
-};
+typedef enum D2S_MERCSUBTYPE {
+    D2S_MERCSUBTYPE_NONE = 0,
+    D2S_MERCSUBTYPE_FIRE_ARROW = 1,
+    D2S_MERCSUBTYPE_COLD_ARROW = 2,
+    D2S_MERCSUBTYPE_COMBAT = 3,
+    D2S_MERCSUBTYPE_DEFENSIVE = 4,
+    D2S_MERCSUBTYPE_OFFENSIVE = 5,
+    D2S_MERCSUBTYPE_FIRE = 6,
+    D2S_MERCSUBTYPE_COLD = 7,
+    D2S_MERCSUBTYPE_LIGHTNING = 8
+} D2S_MERCSUBTYPE;
 const char* const mercNames[] = {
     D2S_MERC_NAME_0,
@@ -202,7 +180,12 @@ const char* const mercNames[] = {
     D2S_MERC_NAME_148
 };
-int _getMercType(int mercID);
-const char* _getMercName(int mercID, int mercNameID);
+// Returns static string from library memory, no need to free
+const char* getMercName(uint16_t mercID, uint16_t mercNameID);
+
+D2S_MERCTYPE getMercType(uint16_t mercID);
+D2S_MERCSUBTYPE getMercSubType(uint16_t mercID);
+D2S_DIFFICULTY getMercDifficulty(uint16_t mercID);
+int setMerc(D2S_MERCTYPE type, D2S_MERCSUBTYPE subtype, D2S_DIFFICULTY difficulty);
 #endif
 \ No newline at end of file
@@ -3,31 +3,43 @@
 #include <stdio.h>
-void getCheckpointDescriptions(unsigned int quest, const char* *descriptions[16]) {
+const char* getQuestName(D2S_QUEST quest) {
     if(quest > D2S_QUESTDATA_NUMQUESTS) {
         fprintf(stderr,"libd2char error: quest %d doesn't exist\n",quest);
-        return;
+        return NULL;
+    }
+    return questName[quest];
+}
+
+int getCheckpointDescriptions(D2S_QUEST quest, const char* *descriptions[16]) {
+    if(quest > D2S_QUESTDATA_NUMQUESTS) {
+        fprintf(stderr,"libd2char error: quest %d doesn't exist\n",quest);
+        return -1;
     }
     memcpy(descriptions,(&checkpointDescriptions) + (quest * 16 * sizeof(const char*)), 16 * sizeof(const char*));
 }
-uint16_t getQuestStatus(D2QuestData* d, unsigned int quest, unsigned int difficulty) {
+int getQuestStatus(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty, uint16_t* data) {
+    // TODO sanity check diff and quest
     if(quest >= D2S_QUEST_DEN_OF_EVIL && quest <= D2S_QUEST_SISTERS_TO_THE_SLAUGHTER) {
-        return d->quests[difficulty].actData[D2S_ACT1].questCheckpoints[quest];
+        *data = d->quests[difficulty].actData[D2S_ACT1].questCheckpoints[quest];
     } else if(quest >= D2S_QUEST_RADAMENT_LAIR && quest <= D2S_QUEST_SEVEN_TOMBS) {
-        return d->quests[difficulty].actData[D2S_ACT2].questCheckpoints[quest - D2S_QUEST_RADAMENT_LAIR];
+        *data = d->quests[difficulty].actData[D2S_ACT2].questCheckpoints[quest - D2S_QUEST_RADAMENT_LAIR];
     } else if(quest >= D2S_QUEST_GOLDEN_BIRD && quest <= D2S_QUEST_GUARDIAN) {
-        return d->quests[difficulty].actData[D2S_ACT3].questCheckpoints[quest - D2S_QUEST_GOLDEN_BIRD];
+        *data = d->quests[difficulty].actData[D2S_ACT3].questCheckpoints[quest - D2S_QUEST_GOLDEN_BIRD];
     } else if(quest >= D2S_QUEST_FALLEN_ANGEL && quest <= D2S_QUEST_TERROR_END) {
-        return d->quests[difficulty].actData[D2S_ACT4].questCheckpoints[quest - D2S_QUEST_FALLEN_ANGEL];
+        *data = d->quests[difficulty].actData[D2S_ACT4].questCheckpoints[quest - D2S_QUEST_FALLEN_ANGEL];
     } else if(quest >= D2S_QUEST_SIEGE_ON_HARROGATH && quest <= D2S_QUEST_EVE_OF_DESTRUCTION) {
-        return d->quests[difficulty].expansionAct.questCheckpoints[quest - D2S_QUEST_SIEGE_ON_HARROGATH];
+        *data = d->quests[difficulty].expansionAct.questCheckpoints[quest - D2S_QUEST_SIEGE_ON_HARROGATH];
+    } else {
+        fprintf(stderr,"libd2char error: quest %d doesn't exist\n",quest);
+        return -1;
     }
-    fprintf(stderr,"libd2char error: quest %d doesn't exist\n",quest);
     return 0;
 }
-void setQuestStatus(D2QuestData* d, unsigned int quest, unsigned int difficulty, uint16_t questData) {
+int setQuestStatus(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty, uint16_t questData) {
+    // TODO sanity check diff and quest
     if(quest >= D2S_QUEST_DEN_OF_EVIL && quest <= D2S_QUEST_SISTERS_TO_THE_SLAUGHTER) {
         d->quests[difficulty].actData[D2S_ACT1].questCheckpoints[quest] = questData;
     } else if(quest >= D2S_QUEST_RADAMENT_LAIR && quest <= D2S_QUEST_SEVEN_TOMBS) {
@@ -40,51 +52,76 @@ void setQuestStatus(D2QuestData* d, unsigned int quest, unsigned int difficulty,
         d->quests[difficulty].expansionAct.questCheckpoints[quest - D2S_QUEST_SIEGE_ON_HARROGATH] = questData;
     } else {
         fprintf(stderr,"libd2char error: quest %d doesn't exist\n",quest);
+        return -1;
     }
+    return 0;
 }
-int isQuestStarted(D2QuestData* d, unsigned int quest, unsigned int difficulty) {
-    return getQuestStatus(d,quest,difficulty) & D2S_QUEST_STATUS_STARTED;
+int isQuestStarted(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty) {
+    uint16_t data = 0;
+    if(getQuestStatus(d,quest,difficulty,&data) < 0) {
+        return -1;
+    }
+    return data & D2S_QUEST_STATUS_STARTED;
 }
-int isQuestRewardCollected(D2QuestData* d, unsigned int quest, unsigned int difficulty) {
-    return !(getQuestStatus(d,quest,difficulty) & D2S_QUEST_STATUS_REWARD_AVAILABLE);
+int isQuestRewardCollected(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty) {
+    uint16_t data = 0;
+    if(getQuestStatus(d,quest,difficulty,&data) < 0) {
+        return -1;
+    }
+    return data & D2S_QUEST_STATUS_REWARD_AVAILABLE;
 }
-int isQuestCompleted(D2QuestData* d, unsigned int quest, unsigned int difficulty) {
-    return getQuestStatus(d,quest,difficulty) & D2S_QUEST_STATUS_COMPLETED;
+int isQuestCompleted(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty) {
+    uint16_t data = 0;
+    if(getQuestStatus(d,quest,difficulty,&data) < 0) {
+        return -1;
+    }
+    return data & D2S_QUEST_STATUS_COMPLETED;
 }
-void setQuestStarted(D2QuestData* d, unsigned int quest, unsigned int difficulty, int bool) {
+int setQuestStarted(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty, int bool) {
     // To reset the quest, just zero out the whole thing
     // To set as started, just set bit 2 and clear the rest 
-    uint16_t questData = getQuestStatus(d,quest,difficulty);
+    uint16_t questData = 0;
+    if(getQuestStatus(d,quest,difficulty,&questData) < 0) {
+        return -1;
+    }
     if(bool) {
         questData = D2S_QUEST_STATUS_STARTED;
     } else {
         questData = 0x0000;
     }
-    setQuestStatus(d,quest,difficulty,questData);
+    return setQuestStatus(d,quest,difficulty,questData);
 }
-void setQuestRewardCollected(D2QuestData* d, unsigned int quest, unsigned int difficulty, int bool) {
+int setQuestRewardCollected(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty, int bool) {
     // To reset, just clear bit 0 and set bit 1.
     // Do the inverse to set reward as collected (but why whould you tho???)
     if(bool) {
-        setQuestCompleted(d,quest,difficulty,1);
+        return setQuestCompleted(d,quest,difficulty,1);
     } else {
-        setQuestCompleted(d,quest,difficulty,0);
-        uint16_t questData = getQuestStatus(d,quest,difficulty);
+        if(setQuestCompleted(d,quest,difficulty,0) < 0) {
+            return -1;
+        }
+        uint16_t questData;
+        if(getQuestStatus(d,quest,difficulty,&questData) < 0) {
+            return -1;
+        }
         questData |= D2S_QUEST_STATUS_REWARD_AVAILABLE;
-        setQuestStatus(d,quest,difficulty,questData);
+        return setQuestStatus(d,quest,difficulty,questData);
     }
 }
-void setQuestCompleted(D2QuestData* d, unsigned int quest, unsigned int difficulty, int bool) {
+int setQuestCompleted(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty, int bool) {
     // To reset, clear bit 0, bit 12 and bit 13 (13 is kinda optional since it will be cleared by 
     // the game when loading the savegame).
     // To set as completed, just set bit 0 and bit 12 and clear bit 1
-    uint16_t questData = getQuestStatus(d,quest,difficulty);
+    uint16_t questData;
+    if(getQuestStatus(d,quest,difficulty,&questData) < 0) {
+        return -1;
+    }
     if(bool) {
         questData &= ~D2S_QUEST_STATUS_REWARD_AVAILABLE;
         questData |= D2S_QUEST_STATUS_COMPLETED;
@@ -93,10 +130,10 @@ void setQuestCompleted(D2QuestData* d, unsigned int quest, unsigned int difficul
         questData &= ~D2S_QUEST_STATUS_COMPLETED;
         questData &= ~D2S_QUEST_STATUS_SEEN_FINISH_ANIMATION;
     }
-    setQuestStatus(d,quest,difficulty,questData);
+    return setQuestStatus(d,quest,difficulty,questData);
 }
-int getSpecialQuestStatus(D2QuestData* d, unsigned int specialQuestState, unsigned int difficulty) {
+int getSpecialQuestStatus(D2QuestData* d, unsigned int specialQuestState, D2S_DIFFICULTY difficulty) {
     int ret = 0;
     switch(specialQuestState) {
         case D2S_SPECIALQUEST_AKARA_RESPEC:
@@ -106,7 +143,7 @@ int getSpecialQuestStatus(D2QuestData* d, unsigned int specialQuestState, unsign
     return ret;
 }
-void setSpecialQuestStatus(D2QuestData* d, unsigned int specialQuestState, unsigned int difficulty, int bool) {
+int setSpecialQuestStatus(D2QuestData* d, unsigned int specialQuestState, D2S_DIFFICULTY difficulty, int bool) {
     if(difficulty != D2S_DIFFICULTY_NORMAL    || 
        difficulty != D2S_DIFFICULTY_NIGHTMARE || 
        difficulty != D2S_DIFFICULTY_HELL) {
 #ifndef D2QUEST_H
 #define D2QUEST_H
+// Forward declaration
+typedef enum D2S_DIFFICULTY D2S_DIFFICULTY; 
+
 #include <stdint.h>
+#include "d2char.h"
 #include "d2strings.h"
 #define D2S_QUESTDATA_HEADER_LENGTH 4
 #define D2S_QUESTDATA_NUMQUESTS 27
-enum D2S_QUEST {
+typedef enum D2S_QUEST {
     D2S_QUEST_UNKNOWN = -1,
     D2S_QUEST_DEN_OF_EVIL = 0,
     D2S_QUEST_SISTER_BURIAL_GROUNDS,
@@ -37,6 +41,10 @@ enum D2S_QUEST {
     D2S_QUEST_BETRAYAL_OF_HARROGATH,
     D2S_QUEST_RITE_OF_PASSAGE,
     D2S_QUEST_EVE_OF_DESTRUCTION
+} D2S_QUEST;
+
+const char* const questName[] = {
+
 };
 enum D2S_QUEST_STATUS {
@@ -47,9 +55,9 @@ enum D2S_QUEST_STATUS {
     D2S_QUEST_STATUS_JUST_FINISHED = 0x2000
 };
-enum D2S_SPECIALQUEST {
+typedef enum D2S_SPECIALQUEST {
     D2S_SPECIALQUEST_AKARA_RESPEC
-};
+} D2S_SPECIALQUEST;
 const char* const checkpointDescriptions[] = {
     D2S_QUEST_CHECKPOINT_0,
@@ -306,8 +314,6 @@ const char* const checkpointDescriptions[] = {
     D2S_QUEST_CHECKPOINT_251,
     D2S_QUEST_CHECKPOINT_252,
     D2S_QUEST_CHECKPOINT_253,
-    D2S_QUEST_CHECKPOINT_254,
-    D2S_QUEST_CHECKPOINT_255,
     D2S_QUEST_CHECKPOINT_256,
     D2S_QUEST_CHECKPOINT_257,
     D2S_QUEST_CHECKPOINT_258,
@@ -515,34 +521,35 @@ typedef struct __attribute__((packed)) {
     D2Quests quests[3]; // 1 set for each difficulty
 } D2QuestData;
-// TODO: These functions are completely unsafe, and don't return success
+// Returns static string from library memory, no need to free
+const char* getQuestName(D2S_QUEST quest);
 // Populates `descriptions` with static strings from library memory, no need to free.
 // `descriptions` contains one string for each bit field of the quest's uint16_t data.
 // Empty entries (non-existant or unknown checkpoints) will have NULL value. Be careful!
-void getCheckpointDescriptions(unsigned int quest, const char* *descriptions[16]);
+int getCheckpointDescriptions(D2S_QUEST quest, const char* *descriptions[16]);
 // Returns quest status for the specified quest and act.
-uint16_t getQuestStatus(D2QuestData* d, unsigned int quest, unsigned int difficulty);
-void setQuestStatus(D2QuestData* d, unsigned int quest, unsigned int difficulty, uint16_t questData);
+int getQuestStatus(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty, uint16_t* data);
+int setQuestStatus(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty, uint16_t questData);
-int isQuestStarted(D2QuestData* d, unsigned int quest, unsigned int difficulty);
-int isQuestRewardCollected(D2QuestData* d, unsigned int quest, unsigned int difficulty);
-int isQuestCompleted(D2QuestData* d, unsigned int quest, unsigned int difficulty);
+int isQuestStarted(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty);
+int isQuestRewardCollected(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty);
+int isQuestCompleted(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty);
 // Set bool to 1 to set the status or 0 to remove it
-void setQuestStarted(D2QuestData* d, unsigned int quest, unsigned int difficulty, int bool);
-void setQuestRewardCollected(D2QuestData* d, unsigned int quest, unsigned int difficulty, int bool);
+int setQuestStarted(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty, int bool);
+int setQuestRewardCollected(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty, int bool);
 // When called to set the request to NOT completed (`bool` = 0), this will NOT set the reward collected status
 // which *may* render the quest unobtainable, this is done in case we may want to further modify the quest state.
 // If you want to mark the quest as not completed just to get the reward, please use `setQuestRewardCollected(,,0)`
 // instead.
-void setQuestCompleted(D2QuestData* d, unsigned int quest, unsigned int difficulty, int bool);
+int setQuestCompleted(D2QuestData* d, D2S_QUEST quest, D2S_DIFFICULTY difficulty, int bool);
 // Some quests have extra fields outside their quest data that govern certain states of the quest
 // So far, I only know of the respec that Akara offers when clearing Den of Evil
-int getSpecialQuestStatus(D2QuestData* d, unsigned int specialQuestState, unsigned int difficulty);
-void setSpecialQuestStatus(D2QuestData* d, unsigned int specialQuestState, unsigned int difficulty, int bool);
+int getSpecialQuestStatus(D2QuestData* d, D2S_SPECIALQUEST specialQuestState, D2S_DIFFICULTY difficulty);
+int setSpecialQuestStatus(D2QuestData* d, D2S_SPECIALQUEST specialQuestState, D2S_DIFFICULTY difficulty, int bool);
 #endif
 \ No newline at end of file
+#include "d2char.h"
+#include "d2skills.h"
+
+#include <stdio.h>
+#include <stdlib.h>
+
+D2S_CHARCLASS getSkillClass(D2S_SKILL skillID) {
+    // TODO
+}
+
+const char* getSkillName(D2S_SKILL skillID) {
+    if(skillID > D2S_SKILL_NUMSKILLS) {
+        fprintf(stderr,"libd2char error: skillID %d doesn't exist\n",skillID);
+        return NULL;
+    }
+    return skills[skillID];
+}
 \ No newline at end of file
@@ -7,6 +7,9 @@
 #define D2S_SKILL_NUMSKILLS 357
+// TODO skill class trees
+typedef int D2S_SKILL;
+
 const char* const skills[] = {
     D2S_SKILL_0,
     D2S_SKILL_1,
@@ -367,4 +370,8 @@ const char* const skills[] = {
     D2S_SKILL_356
 };
+// Returns static string from library memory, no need to free
+const char* getSkillName(D2S_SKILL skillID);
+D2S_CHARCLASS getSkillClass(D2S_SKILL skillID);
+
 #endif
 \ No newline at end of file
@@ -534,37 +534,6 @@ const char* D2S_CHARPROGRESS_EXPANSION_TIER3_NAME_HARDCORE = &quot;Guardian&quot;;
 #define D2S_MERC_NAME_147 "Bill"
 #define D2S_MERC_NAME_148 "Theodoric"
-#define D2S_MERC_ID_0 "Rogue Scout Fire Arrow [Normal"
-#define D2S_MERC_ID_1 "Rogue Scout Cold Arrow [Normal"
-#define D2S_MERC_ID_2 "Rogue Scout Fire Arrow [Nightmare]"
-#define D2S_MERC_ID_3 "Rogue Scout Cold Arrow [Nightmare]"
-#define D2S_MERC_ID_4 "Rogue Scout Fire Arrow [Hell]"
-#define D2S_MERC_ID_5 "Rogue Scout Cold Arrow [Hell]"
-#define D2S_MERC_ID_6 "Desert Mercenary Combat [Normal]"
-#define D2S_MERC_ID_7 "Desert Mercenary Defensive [Normal]"
-#define D2S_MERC_ID_8 "Desert Mercenary Offensive [Normal]"
-#define D2S_MERC_ID_9 "Desert Mercenary Combat [Nightmare]"
-#define D2S_MERC_ID_10 "Desert Mercenary Defensive [Nightmare]"
-#define D2S_MERC_ID_11 "Desert Mercenary Offensive [Nightmare]"
-#define D2S_MERC_ID_12 "Desert Mercenary Combat [Hell]"
-#define D2S_MERC_ID_13 "Desert Mercenary Defensive [Hell]"
-#define D2S_MERC_ID_14 "Desert Mercenary Offensive [Hell]"
-#define D2S_MERC_ID_15 "Eastern Sorceror Fire Spells [Normal]"
-#define D2S_MERC_ID_16 "Eastern Sorceror Cold Spells [Normal]"
-#define D2S_MERC_ID_17 "Eastern Sorceror Lightning Spells [Normal]"
-#define D2S_MERC_ID_18 "Eastern Sorceror Fire Spells [Nightmare]"
-#define D2S_MERC_ID_19 "Eastern Sorceror Cold Spells [Nightmare]"
-#define D2S_MERC_ID_20 "Eastern Sorceror Lightning Spells [Nightmare]"
-#define D2S_MERC_ID_21 "Eastern Sorceror Fire Spells [Hell]"
-#define D2S_MERC_ID_22 "Eastern Sorceror Cold Spells [Hell]"
-#define D2S_MERC_ID_23 "Eastern Sorceror Lightning Spells [Hell]"
-#define D2S_MERC_ID_24 "Barbarian [Normal]"
-#define D2S_MERC_ID_25 "Barbarian [Normal]"
-#define D2S_MERC_ID_26 "Barbarian [Nightmare]"
-#define D2S_MERC_ID_27 "Barbarian [Nightmare]"
-#define D2S_MERC_ID_28 "Barbarian [Hell]"
-#define D2S_MERC_ID_29 "Barbarian [Hell]"
-
 // Quest checkpoints
 // Note: Some quests don't have many checkpoints, but unfortunately lots of checkpoints are
 // missing here. Documentation is pretty much scarce and I'm afraid we won't be able to find
 #include "d2waypoints.h"
+#include "d2char.h"
-int isWaypointActivated(D2WaypointsData* d, unsigned int waypoint, unsigned int difficulty) {
+int isWaypointActivated(D2WaypointsData* d, D2S_WAYPOINT waypoint, D2S_DIFFICULTY difficulty) {
     if(waypoint > D2S_WAYPOINTSDATA_NUMWAYPOINTS) {
         return -1;
     }
@@ -10,7 +11,7 @@ int isWaypointActivated(D2WaypointsData* d, unsigned int waypoint, unsigned int 
 }
 // TODO: Return success
-void setWaypointActivated(D2WaypointsData* d, unsigned int waypoint, unsigned int difficulty, int activated) {
+void setWaypointActivated(D2WaypointsData* d, D2S_WAYPOINT waypoint, D2S_DIFFICULTY difficulty, int activated) {
     if(waypoint > D2S_WAYPOINTSDATA_NUMWAYPOINTS) {
         return;
     }
 #ifndef D2WAYPOINTS_H
 #define D2WAYPOINTS_H
+// Forward declaration
+typedef enum D2S_DIFFICULTY D2S_DIFFICULTY;
+
 #include <stdint.h>
 #include "d2strings.h"
@@ -9,6 +12,10 @@
 #define D2S_WAYPOINTSDATA_LENGTH 5
 #define D2S_WAYPOINTSDATA_NUMWAYPOINTS 39
+typedef enum D2S_WAYPOINT {
+asd
+} D2S_WAYPOINT;
+
 const char* const waypoints[] = {
     D2S_WAYPOINT_0,
     D2S_WAYPOINT_1,
@@ -64,7 +71,7 @@ typedef struct __attribute__((packed)) {
     D2Waypoints waypoints[3]; // 1 set for each difficulty
 } D2WaypointsData;
-int isWaypointActivated(D2WaypointsData* d, unsigned int waypoint, unsigned int difficulty);
-void setWaypointActivated(D2WaypointsData* d, unsigned int waypoint, unsigned int difficulty, int activated);
+int isWaypointActivated(D2WaypointsData* d, D2S_WAYPOINT waypoint, D2S_DIFFICULTY difficulty);
+void setWaypointActivated(D2WaypointsData* d, D2S_WAYPOINT waypoint, D2S_DIFFICULTY difficulty, int activated);
 #endif
 \ No newline at end of file
+-------------------------------------------------------------------------------
+originally extracted from here:
+http://www.coreyh.org/diablo-2-files/documentation/d2s_110_format_table.htm
+-------------------------------------------------------------------------------
+
+
+D2S File Format - Version 1.10
+
+type   name              bits      desc                      cond1   condvar1   condval1 cond2  condvar2  condval2 comment
+ASC8   dwMajic           4         File ID                                                                          +0
+DWRD   dwVersion         32        File Version                                                                     +4
+DWRD   dwSize            32        File Size                                                                        +8
+DWRD   dwCRC             32        File CRC                                                                         +c
+DWRD   dwWeaponSet       32        Weapon Set                                                                       +10
+ASCI   Name              16        Character Name                                                                   +14
+BYTE   charType          8         Character Type                                                                   +24 // 0x40 = ladder 0x20 = expansion 0x10 =? 0x08 = HasDied 0x04 = Hardcore
+                                                                                                                   0x02 = ? 0x01 = new character format
+BYTE   charTitle         8         Character Title                                                                  +25
+WORD   unk1              16        Unknown                                                                          +26 // 00 00
+BYTE   charClass         8         Character Class                                                                  +28
+WORD   unk2              16        Unknown                                                                          +29 // 10 1E
+BYTE   charLevel         8         Level                                                                            +2b
+DWRD   unk3              32        Unknown                                                                          +2c
+DWRD   dwTime            32        Time Stamp                                                                       +30
+DWRD   unk4              32        Unknown                                                                         // FF FF FF FF +34
+DWRD   dwSkillKey[16]    32        Skill Keys                                                                      // No Array support in format !!! +38
+DWRD   dwLeftSkill1      32        Left Skill Weapon Set 1                                                          +78
+DWRD   dwRightSkill1     32        Right Skill Weapon Set 1                                                         +7c
+DWRD   dwLeftSkill2      32        Left Skill Weapon Set 2                                                          +80
+DWRD   dwRightSkill2     32        Right Skill Weapon Set 2                                                         +84
+BYTE   outfit[16]        8         Character Load graphics                                                         // No Array support in format !!! +88
+BYTE   colors[16]        8         Character Load Colors                                                           // No Array support in format !!! +98
+BYTE   Town1             8         Normal Town                                                                     // Only town for last played mode is set
+BYTE   Town2             8         Nightmare Town
+BYTE   Town3             8         Hell Town
+DWRD   dwMapSeed         32        Map Random Seed
+WORD   unk5              16        Unknown                                                                         // 00 00
+BYTE   bMercDead         8         Merc Dead Flag
+BYTE   unk6              8         Unknown
+DWRD   dwMercControl     32        Merc Control seed
+WORD   wMercName         16        Merc Name Index
+WORD   wMercType         16        Merc Type
+DWRD   dwMercExp         32        Merc Experience
+BYTE   unk7[0x90]        8         Unknown                                                                         // No Array support in format !!!
+
+FILE   d2Woo.txt         0         Questinfo Header                                                                // Act/Quest info header
+
+FILE   d2Ws.txt          0         Waypoints                                                                       // waypoints
+
+FILE   d2W4.txt          0         Greetings                                                                       // NPC greeting control
+
+PROP   Stats             0         Player Stats                                                                    // stats read like properties
+
+FILE   d2if.txt          0         Player Skills                                                                   // skills
+
+FILE   itemlist.txt      0         Player Item List
+
+WORD   iCorpses          16        Number of Corpses
+FILE   corpse.txt        iCorpses  Corpse List                                                                     // need to add support for variable 'bits'
+
+ASC8   d2jf              2         Merc List majic                                                                 // jf
+FILE   itemlist.txt      0         Merc Item List                  0 bHasMerc          1
+
+ASC8   d2kf              2         Iron Golem majic                                                                // kf
+BYTE   bHasGolem         8         Iron Golem Flag
+FILE   fields.txt        0         Golem Item                      0 bHasGolem         1
+
+
+
+       //========== corpse.txt                                                                                     // dead body info
+
+BYTE   bodyInfo[12]      8         Corpse Info
+FILE   itemlist.txt      0         Corpse Item List
+
+
+       //========== itemlist.txt                                                                                   // Item record list
+
+ASC8   dwMajic           2         Item List majic                                                                 // JM
+WORD   nItems            16        Number of Items
+FILE   fields.txt        nItems    Item Records
+
+
+
+
+       //========== d2Woo.txt                                                                                      // Act/Quest info header
+
+ASC8   dwMajic           4         Record ID                                                                       // Woo!
+DWRD   dwActs            32        Numer of acts
+WORD   wSize             16        Size in bytes
+
+FILE   d2Act.txt         3*wActs   Quest/Act states
+
+       //========== d2Acts.txt                                                                                     // Act status flags
+
+WORD   wActStart         16        Act Start info
+WORD   wQuestStatus[6]   16        Quest Status
+WORD   wActEnd           16        Act End flags
+
+       //========== d2Ws.txt                                                                                       // waypoints
+
+ASC8   wMajic            2         Record ID                                                                       // ws
+BYTE   unk[6]            8         Unknown
+DWRD   wp[3*6]           32        Waypoint Data
+
+       //========== d2W4.txt                                                                                       // NPC state control
+
+ASC8   wMajic            2         Record ID (0x7701)
+WORD   wSize             16        size of struct
+DWRD   normal[2]         32        Normal
+DWRD   nightmare[2]      32        Nightmare
+DWRD   hell[2]           32        Hell
+DWRD   normal1[2]        32        Normal1
+DWRD   nightmare1[2]     32        Nightmare1
+DWRD   hell1[2]          32        Hell1
+
+
+       //========== d2if.txt                                                                                       // skills
+
+ASC8   wMajic            2         Record ID                                                                       // if
+BYTE   skill_lvls[30]    8         Skill Levels
+
+<html>
+<head>
+   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
+   <meta name="Author" content="Trevin Beattie">
+   <meta name="Description" content="Your character's .d2s file decoded">
+   <meta name="Keywords" content="d2s, Diablo, v1.09, mercenary">
+   <meta name="Classification" content="binary file format">
+   <title>Diablo II v1.09 (English) Mercenary Names</title>
+</head>
+<body>
+
+<h1 align=center>Diablo II (English) Mercenary Names</h1>
+
+<h3 align=center>for Diablo II v1.09 and the Diablo II Expansion
+Set: Lord of Destruction</h3>
+
+<h2 align=center>Rogue Scouts</h2>
+
+<table width="100%" border=0><tr>
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>0</td><td align=center>Aliza</td></tr>
+<tr><td align=center>1</td><td align=center>Amplisa</td></tr>
+<tr><td align=center>2</td><td align=center>Annor</td></tr>
+<tr><td align=center>3</td><td align=center>Abhaya</td></tr>
+<tr><td align=center>4</td><td align=center>Elly</td></tr>
+<tr><td align=center>5</td><td align=center>Paige</td></tr>
+<tr><td align=center>6</td><td align=center>Basanti</td></tr>
+<tr><td align=center>7</td><td align=center>Blaise</td></tr>
+<tr><td align=center>8</td><td align=center>Kyoko</td></tr>
+<tr><td align=center>9</td><td align=center>Klaudia</td></tr>
+<tr><td align=center>10</td><td align=center>Kundri</td></tr>
+<tr><td align=center>11</td><td align=center>Kyle</td></tr>
+<tr><td align=center>12</td><td align=center>Visala</td></tr>
+<tr><td align=center>13</td><td align=center>Elexa</td></tr>
+</table></td>
+
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>14</td><td align=center>Floria</td></tr>
+<tr><td align=center>15</td><td align=center>Fiona</td></tr>
+<tr><td align=center>16</td><td align=center>Gwinni</td></tr>
+<tr><td align=center>17</td><td align=center>Gaile</td></tr>
+<tr><td align=center>18</td><td align=center>Hannah</td></tr>
+<tr><td align=center>19</td><td align=center>Heather</td></tr>
+<tr><td align=center>20</td><td align=center>Iantha</td></tr>
+<tr><td align=center>21</td><td align=center>Diane</td></tr>
+<tr><td align=center>22</td><td align=center>Isolde</td></tr>
+<tr><td align=center>23</td><td align=center>Divo</td></tr>
+<tr><td align=center>24</td><td align=center>Ithera</td></tr>
+<tr><td align=center>25</td><td align=center>Itonya</td></tr>
+<tr><td align=center>26</td><td align=center>Liene</td></tr>
+<tr><td align=center>27</td><td align=center>Maeko</td></tr>
+</table></td>
+
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>28</td><td align=center>Mahala</td></tr>
+<tr><td align=center>29</td><td align=center>Liaza</td></tr>
+<tr><td align=center>30</td><td align=center>Meghan</td></tr>
+<tr><td align=center>31</td><td align=center>Olena</td></tr>
+<tr><td align=center>32</td><td align=center>Oriana</td></tr>
+<tr><td align=center>33</td><td align=center>Ryann</td></tr>
+<tr><td align=center>34</td><td align=center>Rozene</td></tr>
+<tr><td align=center>35</td><td align=center>Raissa</td></tr>
+<tr><td align=center>36</td><td align=center>Sharyn</td></tr>
+<tr><td align=center>37</td><td align=center>Shikha</td></tr>
+<tr><td align=center>38</td><td align=center>Debi</td></tr>
+<tr><td align=center>39</td><td align=center>Tylena</td></tr>
+<tr><td align=center>40</td><td align=center>Wendy</td></tr>
+</table></td>
+</tr></table>
+
+<hr width="50%">
+
+<h2 align=center>Desert Mercenaries</h2>
+
+<table width="100%" border=0><tr>
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>0</td><td align=center>Hazade</td></tr>
+<tr><td align=center>1</td><td align=center>Alhizeer</td></tr>
+<tr><td align=center>2</td><td align=center>Azrael</td></tr>
+<tr><td align=center>3</td><td align=center>Ahsab</td></tr>
+<tr><td align=center>4</td><td align=center>Chalan</td></tr>
+<tr><td align=center>5</td><td align=center>Haseen</td></tr>
+<tr><td align=center>6</td><td align=center>Razan</td></tr>
+</table></td>
+
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>7</td><td align=center>Emilio</td></tr>
+<tr><td align=center>8</td><td align=center>Pratham</td></tr>
+<tr><td align=center>9</td><td align=center>Fazel</td></tr>
+<tr><td align=center>10</td><td align=center>Jemali</td></tr>
+<tr><td align=center>11</td><td align=center>Kasim</td></tr>
+<tr><td align=center>12</td><td align=center>Gulzar</td></tr>
+<tr><td align=center>13</td><td align=center>Mizan</td></tr>
+</table></td>
+
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>14</td><td align=center>Leharas</td></tr>
+<tr><td align=center>15</td><td align=center>Durga</td></tr>
+<tr><td align=center>16</td><td align=center>Neeraj</td></tr>
+<tr><td align=center>17</td><td align=center>Ilzan</td></tr>
+<tr><td align=center>18</td><td align=center>Zanarhi</td></tr>
+<tr><td align=center>19</td><td align=center>Waheed</td></tr>
+<tr><td align=center>20</td><td align=center>Vikhyat</td></tr>
+</table></td>
+</tr></table>
+
+<hr width="50%">
+
+<h2 align=center>Eastern Sorcerors</h2>
+
+<table width="100%" border=0><tr>
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>0</td><td align=center>Jelani</td></tr>
+<tr><td align=center>1</td><td align=center>Barani</td></tr>
+<tr><td align=center>2</td><td align=center>Jabari</td></tr>
+<tr><td align=center>3</td><td align=center>Devak</td></tr>
+<tr><td align=center>4</td><td align=center>Raldin</td></tr>
+<tr><td align=center>5</td><td align=center>Telash</td></tr>
+<tr><td align=center>6</td><td align=center>Ajheed</td></tr>
+</table></td>
+
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>7</td><td align=center>Narphet</td></tr>
+<tr><td align=center>8</td><td align=center>Khaleel</td></tr>
+<tr><td align=center>9</td><td align=center>Phaet</td></tr>
+<tr><td align=center>10</td><td align=center>Geshef</td></tr>
+<tr><td align=center>11</td><td align=center>Vanji</td></tr>
+<tr><td align=center>12</td><td align=center>Haphet</td></tr>
+<tr><td align=center>13</td><td align=center>Thadar</td></tr>
+</table></td>
+
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>14</td><td align=center>Yatiraj</td></tr>
+<tr><td align=center>15</td><td align=center>Rhadge</td></tr>
+<tr><td align=center>16</td><td align=center>Yashied</td></tr>
+<tr><td align=center>17</td><td align=center>Jarulf</td></tr>
+<tr><td align=center>18</td><td align=center>Flux</td></tr>
+<tr><td align=center>19</td><td align=center>Scorch</td></tr>
+</table></td>
+</tr></table>
+
+<hr width="50%">
+
+<h2 align=center>Barbarians</h2>
+
+<table width="100%" border=0><tr>
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>0</td><td align=center>Varaya</td></tr>
+<tr><td align=center>1</td><td align=center>Khan</td></tr>
+<tr><td align=center>2</td><td align=center>Klisk</td></tr>
+<tr><td align=center>3</td><td align=center>Bors</td></tr>
+<tr><td align=center>4</td><td align=center>Brom</td></tr>
+<tr><td align=center>5</td><td align=center>Wiglaf</td></tr>
+<tr><td align=center>6</td><td align=center>Hrothgar</td></tr>
+<tr><td align=center>7</td><td align=center>Scyld</td></tr>
+<tr><td align=center>8</td><td align=center>Healfdane</td></tr>
+<tr><td align=center>9</td><td align=center>Heorogar</td></tr>
+<tr><td align=center>10</td><td align=center>Halgaunt</td></tr>
+<tr><td align=center>11</td><td align=center>Hygelac</td></tr>
+<tr><td align=center>12</td><td align=center>Egtheow</td></tr>
+<tr><td align=center>13</td><td align=center>Bohdan</td></tr>
+<tr><td align=center>14</td><td align=center>Wulfgar</td></tr>
+<tr><td align=center>15</td><td align=center>Hild</td></tr>
+<tr><td align=center>16</td><td align=center>Heatholaf</td></tr>
+</table></td>
+
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>17</td><td align=center>Weder</td></tr>
+<tr><td align=center>18</td><td align=center>Vikhyat</td></tr>
+<tr><td align=center>19</td><td align=center>Unferth</td></tr>
+<tr><td align=center>20</td><td align=center>Sigemund</td></tr>
+<tr><td align=center>21</td><td align=center>Heremod</td></tr>
+<tr><td align=center>22</td><td align=center>Hengest</td></tr>
+<tr><td align=center>23</td><td align=center>Folcwald</td></tr>
+<tr><td align=center>24</td><td align=center>Frisian</td></tr>
+<tr><td align=center>25</td><td align=center>Hnaef</td></tr>
+<tr><td align=center>26</td><td align=center>Guthlaf</td></tr>
+<tr><td align=center>27</td><td align=center>Oslaf</td></tr>
+<tr><td align=center>28</td><td align=center>Yrmenlaf</td></tr>
+<tr><td align=center>29</td><td align=center>Garmund</td></tr>
+<tr><td align=center>30</td><td align=center>Freawaru</td></tr>
+<tr><td align=center>31</td><td align=center>Eadgils</td></tr>
+<tr><td align=center>32</td><td align=center>Onela</td></tr>
+<tr><td align=center>33</td><td align=center>Damien</td></tr>
+</table></td>
+
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>34</td><td align=center>Erfor</td></tr>
+<tr><td align=center>35</td><td align=center>Weohstan</td></tr>
+<tr><td align=center>36</td><td align=center>Wulf</td></tr>
+<tr><td align=center>37</td><td align=center>Bulwye</td></tr>
+<tr><td align=center>38</td><td align=center>Lief</td></tr>
+<tr><td align=center>39</td><td align=center>Magnus</td></tr>
+<tr><td align=center>40</td><td align=center>Klatu</td></tr>
+<tr><td align=center>41</td><td align=center>Drus</td></tr>
+<tr><td align=center>42</td><td align=center>Hoku</td></tr>
+<tr><td align=center>43</td><td align=center>Kord</td></tr>
+<tr><td align=center>44</td><td align=center>Uther</td></tr>
+<tr><td align=center>45</td><td align=center>Ip</td></tr>
+<tr><td align=center>46</td><td align=center>Ulf</td></tr>
+<tr><td align=center>47</td><td align=center>Tharr</td></tr>
+<tr><td align=center>48</td><td align=center>Kaelim</td></tr>
+<tr><td align=center>49</td><td align=center>Ulric</td></tr>
+<tr><td align=center>50</td><td align=center>Alaric</td></tr>
+</table></td>
+
+<td valign=top><table align=center border>
+<tr><th width="30%">Index</th><th width="70%">Name</th></tr>
+<tr><td align=center>51</td><td align=center>Ethelred</td></tr>
+<tr><td align=center>52</td><td align=center>Caden</td></tr>
+<tr><td align=center>53</td><td align=center>Elgifu</td></tr>
+<tr><td align=center>54</td><td align=center>Tostig</td></tr>
+<tr><td align=center>55</td><td align=center>Alcuin</td></tr>
+<tr><td align=center>56</td><td align=center>Emund</td></tr>
+<tr><td align=center>57</td><td align=center>Sigurd</td></tr>
+<tr><td align=center>58</td><td align=center>Gorm</td></tr>
+<tr><td align=center>59</td><td align=center>Hollis</td></tr>
+<tr><td align=center>60</td><td align=center>Ragnar</td></tr>
+<tr><td align=center>61</td><td align=center>Torkel</td></tr>
+<tr><td align=center>62</td><td align=center>Wulfstan</td></tr>
+<tr><td align=center>63</td><td align=center>Alban</td></tr>
+<tr><td align=center>64</td><td align=center>Barloc</td></tr>
+<tr><td align=center>65</td><td align=center>Bill</td></tr>
+<tr><td align=center>66</td><td align=center>Theodoric</td></tr>
+</table></td>
+</tr></table>
+
+<hr width="50%">
+
+<h2 align=center><a name="code">Mercenary Type Codes</a></h2>
+
+<table align=center border>
+<tr><th width="7%">Code</th><th width="33%">Mercenary</th>
+<th width="33%">Attribute</th><th width="27%">Difficulty</th></tr>
+<tr><td align=center>0</td><td align=center>Rogue Scout</td>
+<td align=center>Fire Arrow</td><td align=center>Normal</td></tr>
+<tr><td align=center>1</td><td align=center>Rogue Scout</td>
+<td align=center>Cold Arrow</td><td align=center>Normal</td></tr>
+<tr><td align=center>2</td><td align=center>Rogue Scout</td>
+<td align=center>Fire Arrow</td><td align=center>Nightmare</td></tr>
+<tr><td align=center>3</td><td align=center>Rogue Scout</td>
+<td align=center>Cold Arrow</td><td align=center>Nightmare</td></tr>
+<tr><td align=center>4</td><td align=center>Rogue Scout</td>
+<td align=center>Fire Arrow</td><td align=center>Hell</td></tr>
+<tr><td align=center>5</td><td align=center>Rogue Scout</td>
+<td align=center>Cold Arrow</td><td align=center>Hell</td></tr>
+<tr><td align=center>6</td><td align=center>Desert Mercenary</td>
+<td align=center>Combat</td><td align=center>Normal</td></tr>
+<tr><td align=center>7</td><td align=center>Desert Mercenary</td>
+<td align=center>Defensive</td><td align=center>Normal</td></tr>
+<tr><td align=center>8</td><td align=center>Desert Mercenary</td>
+<td align=center>Offensive</td><td align=center>Normal</td></tr>
+<tr><td align=center>9</td><td align=center>Desert Mercenary</td>
+<td align=center>Combat</td><td align=center>Nightmare</td></tr>
+<tr><td align=center>10</td><td align=center>Desert Mercenary</td>
+<td align=center>Defensive</td><td align=center>Nightmare</td></tr>
+<tr><td align=center>11</td><td align=center>Desert Mercenary</td>
+<td align=center>Offensive</td><td align=center>Nightmare</td></tr>
+<tr><td align=center>12</td><td align=center>Desert Mercenary</td>
+<td align=center>Combat</td><td align=center>Hell</td></tr>
+<tr><td align=center>13</td><td align=center>Desert Mercenary</td>
+<td align=center>Defensive</td><td align=center>Hell</td></tr>
+<tr><td align=center>14</td><td align=center>Desert Mercenary</td>
+<td align=center>Offensive</td><td align=center>Hell</td></tr>
+<tr><td align=center>15</td><td align=center>Eastern Sorceror</td>
+<td align=center>Fire Spells</td><td align=center>Normal</td></tr>
+<tr><td align=center>16</td><td align=center>Eastern Sorceror</td>
+<td align=center>Cold Spells</td><td align=center>Normal</td></tr>
+<tr><td align=center>17</td><td align=center>Eastern Sorceror</td>
+<td align=center>Lightning Spells</td><td align=center>Normal</td></tr>
+<tr><td align=center>18</td><td align=center>Eastern Sorceror</td>
+<td align=center>Fire Spells</td><td align=center>Nightmare</td></tr>
+<tr><td align=center>19</td><td align=center>Eastern Sorceror</td>
+<td align=center>Cold Spells</td><td align=center>Nightmare</td></tr>
+<tr><td align=center>20</td><td align=center>Eastern Sorceror</td>
+<td align=center>Lightning Spells</td><td align=center>Nightmare</td></tr>
+<tr><td align=center>21</td><td align=center>Eastern Sorceror</td>
+<td align=center>Fire Spells</td><td align=center>Hell</td></tr>
+<tr><td align=center>22</td><td align=center>Eastern Sorceror</td>
+<td align=center>Cold Spells</td><td align=center>Hell</td></tr>
+<tr><td align=center>23</td><td align=center>Eastern Sorceror</td>
+<td align=center>Lightning Spells</td><td align=center>Hell</td></tr>
+<tr><td align=center>24</td><td align=center>Barbarian</td>
+<td align=center></td><td align=center>Normal</td></tr>
+<tr><td align=center>25</td><td align=center>Barbarian</td>
+<td align=center></td><td align=center>Normal</td></tr>
+<tr><td align=center>26</td><td align=center>Barbarian</td>
+<td align=center></td><td align=center>Nightmare</td></tr>
+<tr><td align=center>27</td><td align=center>Barbarian</td>
+<td align=center></td><td align=center>Nightmare</td></tr>
+<tr><td align=center>28</td><td align=center>Barbarian</td>
+<td align=center></td><td align=center>Hell</td></tr>
+<tr><td align=center>29</td><td align=center>Barbarian</td>
+<td align=center></td><td align=center>Hell</td></tr>
+</table>
+
+<hr>
+
+</body>
+</html>
+
+-------------------------------------------------------------------------------
+originally extracted from here:
+http://www.coreyh.org/diablo-2-files/documentation/d2s_notes.txt
+-------------------------------------------------------------------------------
+
+Summary of the various sections. Note the header's ID is actually a file ID, but you get the idea :)
+
+[color=blue]ID, content[/color]
+0xaa55aa55, header
+"Woo!", Quest info
+"WS", Waypoint info
+0x7701, NPC info
+"gf", Main stats info
+"if", Skill info
+"JM", Main itemlist
+"JM", Corpse item list
+"jf", Mercenary section (expansion char only)
+"kf", Iron Golem list (expansion char only)
+
+Note that individual items ALSO has the JM ID as do the Mercenary section if you have one. Confusing, yes :)
+
+
+[color=blue]Header[/color]
++0000 file identifier, 0xaa55aa55
++0004 file version 92
++0008 file size
++000c checksum, d2fog.27f5
++0010 0 if [ptClient+428]b is 0, otherwise 1
++0014 character name, 16 bytes
++0024 flags from [ptClient+0a]b, bit 5 (of 0-7) is set by SAVE code if expansion game
++0025 acts done (see link in post below for more info)
+(+0024 and +0025 is actually returned as a word from [ptClient+0a]w
++0026 empty filler to the 2 previous bytes, 0
++0027 empty filler to the 2 previous bytes, 0
++0028 character class from [ptClient+08]b, hopefully matches that of hUnit :)
++0029 hard coded to 0x10
++002a hard coded to 0x1e
++002b clvl from hUnit
++002c ? from [ptClient+454]dw
++0030 time
++0034 -1, function always return -1
++0038 32 2-byte values, supposedly skills assigned to function keys
++0078 8 2-byte values, supposedly skills assigned to mouse buttons
++0088 16 2-byte values (could be 8 4-byte values) set by d2common.283a, seems to relate to appearance of items/character
++00a8 act playing in normal difficulty
++00a9 act playing in nightmare difficulty
++00aa act playing in hell difficulty
+
+Of the three values above, 2 will be 0 the other will be the actual value with bit 7 set to indicate which difficulty is saved
+
++00ab from [ptGame+78], should be initial seed of game
++00af start of mercenary info, much comes from 6fc71c10 (as ebx+xx), needs checking anyway:
+
++00af flags, only 00100000 seems to be in use set if 6fcad880 returns non 0
++00b3 ebx+00
++00b7 ebx+04, then subtract [d2common.2957+148], should be from mercenary txt
++00b9 ebx+08
++00b9 exp of mercenary from hUnit
+
++00bf to +014e empty, all 0. These bytes can be used for your own custom saved information. just make sure you load it properly too :)
+
+That concludes the main header of the save file. Next follow various sections of information.
+
+[color=blue]Quest info[/color]
++014f "Woo!"
++0153 version of block? 0x00000006
++0157 blocksize, 0x012a
++0159 quest info stuff (to come)
+
+[color=blue]Waypoint info[/color]
++0279 "WS"
++027b version of block? 0x00000001
++027f block size 0x0050
++0281 waypoint info stuff (to come)
+
+[color=blue]NPC info[/color]
++02c9 0x7701
++02cb block size, 0x0034
++02cd NPW info stuff (to come)
+
+[color=blue]Main stats info[/color]
++02fd "gf"
++02ff bitfield indicating which of the 16 main stats follow
++0301 stats (dw) indicated by bitfield, from hUnit
+
+The above section is of variable length
+
+[color=blue]Skill info[/color]
++03xx+00 "if"
++03xx+02 base slvl (b) for 30 skills
+
+[color=blue]Item info[/color]
++03xx+30 Start of item info
+
+The item info is mostly made up of various lists of items. A list will usually contain a header that has a two byte "string", for example "JM" (I would say many of those strings you find are actually short for various programmer names) followed by a word indicating the number of items in the list to follow. Next follow each item itself and I think most (all?) of them will start of with the "JM" string (yes confusing since it is used in two different cases so to speak) followed by item specific data. Socketed items follow right after the item they are socketed into and are not counted in the list header for number of items in the list.
+
+The various lists (of which not all need to be present) are:
+
+[color=blue]Main itemlist[/color]
++00 "JM"
++02 number of items in list
++04 List of items
+
+This includes all items your character have, including those in the stash.
+
+
+[color=blue]Corpse item list[/color]
++00 "JM"
++02 number of corpses
++04 if coprse exists, 12 bytes not used
++10 if corpse exists, list of items
+
+The game obviously have had the ability to save several corpses for a character. Currently, only one corpse is supported though. The "number of corpses" can only be set to 0 or 1 and can thus be thought of as a flag for the existance of a corpse. If the corpse exists there follow 4 dwords of random data. The first value is actually set from an uninitialized local variable and can thus be anything that happens to sit on the stack. The next two values are x and y coordinates (not sure if they actually make any sense though). None of the three values are read by the code by the way. I guess the first value was once which map the coprse was on or something. In any case, thsoe 12 bytes can be ignored. Next follows a normal list of items if a corpse existed.
+
+[color=blue]Mercenary item list[/color]
++00 "jf" (only exists if expansion game regardless of if you have a mercenary or not)
++02 "JM" (only exists if you actually have a mercenary)
++04 number of items in list (only exists if you actuall have a mercenary)
++06 List of items (only exists if you actually have a mercenary)
+
+In an expansion game you then get:
+
+[color=blue]Iron Golem list[/color]
++00 "kf"
++02 0 or 1 (b), a 1 indictaing an Iron Golem exists
++03 if an Iron Golem eixts the item used to create it will follow here
+
+
+
+
+Next to be added is detailed info on the data for each item saved in a list. It is a quite variable content depending on the item and also quite large. It will follow below. Note that the same function that compress an item for saving seems to be used to compress items for sending between server and client. It has the ability to mask many properties in such cases for non identified items for example when you gamble I would guess. I will not at all handle that here but only the case for actually saving an item.
+
+Since items are saved in a very compressed way on bit levels (and not bytes). In addition, what actually is saved varies with the item type and so on. I will thus not give offsetts but rather the number of bits (in decimal notation) something is saved in. The order would be the one the game places them though, so disregarding the fact that some section might be missing for some items the order should NEVER be another than the one I list below.
+
+
+[color=blue]Common item data[/color]
+16 "JM"
+32 flags [ptItemstats+18], ptItemstats is [hUnit+70]
+
+Note, the flags are somewhat modified, some removed and some set by the save code but in much should be identical with the run time flags.
+
+10 version of item, 0, 1 or 100. 100 are new expansion items, 1 are new classic items and 0 is old pre expansion items. Note that all items should be converted to new ones in a current game (I think) at least no item should remain as version 0.
+
+3 mode, from hUnit+0c
+
+The mode of items seems to mostly be were the item actually is "located", as oposed to some action it performs. See the thread maping out the ptUnit (which I call hUnit in this thread) for more info. Although I can't imagine a situation were the item is in mode 3 (ground) or 5 (whatever that might be) the save file has a special case for them. In that case, the mode would be followed by 2 32 bit x and y coordinates (from d2common.2856 and 2859). For other items we instead have the three following entries.
+
+4 body location [ptItemstats+40]. This tells were, if at all, the item is equiped
+
+4 x coordinate in inventory (d2common.2856)
+
+4 y coordinate in inventory (d2common.2859)
+
+3 page number PLUS 1. The page tells where in the invenotry the item is. Example of different pages are stash cube, main invenotry on character and so on. Pages like trade screen and such should not matter although I am not sure what happens if the game tries to save your character while the trade screen is open, you might end up with items on that page too for example. Same with an item on the cursor.
+
+32 item code
+
+The 3 letter code each base item have. This is for  non ears only (flag 00010000 in the flag data above is set for ears). Ears does not save the code, instead they have:
+
+ 3 class of ear
+ n*7 name of ear. This is the character name of the ear and is ended by a 0 value. The name is stored at [ptItemstats+44] (first letter) and the following at [ptItemstats+46] and onwards.
+
+For the interested, in non saved structures, if the item is gold (which obviously never save as items), the ammount of gold is inserted after the item code. First comes a 1 bit indicating the size. A 1 indicate a 32 bit value a 0 indicate a 12 bit value. That 12/32 bit value then follows and specify the ammount of gold.
+
+Compact save items will have no other data than the above one. Flag 00200000 is set on compact save items. Note that flag is set only upon save, not normally in the flag register. It will be cleared in the process of loading. The compact saving info of an item is fetched from the appropriate item.txt file upon saving and checked for.
+
+
+
+
+[color=blue]Non compact save item data[/color]
+3 number of socketed items
+32 creation seed, from [hUnit+34]
+7 ilvl, from [ptItemstats+28]
+4 quality, from [ptItemstats+00]
+1 flag for variable picture (itemtypes "varinvgfx")
+3 if flag=1, number indicating which picture to use
+1 flag for autoprefix on item
+11 if flag=1, info on which autoprefix
+
+Next follows data depending on the quality of the item.
+
+Low quality
+3 type of low quality property
+
+Normal quality
+No special data saved
+
+Superior
+3 type of superiorproperty
+
+Magic
+11 which prefix the item has
+11 which suffix the item has
+
+In both cases it is the entry in the appropriate affix table (were a 0 value indicate none). This applies to the autoprefix above as well.
+
+Rare and Crafted
+8 which prefix name the item has
+8 which suffix name the item has
+1 flag indicating if a prefix follows
+11 if flag=1, which prefix the item has
+1 flag indicating if a suffix follows
+11 if flag=1, which suffix the item has
+1 flag indicating if a prefix follows
+11 if flag=1, which prefix the item has
+1 flag indicating if a suffix follows
+11 if flag=1, which suffix the item has
+1 flag indicating if a prefix follows
+11 if flag=1, which prefix the item has
+1 flag indicating if a suffix follows
+11 if flag=1, which suffix the item has
+
+Each rare item can have up to 3 prefixes and 3 suffixes.
+
+Set
+12 which set (in setitems.txt) the item is part of
+
+Unique
+12 which unique (in unqiue.txt) the item is
+
+
+...more to come
+
+<html>
+<h1 align="center">Diablo II Save Game File Format</h1>
+<h3 align="center">for Diablo II Expansion Set v1.13d</h3>
+<div align="center">Updated July 1, 2012</div>
+<p>This page was originally written by Trevin Beattie, whose site is no more (his latest version of this page is available
+<a href="https://web.archive.org/web/20161224202623/http://web.archive.org/web/20070831101200/http://www.xmission.com/~trevin/DiabloIIv1.09_File_Format.shtml">here</a> though).<br/>
+Now this page is maintained by me, Yuri Sakhno (George1).</p>
+
+<h2>Introduction</h2>
+<p>This page describes the format of saved game files for the game Diablo II Expansion Set v1.13d.
+While the information presented here is mostly aplicable to earlier versions of the game, there were some drastic
+changes in version 1.10 (particularly, in how character stats are saved), so if you intend to read files of the versions
+of the game erlier than that, you would probably be better off opening that save in some recent version of the game and
+then saving it again (upgrading the saved game file).</p>
+<p><i>(Note: all values larger than a byte are stored in x86 little-endian order &#x2014;
+i.e., least significant byte first. A &quot;<tt>short</tt>&quot; is 2 bytes long,
+and a &quot;<tt>long</tt>&quot; is 4 bytes long. Values starting with &quot;0x&quot; are given
+in hexadecimal notation; otherwise they are decimal.)</i></p>
+
+<h2>File Header</h2>
+<p>Each save file starts with a file header. Depending on the circumstances, this may be the only section present in saved game file.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="8%">Byte Position</th>
+    <th width="8%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">0</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>File identifier. This must be the value <tt>0xAA55AA55</tt>.</td>
+  </tr>
+  <tr>
+    <td align="middle">4</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>File version. The following values are known:<br/>
+      &#xA0;&#xA0;&#xA0; <tt>0x47</tt>&#xA0; v1.00 through v1.06<br/>
+      &#xA0;&#xA0;&#xA0; <tt>0x57</tt>&#xA0; v1.07 or Expansion Set v1.08<br/>
+      &#xA0;&#xA0;&#xA0; <tt>0x59</tt>&#xA0; standard game v1.08<br/>
+      &#xA0;&#xA0;&#xA0; <tt>0x5C</tt>&#xA0; v1.09 (both the standard game and the Expansion Set.)<br/>
+      &#xA0;&#xA0;&#xA0; <tt>0x60</tt>&#xA0; v1.10 and above<br/>
+      As it was outlined above, this document only covers version <tt>0x60</tt> of the file format.</td>
+  </tr>
+  <tr>
+    <td align="middle">8</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>Size of the file, in bytes.</td>
+  </tr>
+  <tr>
+    <td align="middle">12</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>Checksum of the netire save file. If you attempt to hack the file without storing the
+      correct checksum afterwards, your game will fail to load.
+      Fortunately, the checksum algorithm is very simple.
+      After clearing the checksum field, you add up the values of all the bytes
+      in the file, rotating the running total one bit to the left before adding
+      each byte. Then store the result in this field.</td>
+  </tr>
+  <tr>
+    <td align="middle">16</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>Active arms. Determines which weapon set is currently active.</td>
+  </tr>
+  <tr>
+    <td align="middle">20</td>
+    <td align="middle">16 <tt>char</tt>s</td>
+    <td><a href="Random_Character_Names.html">Character name</a>. The name may be up to 15 characters long;
+      the rest of the field must be padded with null-characters. <i>Remember the rules for
+      Diablo II character names: 2-15 characters, containing only upper and
+      lower case letters (A-Z), with the possible addition of one dash ( - ) or
+      underscore ( _ ) as long as it is not the first or last character of the
+      name.</i></td>
+  </tr>
+  <tr>
+    <td align="middle">36</td>
+    <td align="middle">byte</td>
+    <td>
+      <div>Character status. This is a bit field:</div>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td align="middle" colspan="2"><i>unknown</i></td>
+          <td align="middle">Expansion<br/>Character</td>
+          <td align="middle"><i>unknown</i></td>
+          <td align="middle">Died</td>
+          <td align="middle">Hardcore</td>
+          <td align="middle" colspan="2"><i>unknown</i></td>
+        </tr>
+      </tbody>
+      </table>
+      <div><i>Note: the &quot;died&quot; bit indicates that your character
+      has died at some point in the past. It is never cleared when you resume the game.
+      To find out whether your character is currently dead, you need to look
+      in the <a href="#item_list">item list</a> below to see if there is some corpse data.
+      Obviously, if you have a hardcore character and this bit is set, you won't be able
+      to play the game with that charcter anymore.</i></div></td>
+  </tr>
+  <tr>
+    <td align="middle">37</td>
+    <td align="middle">byte</td>
+    <td>
+      Character progression. This number tells (sort of) how many acts
+      you have completed from all difficulty levels. It appears to be
+      incremented when you kill the final demon in an act &#x2014; i.e., Andarial,
+      Duriel, Mephisto, and Diablo / Baal. There's a catch to that last
+      one: in an Expansion game, the value is <em>not</em> incremented after
+      killing Diablo, but is incremented by 2 after killing Baal. (The
+      reason is unknown.) So it skips the values 4, 9, and 14.
+      <p>I believe this value is used in determining your character's
+      title. The title is one of the following values (depending on the
+      character class' gender):</p>
+      <table border="0" align="center">
+      <tbody>
+        <tr>
+          <th width="6%">Value</th>
+          <th width="20%">Standard</th>
+          <th width="20%">Hardcore</th>
+          <th width="6%">Value</th>
+          <th width="20%">Expansion</th>
+          <th width="20%">Hardcode Expansion</th>
+          <td width="8%" colspan="5"><!-- @ --></td>
+        </tr>
+        <tr>
+          <td align="middle"><tt>0</tt>-<tt>3</tt></td>
+          <td align="middle" colspan="2"><i>(no title)</i></td>
+          <td align="middle"><tt>0</tt>-<tt>3</tt></td>
+          <td align="middle" colspan="2"><i>(no title)</i></td>
+        </tr>
+        <tr>
+          <td align="middle"><tt>4</tt>-<tt>7</tt></td>
+          <td align="middle">Sir / Dame</td>
+          <td align="middle">Count / Countess</td>
+          <td align="middle"><tt>5</tt>-<tt>8</tt></td>
+          <td align="middle">Slayer</td>
+          <td align="middle">Destroyer</td>
+        </tr>
+        <tr>
+          <td align="middle"><tt>8</tt>-<tt>11</tt></td>
+          <td align="middle">Lord / Lady</td>
+          <td align="middle">Duke / Duchess</td>
+          <td align="middle"><tt>10</tt>-<tt>13</tt></td>
+          <td align="middle">Champion</td>
+          <td align="middle">Conqueror</td>
+        </tr>
+        <tr>
+          <td align="middle"><tt>12</tt></td>
+          <td align="middle">Baron / Baroness</td>
+          <td align="middle">King / Queen</td>
+          <td align="middle"><tt>15</tt></td>
+          <td align="middle">Patriarch / Matriarch</td>
+          <td align="middle">Guardian</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">38</td>
+    <td align="middle">2 bytes</td>
+    <td><i>unknown; probably some kind of padding</i></td>
+  </tr>
+  <tr>
+    <td align="middle">40</td>
+    <td align="middle">byte</td>
+    <td>Character class. The defined classes are:<br/>
+      &#xA0;&#xA0;&#xA0;&#xA0; <tt>0x00</tt>&#xA0; Amazon<br/>
+      &#xA0;&#xA0;&#xA0;&#xA0; <tt>0x01</tt>&#xA0; Sorceress<br/>
+      &#xA0;&#xA0;&#xA0;&#xA0; <tt>0x02</tt>&#xA0; Necromancer<br/>
+      &#xA0;&#xA0;&#xA0;&#xA0; <tt>0x03</tt>&#xA0; Paladin<br/>
+      &#xA0;&#xA0;&#xA0;&#xA0; <tt>0x04</tt>&#xA0; Barbarian<br/>
+      &#xA0;&#xA0;&#xA0;&#xA0; <tt>0x05</tt>&#xA0; Druid (Expansion character only)<br/>
+      &#xA0;&#xA0;&#xA0;&#xA0; <tt>0x06</tt>&#xA0; Assassin (Expansion character only)</td>
+  </tr>
+  <tr>
+    <td align="middle">41</td>
+    <td align="middle">2 bytes</td>
+    <td><i>unknown; I've only seen the values { 16, 30 } here.</i></td>
+  </tr>
+  <tr>
+    <td align="middle"><a name="header_level">43</a></td>
+    <td align="middle">byte</td>
+    <td>Character's level. This is the level shown on the character selection screen, but it
+      should equal the level given in the <a href="#stats_level">character statistics</a> section.</td>
+  </tr>
+  <tr>
+    <td align="middle">44</td>
+    <td align="middle"><tt>long</tt></td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">48</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>Time stamp. This is in the standard <tt>time()</tt> format of the number
+      of seconds which have elapsed since midnight, January 1, 1970 (UTC).</td>
+  </tr>
+  <tr>
+    <td align="middle">52</td>
+    <td align="middle"><tt>long</tt></td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">56</td>
+    <td align="middle">16 <tt>long</tt>s</td>
+    <td>These are the <a href="Skills.html">skill Ids</a> assigned to the hotkeys for Skill&#xA0;1
+      through Skill&#xA0;16. If a skill hotkey is not assigned to a skill, the value is <tt>0xFFFF</tt>.
+      <p><!-- @ --></p>
+      <div>Hotkey definitions are stored in the <tt><i>character</i>.key</tt>
+      file. The structure of that file is not covered by this document.</div></td>
+  </tr>
+  <tr>
+    <td align="middle"><a name="120">120</a></td>
+    <td align="middle"><tt>long</tt></td>
+    <td>The action assigned to the left mouse button. The value of this field is a <a href="Skills.html">skill Id</a>.</td>
+  </tr>
+  <tr>
+    <td align="middle">124</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>The action assigned to the right mouse button. The value of this field is also a <b>skill Id</b>.</td>
+  </tr>
+  <tr>
+    <td align="middle">128</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>In an Expansion character, the action assigned to the alternate left
+      mouse button. (The button assignments are swapped when you swap weapons.)</td>
+  </tr>
+  <tr>
+    <td align="middle">132</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>In an Expansion character, the action assigned to the alternate right mouse button.</td>
+  </tr>
+  <tr>
+    <td align="middle">136</td>
+    <td align="middle">32 bytes</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">168</td>
+    <td align="middle">3 bytes</td>
+    <td>These bytes indicate which difficulty the character is playing.
+      The first byte corresponds to Normal, the second Nightmare, and the third
+      Hell. If the value is zero, the character is not playing at that
+      level. Otherwise, the value looks like this:
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td align="middle">Active</td>
+          <td align="middle" colspan="4"><i>unknown</i></td>
+          <td align="middle" colspan="3">Which Act the<br/>character is in (<tt>0</tt>-<tt>4</tt>)</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">171</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>Map Id. This value looks like a random number, but it corresponds with one of the <tt>long</tt>s
+      found in the <tt><i>character</i>.map</tt> file, according to the difficulty being played.</td>
+  </tr>
+  <tr>
+    <td align="middle">175</td>
+    <td align="middle"><tt>short</tt></td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">177</td>
+    <td align="middle"><tt>short</tt></td>
+    <td>If your Expansion character has a mercenary who is currently dead, this field is non-zero.</td>
+  </tr>
+  <tr>
+    <td align="middle">179</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>This looks like a random Id for your mercenary. It is <tt>0</tt> if you have never had a mercenary.
+      If your mercenary has died or (in the standard game) been left behind when you move on to the next act,
+      this field is still set to the last mercenary you had.</td>
+  </tr>
+  <tr>
+    <td align="middle"><a name="183">183</a></td>
+    <td align="middle"><tt>short</tt></td>
+    <td>This is a numerical index into the game's language-dependent string table for mercenary names.
+      There is a separate list for each type of mercenary (Rogue Scout, Desert Mercenary, Eastern Sorceror,
+      and Barbarian). Trevin wrote a <a href="Mercenaries.html">list of mercenary names</a> for the English 1.09 patch.</td>
+  </tr>
+  <tr>
+    <td align="middle">185</td>
+    <td align="middle"><tt>short</tt></td>
+    <td>This code determines the difficulty level and act where your mercenary was found, as well as the attribute
+      of your mercenary (i.e. Cold, Fire, Lightning). Trevin wrote a
+      <a href="Mercenaries.html#code">list of the mercenary codes</a> appended to the end of the mercenary name.</td>
+  </tr>
+  <tr>
+    <td align="middle">187</td>
+    <td align="middle"><tt>long</tt></td>
+    <td>Your mercenary's experience points.</td>
+  </tr>
+  <tr>
+    <td align="middle">191</td>
+    <td align="middle">144 bytes</td>
+    <td><i>unknown</i></td>
+  </tr>
+</tbody>
+</table>
+
+<a name="new_character_small_file"><p>For the newly-created character, this is the only information present in the file (i.e. the file consists of just the header).
+The save file is extended (all other sections added) when you exit the game (even if you haven't done anything in it),
+but the very first save created by the game (i.e. right after you click the OK button on the character-creation screen)
+will be the save with just the header present. Such a save is still a legitimate save, which the game can successfully load.</p></a>
+
+<h2>Quest Completion Data</h2>
+<p>The quest data begins with the following header:</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="10%">Byte Position</th>
+    <th width="10%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">335</td>
+    <td align="middle">4 <tt>char</tt>s</td>
+    <td>The string identifier &quot;<tt>Woo!</tt>&quot;.</td>
+  </tr>
+  <tr>
+    <td align="middle">339</td>
+    <td align="middle">6 bytes</td>
+    <td><i>unknown; there are values { <tt>0x06</tt>, <tt>0x00</tt>, <tt>0x00</tt>, <tt>0x00</tt>, <tt>0x2A</tt>, <tt>0x01</tt> } always present here.</i></td>
+  </tr>
+</tbody>
+</table>
+<p>The header is followed by three structures, one for each difficulty level. Note that the byte
+offsets given here are offsets into the structure; the first structure is at offset 345 in the file,
+the second one is at offset 441, and the third one at 537. You have to add the offsets from the table
+to these values to get the actual offset in the file for the corresponding field for the specific difficulty level.</p>
+<p>Although there is some variation in the meaning of the bits per quest, some of the bits appear to have constant meaning.</p>
+<p>Bit 0 indicates the quest is complete. If bit 0 is not set but the rest of the field is non-zero,
+then the quest has been started, but not finished.</p>
+<p>Bit 1 generally means you have completed the requirements for the quest
+(i.e., killed the boss demon), and all that's left is to collect the reward &#x2014;
+for example, &quot;Charsi will imbue an item with magical power.&quot; Not all
+quests have this option. If this bit is set, bit 0 must be cleared.</p>
+<p>Bit 2 is often set when an NPC gives you a quest.</p>
+<p>Bit 12 is set when you have seen the swirling fire animation that closes a quest icon.</p>
+<p>Bit 13 indicates the quest was completed in the current game; when you save
+the game and then reload it, all bit 13's are cleared.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="10%">Byte Position</th>
+    <th width="10%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">0</td>
+    <td align="middle"><tt>short</tt></td>
+    <td>This field contains a 1 if you have been introduced (by Warriv) to Act I.</td>
+  </tr>
+  <tr>
+    <td align="middle">2</td>
+    <td align="middle">6 <tt>short</tt>s</td>
+    <td>
+      <div>These fields contain quest completion data for each quest in Act I.</div>
+      <table cellspacing="0" width="100%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%"><tt>short</tt>&#xA0;#</th>
+          <th width="35%">Quest</th>
+          <th width="55%">Notes</th>
+        </tr>
+        <tr>
+          <td align="middle">0</td>
+          <td>Den of Evil</td>
+          <td>Bit 4 is set when you enter the Den.</td>
+        </tr>
+        <tr>
+          <td align="middle">1</td>
+          <td>Sisters' Burial Grounds</td>
+          <td>Bit 4 is set when you enter the Burial Grounds.</td>
+        </tr>
+        <tr>
+          <td align="middle">2</td>
+          <td>Tools of the Trade</td>
+          <td>Bit 6 is set when you pick up the Horadric Malus.</td>
+        </tr>
+        <tr>
+          <td align="middle">3</td>
+          <td>The Search for Cain</td>
+          <td>Bit 4 is set when you enter Tristram.<br/>Bit 10 indicates
+            whether you have completed the secret Cow Level (&quot;Moo&quot;). If
+            you want to fight the Cow King again, just clear this bit!<br/>If you
+            enter Act II without rescuing Deckard Cain, bit 14 will get
+            set. You will not be able to rescue Cain yourself; the Rogues
+            will have done it instead, and as a consequence, you will be charged
+            a fee if you want Cain to identify items for you.</td>
+        </tr>
+        <tr>
+          <td align="middle">4</td>
+          <td>The Forgotten Tower</td>
+          <td>Bit 2 is set when you read the Moldy Tome.<br/>Bit 6 is set when
+            you enter the Forgotten Tower.</td>
+        </tr>
+        <tr>
+          <td align="middle">5</td>
+          <td>Sisters to the Slaughter</td>
+          <td><!-- @ --></td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">14</td>
+    <td align="middle"><tt>short</tt></td>
+    <td><i>uncertain; perhaps this gets set to a non-zero value after you travel from Act I to Act II.</i></td>
+  </tr>
+  <tr>
+    <td align="middle">16</td>
+    <td align="middle"><tt>short</tt></td>
+    <td>This field contains a 1 if you have been introduced (by Jerhyn) to Act II.</td>
+  </tr>
+  <tr>
+    <td align="middle">18</td>
+    <td align="middle">6 <tt>short</tt>s</td>
+    <td>
+      <div>These fields contain quest completion data for each quest in Act II.</div>
+      <table cellspacing="0" width="100%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%"><tt>short</tt>&#xA0;#</th>
+          <th width="35%">Quest</th>
+          <th width="55%">Notes</th>
+        </tr>
+        <tr>
+          <td align="middle">0</td>
+          <td>Radament's Lair</td>
+          <td>Bit 4 is set when you find Radament.</td>
+        </tr>
+        <tr>
+          <td align="middle">1</td>
+          <td>The Horadric Staff</td>
+          <td>Bit 4 is set when Cain tells you about the Viper Amulet.<br/>
+            Bit 5 is set when Cain tells you about the Staff of Kings.<br/>
+            Bit 10 is set when Cain tells you about the Horadric Staff.<br/>
+            Bit 11 is set when you make the Horadric Staff.</td>
+        </tr>
+        <tr>
+          <td align="middle">2</td>
+          <td>Tainted Sun</td>
+          <td>Bit 2 is set when the sun goes out.<br/>
+            Bit 3 is set when Drognan tells you why.</td>
+        </tr>
+        <tr>
+          <td align="middle">3</td>
+          <td>Arcane Sanctuary</td>
+          <td rowspan="2"><!-- @ --></td>
+        </tr>
+        <tr>
+          <td align="middle">4</td>
+          <td>The Summoner</td>
+        </tr>
+        <tr>
+          <td align="middle">5</td>
+          <td>The Seven Tombs</td>
+          <td>Bit 3 is set when you talk to Tyrael.<br/>
+            Bit 4 is set when you talk to Jerhyn (after killing Duriel).<br/>
+            Bit 5 is set when you kill Duriel.<br/>
+            Bit 6 is set when Atma congratulates you.<br/>
+            Bit 7 is set when Warriv congratulates you.<br/>
+            Bit 8 is set by Drognan.<br/>
+            Bit 9 is set by Lysander.<br/>
+            Bit 10 is set by Cain.<br/>
+            Bit 11 is set by Fara.</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">30</td>
+    <td align="middle"><tt>short</tt></td>
+    <td><i>uncertain; perhaps this gets set to a non-zero value after you travel from Act II to Act III.</i></td>
+  </tr>
+  <tr>
+    <td align="middle">32</td>
+    <td align="middle"><tt>short</tt></td>
+    <td>This field contains a 1 if you have been introduced (by Hratli) to Act III.</td>
+  </tr>
+  <tr>
+    <td align="middle">34</td>
+    <td align="middle">6 <tt>short</tt>s</td>
+    <td>
+      <div>These fields contain quest completion data for each quest in Act III.</div>
+      <table cellspacing="0" width="100%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%"><tt>short</tt>&#xA0;#</th>
+          <th width="35%">Quest</th>
+          <th width="55%">Notes</th>
+        </tr>
+        <tr>
+          <td align="middle">0</td>
+          <td>Lam Esen's Tome</td>
+          <td rowspan="2"><!-- @ --></td>
+        </tr>
+        <tr>
+          <td align="middle">1</td>
+          <td>Khalim's Will</td>
+        </tr>
+        <tr>
+          <td align="middle">2</td>
+          <td>Blade of the Old Religion</td>
+          <td>Bit 2 is set when you pick up the Gidbinn.<br/>
+            Bit 3 is set when Hratli asks you to find the Gidbinn.</td>
+        </tr>
+        <tr>
+          <td align="middle">3</td>
+          <td>The Golden Bird</td>
+          <td>Bit 2 is set when Cain tells you about the Jade Figurine.<br/>
+            Bit 4 is set when Cain tells you about the Golden Bird.<br/>
+            Bit 5 is set when you are given the Potion of Life, and cleared again when you
+            drink the Potion. (This prevents you from drinking more than one in a game.)<br/>
+            Bit 6 is set when you find the Jade Figurine.</td>
+        </tr>
+        <tr>
+          <td align="middle">4</td>
+          <td>The Blackened Temple</td>
+          <td rowspan="2"><!-- @ --></td>
+        </tr>
+        <tr>
+          <td align="middle">5</td>
+          <td>The Guardian</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">46</td>
+    <td align="middle"><tt>short</tt></td>
+    <td><i>uncertain; perhaps this gets set to a non-zero value after you travel from Act III to Act IV.</i></td>
+  </tr>
+  <tr>
+    <td align="middle">48</td>
+    <td align="middle"><tt>short</tt></td>
+    <td>This field contains a 1 if you have been introduced to Act IV.</td>
+  </tr>
+  <tr>
+    <td align="middle">50</td>
+    <td align="middle">6 <tt>short</tt>s</td>
+    <td>
+      <div>These fields contain quest completion data for each quest in Act
+      IV. Note that there are only three quests here, as opposed to 6 for
+      the first three Acts.</div>
+      <table cellspacing="0" width="100%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%"><tt>short</tt>&#xA0;#</th>
+          <th width="35%">Quest</th>
+          <th width="55%">Notes</th>
+        </tr>
+        <tr>
+          <td align="middle">0</td>
+          <td>The Fallen Angel</td>
+          <td rowspan="3"><!-- @ --></td>
+        </tr>
+        <tr>
+          <td align="middle">1</td>
+          <td>Terror's End</td>
+        </tr>
+        <tr>
+          <td align="middle">2</td>
+          <td>Hell's Forge</td>
+        </tr>
+        <tr>
+          <td align="middle">3-5</td>
+          <td><i>unused</i></td>
+          <td>It looks like quest data for Act IV still has place for 6 quests, despite the fact that this act only has 3.</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">62</td>
+    <td align="middle"><tt>short</tt></td>
+    <td><i>uncertain; perhaps this gets set to a non-zero value after you travel from Act IV to Act V in an Expansion game,
+      <b>but this assumption has not been verified yet</b>.</i></td>
+  </tr>
+  <tr>
+    <td align="middle">64</td>
+    <td align="middle"><tt>short</tt></td>
+    <td><i>unknown; in an Expansion character, this was set to 1 after
+      completing Terror's End and talking to Cain in act IV</i>.</td>
+  </tr>
+  <tr>
+    <td align="middle">66</td>
+    <td align="middle">2 <tt>short</tt>s</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">70</td>
+    <td align="middle">6 <tt>short</tt>s</td>
+    <td>
+      <div>These fields contain quest completion data for each quest in Act V.</div>
+      <table cellspacing="0" width="100%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%"><tt>short</tt>&#xA0;#</th>
+          <th width="35%">Quest</th>
+          <th width="55%">Notes</th>
+        </tr>
+        <tr>
+          <td align="middle">0</td>
+          <td>Siege on Harrogath</td>
+          <td>Bit 3 is set when you find Shenk.<br/>
+            Bit 5 is set when Larzuk offers to socket an item for you.</td>
+        </tr>
+        <tr>
+          <td align="middle">1</td>
+          <td>Rescue on Mount Arreat</td>
+          <td><!-- @ --></td>
+        </tr>
+        <tr>
+          <td align="middle">2</td>
+          <td>Prison of Ice</td>
+          <td>Bit 7 is set when you read the Scroll of Resistance.<br/>
+            Bit 8 is set after you rescue Anya and talk to Malah.</td>
+        </tr>
+        <tr>
+          <td align="middle">3</td>
+          <td>Betrayal of Harrogath</td>
+          <td>Bit 4 is set when Anya offers to personalize an item for you.</td>
+        </tr>
+        <tr>
+          <td align="middle">4</td>
+          <td>Rite of Passage</td>
+          <td><!-- @ --></td>
+        </tr>
+        <tr>
+          <td align="middle">5</td>
+          <td>Eve of Destruction</td>
+          <td>Bit 4 is set when Larzuk congratulates you.<br/>
+            Bit 5 is set when Cain congratulates you.<br/>
+            Bit 6 is set when Malah congratulates you.<br/>
+            Bit 7 is set by Tyrael.<br/>
+            Bit 8 is set by Qual-Kehk.<br/>
+            Bit 9 is set by Anya.</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">82</td>
+    <td align="middle">7 <tt>short</tt>s</td>
+    <td><i>unknown</i></td>
+  </tr>
+</tbody>
+</table>
+
+<h2>Waypoints Data</h2>
+<p>The waypoints data begins with the following header:</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="10%">Byte Position</th>
+    <th width="10%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">633</td>
+    <td align="middle">2 <tt>char</tt>s</td>
+    <td>The string identifier &quot;<tt>WS</tt>&quot;.</td>
+  </tr>
+  <tr>
+    <td align="middle">635</td>
+    <td align="middle">6 bytes</td>
+    <td><i>unknown; there are values { <tt>0x01</tt>, <tt>0x00</tt>, <tt>0x00</tt>, <tt>0x00</tt>, <tt>0x50</tt>, <tt>0x00</tt> } always present here.</i></td>
+  </tr>
+</tbody>
+</table>
+<p>The header is followed by three structures, one per each difficulty level.
+Note that the byte offsets given here are offsets into the structure; the first structure is at offset 641 in the file,
+the second one is at offset 665, and the third at 689. You have to add the offsets from the table
+to these values to get the actual offset in the file for the corresponding field for the specific difficulty level.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="10%">Byte Position</th>
+    <th width="10%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">0</td>
+    <td align="middle">2 bytes</td>
+    <td><i>unknown; there are values { <tt>0x02</tt>, <tt>0x01</tt> } always present here.</i></td>
+  </tr>
+  <tr>
+    <td align="middle">2</td>
+    <td align="middle">5 bytes</td>
+    <td>Waypoints. This is a bitfield, with one bit assigned to each
+      waypoint in LSB order &#x2014; so bit 0 in the Rogue Encampment waypoint for Act
+      I. The first waypoint in every Act is activated as soon as you enter
+      that Act. There are 9 waypoints (bits) in each of Acts I, II, and
+      III, and 3 waypoints (bits) in Act IV, so the last waypoint before Diablo
+      (River of Flame) is bit 29 (since we start counting from 0). The
+      first waypoint for Act V follows at bit 30, and continues to the last
+      (ninth) waypoint in Act V at bit 38.
+      <p><!-- @ --></p>
+      <div>The first waypoint in each of the difficulty levels is always activated,
+      even if you have never been to that difficulty level.</div></td>
+  </tr>
+  <tr>
+    <td align="middle">7</td>
+    <td align="middle">17 bytes</td>
+    <td><i>unknown</i></td>
+  </tr>
+</tbody>
+</table>
+
+<p>There is an additional byte value at file offset 713 after the three waypoints structures.
+This byte always has value <tt>0x01</tt> and probably serves as some kind of trailer.</p>
+
+<h2>NPC Introductions</h2>
+<p>Trevin's data on the next section was very sketchy, and hasn't improved since at all.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="10%">Byte Position</th>
+    <th width="10%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">714</td>
+    <td align="middle">2 <tt>char</tt>s</td>
+    <td>The string identifier &quot;<tt>w4</tt>&quot;.</td>
+  </tr>
+  <tr>
+    <td align="middle">716</td>
+    <td align="middle">1 byte</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">717</td>
+    <td align="middle">1 byte</td>
+    <td>
+      <div>You have been introduced to:</div>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td align="middle">Warriv</td>
+          <td><!-- @ --></td>
+          <td align="middle">Charsi</td>
+          <td><!-- @ --></td>
+          <td align="middle">Kashya</td>
+          <td align="middle">Akara</td>
+          <td align="middle">Gheed</td>
+          <td><!-- @ --></td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">718</td>
+    <td align="middle">1 byte</td>
+    <td>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td align="middle">Greiz</td>
+          <td><!-- @ --></td>
+          <td align="middle">Meshif</td>
+          <td align="middle">Geglash</td>
+          <td align="middle">Lysander</td>
+          <td align="middle">Fara</td>
+          <td align="middle">Drognan</td>
+          <td><!-- @ --></td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">719</td>
+    <td align="middle">1 byte</td>
+    <td>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td align="middle">Alkor</td>
+          <td><!-- @ --></td>
+          <td align="middle">Asheara</td>
+          <td colspan="2"><!-- @ --></td>
+          <td align="middle">Cain</td>
+          <td><!-- @ --></td>
+          <td align="middle">Elzix</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">720</td>
+    <td align="middle">1 byte</td>
+    <td>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td align="middle">Malah</td>
+          <td align="middle">Anya</td>
+          <td><!-- @ --></td>
+          <td align="middle">Natalya</td>
+          <td align="middle">Meshif</td>
+          <td colspan="2"><!-- @ --></td>
+          <td align="middle">Ormus</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">721</td>
+    <td align="middle">1 byte</td>
+    <td>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td colspan="5"><!-- @ --></td>
+          <td align="middle">Cain</td>
+          <td align="middle">Qual-Kehk</td>
+          <td align="middle">Nihlathak</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">722</td>
+    <td align="middle">3 bytes</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">725</td>
+    <td align="middle">8 bytes</td>
+    <td>Introductions repeated for Nightmare difficulty.</td>
+  </tr>
+  <tr>
+    <td align="middle">733</td>
+    <td align="middle">8 bytes</td>
+    <td>Introductions repeated for Hell difficulty.</td>
+  </tr>
+  <tr>
+    <td align="middle">741</td>
+    <td align="middle">1 byte</td>
+    <td>
+      <p>It would appear that bits 1-6 of byte 741 get set after you take the
+      caravan to Act II in Normal difficulty. Bit 7 of byte 741 through
+      bit 1 of byte 743 get set after you sail to Act III. On entering Act
+      IV, bits 2, 5, 6, &amp; 7 of byte 743 and bits 0, 3, &amp; 4 of byte 744
+      get set.</p>
+      <p>When you return to a previous act and talk to the NPC's, these bits are
+      cleared.</p>
+      <div>You have yet to be welcomed back by:</div>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td align="middle">Warriv</td>
+          <td align="middle">?</td>
+          <td align="middle">Charsi</td>
+          <td align="middle">Warriv</td>
+          <td align="middle">Kashya</td>
+          <td align="middle">Akara</td>
+          <td align="middle">Gheed</td>
+          <td><!-- @ --></td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">742</td>
+    <td align="middle">1 byte</td>
+    <td>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td align="middle">Greiz</td>
+          <td align="middle">Jerhyn</td>
+          <td align="middle">Meshif</td>
+          <td align="middle">Geglash</td>
+          <td align="middle">?</td>
+          <td align="middle">Fara</td>
+          <td align="middle">Drognan</td>
+          <td align="middle">?</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">743</td>
+    <td align="middle">1 byte</td>
+    <td>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td align="middle">Alkor</td>
+          <td align="middle">Hratli</td>
+          <td align="middle">Asheara</td>
+          <td colspan="2"><!-- @ --></td>
+          <td align="middle">?</td>
+          <td align="middle">?</td>
+          <td align="middle">Elzix</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">744</td>
+    <td align="middle">1 byte</td>
+    <td>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <th width="10%">7</th>
+          <th width="10%">6</th>
+          <th width="10%">5</th>
+          <th width="10%">4</th>
+          <th width="10%">3</th>
+          <th width="10%">2</th>
+          <th width="10%">1</th>
+          <th width="10%">0</th>
+        </tr>
+        <tr>
+          <td colspan="3"><!-- @ --></td>
+          <td align="middle">?</td>
+          <td align="middle">?</td>
+          <td colspan="2"><!-- @ --></td>
+          <td align="middle">Ormus</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">745</td>
+    <td align="middle">4 bytes</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">749</td>
+    <td align="middle">8 bytes</td>
+    <td>Greetings repeated for Nightmare difficulty.</td>
+  </tr>
+  <tr>
+    <td align="middle">757</td>
+    <td align="middle">8 bytes</td>
+    <td>Greetings repeated for Hell difficulty.</td>
+  </tr>
+</tbody>
+</table>
+
+<h2>Character Statistics</h2>
+<p>The character statistics begin with 2-character identifier:</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="10%">Byte Position</th>
+    <th width="10%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">765</td>
+    <td align="middle">2 <tt>char</tt>s</td>
+    <td>The string identifier &quot;<tt>gf</tt>&quot;.</td>
+  </tr>
+</tbody>
+</table>
+<p>From this point on, the contents of the file are variable, because character stats are stored in packed format
+and certain stats may be absent (if the stat is absent in the save file, its value is 0.</p>
+<p>Starting from patch version 1.10 Diablo II stores stats differently than it used to be in previous game version.
+Every character stat is stored as a two-value pair. These pairs (and even the values inside them are not
+byte-aligned. They may start in the middle of one byte, and continue to the second.
+Here is the basic structure of the pair (note that field sizes are given in bits):</p>
+<table width="100%" border="1">
+<thead>
+  <tr>
+    <th align="middle" width="10%">Field Size</th>
+    <th align="middle" width="90%">Description</th>
+  </tr>
+</thead>
+<tbody>
+  <tr>
+    <td align="middle">9</td>
+    <td>Stat Id. This field determines the stat whose value is stored in the value-pair and, more importantly,
+      the size of the next field in the pair.</td>
+  </tr>
+  <tr>
+    <td align="middle"><i>variable</i></td>
+    <td>The value that is to be assigned to the corresponding stat. The size of the field, in bits,
+      is determined by the stat itself. Read on to find out where this information can be obtained.</td>
+  </tr>
+</tbody>
+</table>
+<p>The stats list is terminated by the 9-bit value of <tt>0x1FF</tt> (all 9 bits are set),
+i.e. the entire list is read in a loop, where you read the Id first and, if that Id is <tt>0x1FF</tt>,
+you exit the loop, otherwise you read the next <i>n</i> bits as a stat value and repeat the loop.</p>
+<p>The Ids of stats (and sizes of values) are determined by the data-tables normally stored inside
+the game archive (the MPQ files). The file for this specific purpose is named <tt>ItemStatCost.txt</tt>,
+which is a kind of CSV file, but with tabulation characters used as separators instead of commas.
+The game actually uses the <tt>ItemStatCost.bin</tt> one, which is sort of a compiled version
+of the corresponding text file.</p>
+<p>Here is an Excel-formatted <a href="ItemStatCost.xlsx">ItemStatCost.xlsx</a> file that contains
+the data for 1.13d patch with some nice formatting and extra comments. This file actually contains
+data from two tables, the one needed for the purpose of reading character stats is given on the <b>ItemStatCost</b> sheet.</p>
+<p>The column <b>ID</b> specifies the Id of the stat, as stored in the 9-bit field of the two-value pair.
+The row containing that Id describes the stat. There is a textual name of the stat in the <b>Stat</b> column,
+as well as the size of the value, in bits, that follows the Id in the two-value pair. This size is specified
+by the <b>CSvBits</b> column. Only values that have value <b>1</b> in the <b>Saved</b> column (first 16 stats)
+are actually saved in the character stats section of the save file.</p>
+<p>The stats described by the <b>ItemStatCost</b> table are as follows (in table below Stat Name corresponds
+to the value in the <b>Stat</b> column from the data table):</p>
+
+<table width="100%" border="1">
+<thead>
+  <tr>
+    <th width="10%">Stat Name</th>
+    <th width="90%">Details</th>
+  </tr>
+</thead>
+<tbody>
+  <tr>
+    <td align="middle">strength</td>
+    <td rowspan="4">These stats are self-explanatory. They are always present.</td>
+  </tr>
+  <tr><td align="middle">energy</td></tr>
+  <tr><td align="middle">dexterity</td></tr>
+  <tr><td align="middle">vitality</td></tr>
+  <tr>
+    <td align="middle">statpts</td>
+    <td>The number of Stat Points earned but not distributed.
+      This stat may be absent from the save file if you have distibuted all stat points.</td>
+  </tr>
+  <tr>
+    <td align="middle">newskills</td>
+    <td>The number of Skill Choices earned but not distributed.
+      This stat may be absent from the save file if you have distibuted all skill points.</td>
+  </tr>
+  <tr>
+    <td align="middle">hitpoints</td>
+    <td>Current amount of Life points.
+      <p><!-- @ --></p>
+      <div>These 6 stats are (usually) always present. (There is
+      an exception: if your character is dead, the current Life stat will be
+      gone!) <u>They are also <i>not</i> plain integer values!</u>
+      Instead, each field is a fixed-point binary number, with a 24-bit integer
+      part and an 8-bit fraction part. For example, if the Current Life
+      stat contains the value 0x020AC0, then to get the amount of life
+      remaining you take that value and divide by 256.0 to get 522.75
+      (rounding the number to an integer for display. Note that the
+      current amount of Life, Mana or Stamina may be more than the base amount,
+      because the base does not take into account any blessings bestowed by
+      magical items you are carrying.</div></td>
+  </tr>
+  <tr>
+    <td align="middle">maxhp</td>
+    <td>Base amount of Life points.</td>
+  </tr>
+  <tr>
+    <td align="middle">mana</td>
+    <td>Current amount of Mana points.</td>
+  </tr>
+  <tr>
+    <td align="middle">maxmana</td>
+    <td>Base amount of Mana points.</td>
+  </tr>
+  <tr>
+    <td align="middle">stamina</td>
+    <td>Current amount of Stamina points.</td>
+  </tr>
+  <tr>
+    <td align="middle">maxstamina</td>
+    <td>Base amount of Stamina points.</td>
+  </tr>
+  <tr>
+    <td align="middle"><a name="stats_level">level</a></td>
+    <td>Your character's level. This value must be in the range 1-99
+      (and is therefore always present, even on a new character, with
+      a <a href="#new_character_small_file">minor exception</a>) and should be
+      the same as <a href="#header_level">byte 43</a> in the file header.</td>
+  </tr>
+  <tr>
+    <td align="middle">experience</td>
+    <td>The amount of experience your character has. If you haven't
+      killed a single monster in the game, your experience will be 0, and this
+      field is not stored. Otherwise, this field is always present.</td>
+  </tr>
+  <tr>
+    <td align="middle">gold</td>
+    <td>The amount of gold you are carrying with you (in your inventory or backpack).
+      Just as a helpful reminder, the maximum amount of gold you may carry is directly
+      proportional to your level, at 10,000 gold per level. Thus, a new character can only
+      carry 10,000 gold pieces, but a level 99 character (the maximum) can carry nearly
+      a million in gold (990,000).</td>
+  </tr>
+  <tr>
+    <td align="middle">goldbank</td>
+    <td>The amount of gold you have stowed away (in stash). Just as a helpful
+      reminder, starting from the 1.13c patch onwards, the maximum amount of gold
+      in your stash does not depend on your character's level, and is now a flat
+      cap of 2,500,000 instead.</td>
+  </tr>
+</tbody>
+</table>
+<p>As it was specified above, the stats list is terminated with a stat Id with a special meaning
+(the Id has value <tt>0x1FF</tt> in this case), and the stat value for this stat Id is not stored
+(you may view it as a stat whose stat value is 0 bits in size). After that the remaining bits are
+padded with 0-bits to the nearest byte-boundary so that the next section is byte-aligned.</p>
+
+<h2><a name="skills">Character Skills</a></h2>
+<p>The character skills section begins with the 2-character header,
+&quot;<tt>if</tt>&quot;. This is followed by 30 bytes, each byte corresponding to
+one of the character's special skills. To save space, Trevin listed the skills
+in a <a href="Skills.html">separate table</a>.</p>
+
+<h2><a name="item_list">Item List</a></h2>
+<p>The next major section of the save file is the item list. It begins with the following header:</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">2 <tt>char</tt>s</td>
+    <td>The string identifier &quot;<tt>JM</tt>&quot;.</td>
+  </tr>
+  <tr>
+    <td align="middle"><tt>short</tt></td>
+    <td>The number of items your character has. This includes items
+      equipped, tucked in your belt, stored in your inventory, stored in your
+      stash, and hidden in the Horadric Cube. It does <em>not</em>,
+      however, include gems, runes, or jewels which have been inserted into a
+      socketed item. (Those are counted as part of the item.)</td>
+  </tr>
+</tbody>
+</table>
+<p>This header is followed by a list of items. The format of the items is described
+on the <a href="Item_Format.xhtml">Item Format</a> page.</p>
+<p>After the list of items, you will find another item list header similar to
+the one shown above; only this time the item count will be either 0 or 1. The value 0
+means that your character is currently alive. If the value is 1, then that means
+your character is dead (if you load this save, a corpse will be lying at your feet in town),
+in which case 12 bytes of <i>(unknown)</i> data will follow, after which there will be
+another items list header (the one with the identifier &quot;<tt>JM</tt>&quot; and item count)
+and item list for items on your corpse. Sadly, the meaning of the 12 bytes is unknown.</p>
+<p>If you have an Expansion character, then the corpse item list (if there is one) will be
+followed by the 2-character identifier &quot;<tt>jf</tt>&quot;. If <em>and only
+if</em> you have a mercenary (alive or dead), this header is followed by an item
+list header and (possibly empty) item list containing items equipped on the
+mercenary. This item list is followed by the 2-character trailer &quot;<tt>kf</tt>&quot;.</p>
+<p>If you have a necromancer, it is possible for you to have an Iron Golem that
+is preserved when your game is saved and restored. The Iron Golem is based on an
+item. Following the mercenary item list, there will be a single byte that is <tt>0x00</tt>
+if there is no golem, or <tt>0x01</tt> if there is. If there is a golem, this byte is
+followed by a single item.</p>
+</body>
+</html>
+-------------------------------------------------------------------------------
+originally extracted from here:
+http://www.coreyh.org/diablo-2-files/documentation/d2s_save_file_format_1.13d.html
+-------------------------------------------------------------------------------
+
+
+                        Diablo II Save Game File Format
+
+                      for Diablo II Expansion Set v1.13d
+
+                             Updated July 1, 2012
+
+This page was originally written by Trevin Beattie, whose site is no more (his
+latest version of this page is available here though).
+Now this page is maintained by me, Yuri Sakhno (George1).
+
+Introduction
+
+This page describes the format of saved game files for the game Diablo II
+Expansion Set v1.13d. While the information presented here is mostly aplicable
+to earlier versions of the game, there were some drastic changes in version
+1.10 (particularly, in how character stats are saved), so if you intend to read
+files of the versions of the game erlier than that, you would probably be
+better off opening that save in some recent version of the game and then saving
+it again (upgrading the saved game file).
+
+(Note: all values larger than a byte are stored in x86 little-endian order —
+i.e., least significant byte first. A "short" is 2 bytes long, and a "long" is
+4 bytes long. Values starting with "0x" are given in hexadecimal notation;
+otherwise they are decimal.)
+
+File Header
+
+Each save file starts with a file header. Depending on the circumstances, this
+may be the only section present in saved game file.
+
+┌────────┬──────┬─────────────────────────────────────────────────────────────────┐
+│  Byte  │ Size │                            Contents                             │
+│Position│      │                                                                 │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│0       │long  │File identifier. This must be the value 0xAA55AA55.              │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │File version. The following values are known:                    │
+│        │      │    0x47  v1.00 through v1.06                                    │
+│        │      │    0x57  v1.07 or Expansion Set v1.08                           │
+│        │      │    0x59  standard game v1.08                                    │
+│4       │long  │    0x5C  v1.09 (both the standard game and the Expansion        │
+│        │      │Set.)                                                            │
+│        │      │    0x60  v1.10 and above                                        │
+│        │      │As it was outlined above, this document only covers version      │
+│        │      │0x60 of the file format.                                         │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│8       │long  │Size of the file, in bytes.                                      │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │Checksum of the netire save file. If you attempt to hack the     │
+│        │      │file without storing the correct checksum afterwards, your       │
+│        │      │game will fail to load. Fortunately, the checksum algorithm is   │
+│12      │long  │very simple. After clearing the checksum field, you add up the   │
+│        │      │values of all the bytes in the file, rotating the running        │
+│        │      │total one bit to the left before adding each byte. Then store    │
+│        │      │the result in this field.                                        │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│16      │long  │Active arms. Determines which weapon set is currently active.    │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │Character name. The name may be up to 15 characters long; the    │
+│        │      │rest of the field must be padded with null-characters.           │
+│        │16    │Remember the rules for Diablo II character names: 2-15           │
+│20      │chars │characters, containing only upper and lower case letters         │
+│        │      │(A-Z), with the possible addition of one dash ( - ) or           │
+│        │      │underscore ( _ ) as long as it is not the first or last          │
+│        │      │character of the name.                                           │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │Character status. This is a bit field:                           │
+│        │      │┌────┬────┬─────────┬───────┬────┬────────┬────┬────┐            │
+│        │      ││ 7  │ 6  │    5    │   4   │ 3  │   2    │ 1  │ 0  │            │
+│        │      │├────┴────┼─────────┼───────┼────┼────────┼────┴────┤            │
+│        │      ││unknown  │Expansion│unknown│Died│Hardcore│unknown  │            │
+│        │      ││         │Character│       │    │        │         │            │
+│36      │byte  │└─────────┴─────────┴───────┴────┴────────┴─────────┘            │
+│        │      │Note: the "died" bit indicates that your character has died at   │
+│        │      │some point in the past. It is never cleared when you resume      │
+│        │      │the game. To find out whether your character is currently        │
+│        │      │dead, you need to look in the item list below to see if there    │
+│        │      │is some corpse data. Obviously, if you have a hardcore           │
+│        │      │character and this bit is set, you won't be able to play the     │
+│        │      │game with that charcter anymore.                                 │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │Character progression. This number tells (sort of) how many      │
+│        │      │acts you have completed from all difficulty levels. It appears   │
+│        │      │to be incremented when you kill the final demon in an act —      │
+│        │      │i.e., Andarial, Duriel, Mephisto, and Diablo / Baal. There's a   │
+│        │      │catch to that last one: in an Expansion game, the value is not   │
+│        │      │incremented after killing Diablo, but is incremented by 2        │
+│        │      │after killing Baal. (The reason is unknown.) So it skips the     │
+│        │      │values 4, 9, and 14.                                             │
+│        │      │                                                                 │
+│        │      │I believe this value is used in determining your character's     │
+│        │      │title. The title is one of the following values (depending on    │
+│37      │byte  │the character class' gender):                                    │
+│        │      │                                                                 │
+│        │      │Value  Standard   Hardcore  Value Expansion   Hardcode           │
+│        │      │                                             Expansion           │
+│        │      │0-3   (no title)            0-3   (no title)                     │
+│        │      │4-7   Sir / Dame Count /    5-8   Slayer     Destroyer           │
+│        │      │                 Countess                                        │
+│        │      │8-11  Lord /     Duke /     10-13 Champion   Conqueror           │
+│        │      │      Lady       Duchess                                         │
+│        │      │      Baron /    King /           Patriarch                      │
+│        │      │12    Baroness   Queen      15    /          Guardian            │
+│        │      │                                  Matriarch                      │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│38      │2     │unknown; probably some kind of padding                           │
+│        │bytes │                                                                 │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │Character class. The defined classes are:                        │
+│        │      │     0x00  Amazon                                                │
+│        │      │     0x01  Sorceress                                             │
+│40      │byte  │     0x02  Necromancer                                           │
+│        │      │     0x03  Paladin                                               │
+│        │      │     0x04  Barbarian                                             │
+│        │      │     0x05  Druid (Expansion character only)                      │
+│        │      │     0x06  Assassin (Expansion character only)                   │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│41      │2     │unknown; I've only seen the values { 16, 30 } here.              │
+│        │bytes │                                                                 │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │Character's level. This is the level shown on the character      │
+│43      │byte  │selection screen, but it should equal the level given in the     │
+│        │      │character statistics section.                                    │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│44      │long  │unknown                                                          │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │Time stamp. This is in the standard time() format of the         │
+│48      │long  │number of seconds which have elapsed since midnight, January     │
+│        │      │1, 1970 (UTC).                                                   │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│52      │long  │unknown                                                          │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │These are the skill Ids assigned to the hotkeys for Skill 1      │
+│        │      │through Skill 16. If a skill hotkey is not assigned to a         │
+│56      │16    │skill, the value is 0xFFFF.                                      │
+│        │longs │                                                                 │
+│        │      │Hotkey definitions are stored in the character.key file. The     │
+│        │      │structure of that file is not covered by this document.          │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│120     │long  │The action assigned to the left mouse button. The value of       │
+│        │      │this field is a skill Id.                                        │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│124     │long  │The action assigned to the right mouse button. The value of      │
+│        │      │this field is also a skill Id.                                   │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │In an Expansion character, the action assigned to the            │
+│128     │long  │alternate left mouse button. (The button assignments are         │
+│        │      │swapped when you swap weapons.)                                  │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│132     │long  │In an Expansion character, the action assigned to the            │
+│        │      │alternate right mouse button.                                    │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│136     │32    │unknown                                                          │
+│        │bytes │                                                                 │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │These bytes indicate which difficulty the character is           │
+│        │      │playing. The first byte corresponds to Normal, the second        │
+│        │      │Nightmare, and the third Hell. If the value is zero, the         │
+│        │      │character is not playing at that level. Otherwise, the value     │
+│        │      │looks like this:                                                 │
+│168     │3     │┌──────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┐               │
+│        │bytes ││  7   │  6  │  5  │  4  │  3  │  2  │  1  │  0  │               │
+│        │      │├──────┼─────┴─────┴─────┴─────┼─────┴─────┴─────┤               │
+│        │      ││      │                       │Which Act the    │               │
+│        │      ││Active│unknown                │character is in  │               │
+│        │      ││      │                       │(0-4)            │               │
+│        │      │└──────┴───────────────────────┴─────────────────┘               │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │Map Id. This value looks like a random number, but it            │
+│171     │long  │corresponds with one of the longs found in the character.map     │
+│        │      │file, according to the difficulty being played.                  │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│175     │short │unknown                                                          │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│177     │short │If your Expansion character has a mercenary who is currently     │
+│        │      │dead, this field is non-zero.                                    │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │This looks like a random Id for your mercenary. It is 0 if you   │
+│        │      │have never had a mercenary. If your mercenary has died or (in    │
+│179     │long  │the standard game) been left behind when you move on to the      │
+│        │      │next act, this field is still set to the last mercenary you      │
+│        │      │had.                                                             │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │This is a numerical index into the game's language-dependent     │
+│        │      │string table for mercenary names. There is a separate list for   │
+│183     │short │each type of mercenary (Rogue Scout, Desert Mercenary, Eastern   │
+│        │      │Sorceror, and Barbarian). Trevin wrote a list of mercenary       │
+│        │      │names for the English 1.09 patch.                                │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│        │      │This code determines the difficulty level and act where your     │
+│185     │short │mercenary was found, as well as the attribute of your            │
+│        │      │mercenary (i.e. Cold, Fire, Lightning). Trevin wrote a list of   │
+│        │      │the mercenary codes appended to the end of the mercenary name.   │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│187     │long  │Your mercenary's experience points.                              │
+├────────┼──────┼─────────────────────────────────────────────────────────────────┤
+│191     │144   │unknown                                                          │
+│        │bytes │                                                                 │
+└────────┴──────┴─────────────────────────────────────────────────────────────────┘
+
+For the newly-created character, this is the only information present in the
+file (i.e. the file consists of just the header). The save file is extended
+(all other sections added) when you exit the game (even if you haven't done
+anything in it), but the very first save created by the game (i.e. right after
+you click the OK button on the character-creation screen) will be the save with
+just the header present. Such a save is still a legitimate save, which the game
+can successfully load.
+
+Quest Completion Data
+
+The quest data begins with the following header:
+
+┌────────┬───────┬────────────────────────────────────────────────────────────┐
+│  Byte  │ Size  │                          Contents                          │
+│Position│       │                                                            │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│335     │4 chars│The string identifier "Woo!".                               │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│339     │6 bytes│unknown; there are values { 0x06, 0x00, 0x00, 0x00, 0x2A,   │
+│        │       │0x01 } always present here.                                 │
+└────────┴───────┴────────────────────────────────────────────────────────────┘
+
+The header is followed by three structures, one for each difficulty level. Note
+that the byte offsets given here are offsets into the structure; the first
+structure is at offset 345 in the file, the second one is at offset 441, and
+the third one at 537. You have to add the offsets from the table to these
+values to get the actual offset in the file for the corresponding field for the
+specific difficulty level.
+
+Although there is some variation in the meaning of the bits per quest, some of
+the bits appear to have constant meaning.
+
+Bit 0 indicates the quest is complete. If bit 0 is not set but the rest of the
+field is non-zero, then the quest has been started, but not finished.
+
+Bit 1 generally means you have completed the requirements for the quest (i.e.,
+killed the boss demon), and all that's left is to collect the reward — for
+example, "Charsi will imbue an item with magical power." Not all quests have
+this option. If this bit is set, bit 0 must be cleared.
+
+Bit 2 is often set when an NPC gives you a quest.
+
+Bit 12 is set when you have seen the swirling fire animation that closes a
+quest icon.
+
+Bit 13 indicates the quest was completed in the current game; when you save the
+game and then reload it, all bit 13's are cleared.
+
+┌────────┬───────┬────────────────────────────────────────────────────────────┐
+│  Byte  │ Size  │                          Contents                          │
+│Position│       │                                                            │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│0       │short  │This field contains a 1 if you have been introduced (by     │
+│        │       │Warriv) to Act I.                                           │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │These fields contain quest completion data for each quest in│
+│        │       │Act I.                                                      │
+│        │       │┌──────┬───────────────────┬───────────────────────────────┐│
+│        │       ││short │       Quest       │             Notes             ││
+│        │       ││  #   │                   │                               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││0     │Den of Evil        │Bit 4 is set when you enter the││
+│        │       ││      │                   │Den.                           ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││1     │Sisters' Burial    │Bit 4 is set when you enter the││
+│        │       ││      │Grounds            │Burial Grounds.                ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││2     │Tools of the Trade │Bit 6 is set when you pick up  ││
+│        │       ││      │                   │the Horadric Malus.            ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││      │                   │Bit 4 is set when you enter    ││
+│        │       ││      │                   │Tristram.                      ││
+│        │       ││      │                   │Bit 10 indicates whether you   ││
+│        │       ││      │                   │have completed the secret Cow  ││
+│2       │6      ││      │                   │Level ("Moo"). If you want to  ││
+│        │shorts ││      │                   │fight the Cow King again, just ││
+│        │       ││      │                   │clear this bit!                ││
+│        │       ││3     │The Search for Cain│If you enter Act II without    ││
+│        │       ││      │                   │rescuing Deckard Cain, bit 14  ││
+│        │       ││      │                   │will get set. You will not be  ││
+│        │       ││      │                   │able to rescue Cain yourself;  ││
+│        │       ││      │                   │the Rogues will have done it   ││
+│        │       ││      │                   │instead, and as a consequence, ││
+│        │       ││      │                   │you will be charged a fee if   ││
+│        │       ││      │                   │you want Cain to identify items││
+│        │       ││      │                   │for you.                       ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││      │                   │Bit 2 is set when you read the ││
+│        │       ││4     │The Forgotten Tower│Moldy Tome.                    ││
+│        │       ││      │                   │Bit 6 is set when you enter the││
+│        │       ││      │                   │Forgotten Tower.               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││5     │Sisters to the     │                               ││
+│        │       ││      │Slaughter          │                               ││
+│        │       │└──────┴───────────────────┴───────────────────────────────┘│
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│14      │short  │uncertain; perhaps this gets set to a non-zero value after  │
+│        │       │you travel from Act I to Act II.                            │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│16      │short  │This field contains a 1 if you have been introduced (by     │
+│        │       │Jerhyn) to Act II.                                          │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │These fields contain quest completion data for each quest in│
+│        │       │Act II.                                                     │
+│        │       │┌──────┬───────────────────┬───────────────────────────────┐│
+│        │       ││short │       Quest       │             Notes             ││
+│        │       ││  #   │                   │                               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││0     │Radament's Lair    │Bit 4 is set when you find     ││
+│        │       ││      │                   │Radament.                      ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││      │                   │Bit 4 is set when Cain tells   ││
+│        │       ││      │                   │you about the Viper Amulet.    ││
+│        │       ││      │                   │Bit 5 is set when Cain tells   ││
+│        │       ││1     │The Horadric Staff │you about the Staff of Kings.  ││
+│        │       ││      │                   │Bit 10 is set when Cain tells  ││
+│        │       ││      │                   │you about the Horadric Staff.  ││
+│        │       ││      │                   │Bit 11 is set when you make the││
+│        │       ││      │                   │Horadric Staff.                ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││      │                   │Bit 2 is set when the sun goes ││
+│        │       ││2     │Tainted Sun        │out.                           ││
+│18      │6      ││      │                   │Bit 3 is set when Drognan tells││
+│        │shorts ││      │                   │you why.                       ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││3     │Arcane Sanctuary   │                               ││
+│        │       │├──────┼───────────────────┤                               ││
+│        │       ││4     │The Summoner       │                               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││      │                   │Bit 3 is set when you talk to  ││
+│        │       ││      │                   │Tyrael.                        ││
+│        │       ││      │                   │Bit 4 is set when you talk to  ││
+│        │       ││      │                   │Jerhyn (after killing Duriel). ││
+│        │       ││      │                   │Bit 5 is set when you kill     ││
+│        │       ││      │                   │Duriel.                        ││
+│        │       ││5     │The Seven Tombs    │Bit 6 is set when Atma         ││
+│        │       ││      │                   │congratulates you.             ││
+│        │       ││      │                   │Bit 7 is set when Warriv       ││
+│        │       ││      │                   │congratulates you.             ││
+│        │       ││      │                   │Bit 8 is set by Drognan.       ││
+│        │       ││      │                   │Bit 9 is set by Lysander.      ││
+│        │       ││      │                   │Bit 10 is set by Cain.         ││
+│        │       ││      │                   │Bit 11 is set by Fara.         ││
+│        │       │└──────┴───────────────────┴───────────────────────────────┘│
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│30      │short  │uncertain; perhaps this gets set to a non-zero value after  │
+│        │       │you travel from Act II to Act III.                          │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│32      │short  │This field contains a 1 if you have been introduced (by     │
+│        │       │Hratli) to Act III.                                         │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │These fields contain quest completion data for each quest in│
+│        │       │Act III.                                                    │
+│        │       │┌──────┬───────────────────┬───────────────────────────────┐│
+│        │       ││short │       Quest       │             Notes             ││
+│        │       ││  #   │                   │                               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││0     │Lam Esen's Tome    │                               ││
+│        │       │├──────┼───────────────────┤                               ││
+│        │       ││1     │Khalim's Will      │                               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││      │                   │Bit 2 is set when you pick up  ││
+│        │       ││2     │Blade of the Old   │the Gidbinn.                   ││
+│        │       ││      │Religion           │Bit 3 is set when Hratli asks  ││
+│        │       ││      │                   │you to find the Gidbinn.       ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │6      ││      │                   │Bit 2 is set when Cain tells   ││
+│34      │shorts ││      │                   │you about the Jade Figurine.   ││
+│        │       ││      │                   │Bit 4 is set when Cain tells   ││
+│        │       ││      │                   │you about the Golden Bird.     ││
+│        │       ││      │                   │Bit 5 is set when you are given││
+│        │       ││3     │The Golden Bird    │the Potion of Life, and cleared││
+│        │       ││      │                   │again when you drink the       ││
+│        │       ││      │                   │Potion. (This prevents you from││
+│        │       ││      │                   │drinking more than one in a    ││
+│        │       ││      │                   │game.)                         ││
+│        │       ││      │                   │Bit 6 is set when you find the ││
+│        │       ││      │                   │Jade Figurine.                 ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││4     │The Blackened      │                               ││
+│        │       ││      │Temple             │                               ││
+│        │       │├──────┼───────────────────┤                               ││
+│        │       ││5     │The Guardian       │                               ││
+│        │       │└──────┴───────────────────┴───────────────────────────────┘│
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│46      │short  │uncertain; perhaps this gets set to a non-zero value after  │
+│        │       │you travel from Act III to Act IV.                          │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│48      │short  │This field contains a 1 if you have been introduced to Act  │
+│        │       │IV.                                                         │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │These fields contain quest completion data for each quest in│
+│        │       │Act IV. Note that there are only three quests here, as      │
+│        │       │opposed to 6 for the first three Acts.                      │
+│        │       │┌──────┬───────────────────┬───────────────────────────────┐│
+│        │       ││short │       Quest       │             Notes             ││
+│        │       ││  #   │                   │                               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││0     │The Fallen Angel   │                               ││
+│50      │6      │├──────┼───────────────────┤                               ││
+│        │shorts ││1     │Terror's End       │                               ││
+│        │       │├──────┼───────────────────┤                               ││
+│        │       ││2     │Hell's Forge       │                               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││      │                   │It looks like quest data for   ││
+│        │       ││3-5   │unused             │Act IV still has place for 6   ││
+│        │       ││      │                   │quests, despite the fact that  ││
+│        │       ││      │                   │this act only has 3.           ││
+│        │       │└──────┴───────────────────┴───────────────────────────────┘│
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │uncertain; perhaps this gets set to a non-zero value after  │
+│62      │short  │you travel from Act IV to Act V in an Expansion game, but   │
+│        │       │this assumption has not been verified yet.                  │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│64      │short  │unknown; in an Expansion character, this was set to 1 after │
+│        │       │completing Terror's End and talking to Cain in act IV.      │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│66      │2      │unknown                                                     │
+│        │shorts │                                                            │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │These fields contain quest completion data for each quest in│
+│        │       │Act V.                                                      │
+│        │       │┌──────┬───────────────────┬───────────────────────────────┐│
+│        │       ││short │       Quest       │             Notes             ││
+│        │       ││  #   │                   │                               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││      │                   │Bit 3 is set when you find     ││
+│        │       ││0     │Siege on Harrogath │Shenk.                         ││
+│        │       ││      │                   │Bit 5 is set when Larzuk offers││
+│        │       ││      │                   │to socket an item for you.     ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││1     │Rescue on Mount    │                               ││
+│        │       ││      │Arreat             │                               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││      │                   │Bit 7 is set when you read the ││
+│        │       ││2     │Prison of Ice      │Scroll of Resistance.          ││
+│70      │6      ││      │                   │Bit 8 is set after you rescue  ││
+│        │shorts ││      │                   │Anya and talk to Malah.        ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││3     │Betrayal of        │Bit 4 is set when Anya offers  ││
+│        │       ││      │Harrogath          │to personalize an item for you.││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││4     │Rite of Passage    │                               ││
+│        │       │├──────┼───────────────────┼───────────────────────────────┤│
+│        │       ││      │                   │Bit 4 is set when Larzuk       ││
+│        │       ││      │                   │congratulates you.             ││
+│        │       ││      │                   │Bit 5 is set when Cain         ││
+│        │       ││      │                   │congratulates you.             ││
+│        │       ││5     │Eve of Destruction │Bit 6 is set when Malah        ││
+│        │       ││      │                   │congratulates you.             ││
+│        │       ││      │                   │Bit 7 is set by Tyrael.        ││
+│        │       ││      │                   │Bit 8 is set by Qual-Kehk.     ││
+│        │       ││      │                   │Bit 9 is set by Anya.          ││
+│        │       │└──────┴───────────────────┴───────────────────────────────┘│
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│82      │7      │unknown                                                     │
+│        │shorts │                                                            │
+└────────┴───────┴────────────────────────────────────────────────────────────┘
+
+Waypoints Data
+
+The waypoints data begins with the following header:
+
+┌────────┬───────┬────────────────────────────────────────────────────────────┐
+│  Byte  │ Size  │                          Contents                          │
+│Position│       │                                                            │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│633     │2 chars│The string identifier "WS".                                 │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│635     │6 bytes│unknown; there are values { 0x01, 0x00, 0x00, 0x00, 0x50,   │
+│        │       │0x00 } always present here.                                 │
+└────────┴───────┴────────────────────────────────────────────────────────────┘
+
+The header is followed by three structures, one per each difficulty level. Note
+that the byte offsets given here are offsets into the structure; the first
+structure is at offset 641 in the file, the second one is at offset 665, and
+the third at 689. You have to add the offsets from the table to these values to
+get the actual offset in the file for the corresponding field for the specific
+difficulty level.
+
+┌────────┬───────┬────────────────────────────────────────────────────────────┐
+│  Byte  │ Size  │                          Contents                          │
+│Position│       │                                                            │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│0       │2 bytes│unknown; there are values { 0x02, 0x01 } always present     │
+│        │       │here.                                                       │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │Waypoints. This is a bitfield, with one bit assigned to each│
+│        │       │waypoint in LSB order — so bit 0 in the Rogue Encampment    │
+│        │       │waypoint for Act I. The first waypoint in every Act is      │
+│        │       │activated as soon as you enter that Act. There are 9        │
+│        │       │waypoints (bits) in each of Acts I, II, and III, and 3      │
+│        │       │waypoints (bits) in Act IV, so the last waypoint before     │
+│2       │5 bytes│Diablo (River of Flame) is bit 29 (since we start counting  │
+│        │       │from 0). The first waypoint for Act V follows at bit 30, and│
+│        │       │continues to the last (ninth) waypoint in Act V at bit 38.  │
+│        │       │                                                            │
+│        │       │The first waypoint in each of the difficulty levels is      │
+│        │       │always activated, even if you have never been to that       │
+│        │       │difficulty level.                                           │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│7       │17     │unknown                                                     │
+│        │bytes  │                                                            │
+└────────┴───────┴────────────────────────────────────────────────────────────┘
+
+There is an additional byte value at file offset 713 after the three waypoints
+structures. This byte always has value 0x01 and probably serves as some kind of
+trailer.
+
+NPC Introductions
+
+Trevin's data on the next section was very sketchy, and hasn't improved since
+at all.
+
+┌────────┬───────┬────────────────────────────────────────────────────────────┐
+│  Byte  │ Size  │                          Contents                          │
+│Position│       │                                                            │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│714     │2 chars│The string identifier "w4".                                 │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│716     │1 byte │unknown                                                     │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │You have been introduced to:                                │
+│        │       │┌──────┬────┬──────┬────┬──────┬─────┬─────┬────┐           │
+│717     │1 byte ││  7   │ 6  │  5   │ 4  │  3   │  2  │  1  │ 0  │           │
+│        │       │├──────┼────┼──────┼────┼──────┼─────┼─────┼────┤           │
+│        │       ││Warriv│    │Charsi│    │Kashya│Akara│Gheed│    │           │
+│        │       │└──────┴────┴──────┴────┴──────┴─────┴─────┴────┘           │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │┌─────┬───┬──────┬───────┬────────┬────┬───────┬───┐        │
+│        │       ││  7  │ 6 │  5   │   4   │   3    │ 2  │   1   │ 0 │        │
+│718     │1 byte │├─────┼───┼──────┼───────┼────────┼────┼───────┼───┤        │
+│        │       ││Greiz│   │Meshif│Geglash│Lysander│Fara│Drognan│   │        │
+│        │       │└─────┴───┴──────┴───────┴────────┴────┴───────┴───┘        │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │┌─────┬────┬───────┬────┬────┬─────┬────┬─────┐             │
+│        │       ││  7  │ 6  │   5   │ 4  │ 3  │  2  │ 1  │  0  │             │
+│719     │1 byte │├─────┼────┼───────┼────┴────┼─────┼────┼─────┤             │
+│        │       ││Alkor│    │Asheara│         │Cain │    │Elzix│             │
+│        │       │└─────┴────┴───────┴─────────┴─────┴────┴─────┘             │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │┌─────┬─────┬────┬───────┬──────┬────┬────┬─────┐           │
+│        │       ││  7  │  6  │ 5  │   4   │  3   │ 2  │ 1  │  0  │           │
+│720     │1 byte │├─────┼─────┼────┼───────┼──────┼────┴────┼─────┤           │
+│        │       ││Malah│Anya │    │Natalya│Meshif│         │Ormus│           │
+│        │       │└─────┴─────┴────┴───────┴──────┴─────────┴─────┘           │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │┌────┬────┬────┬────┬────┬────┬─────────┬─────────┐         │
+│        │       ││ 7  │ 6  │ 5  │ 4  │ 3  │ 2  │    1    │    0    │         │
+│721     │1 byte │├────┴────┴────┴────┴────┼────┼─────────┼─────────┤         │
+│        │       ││                        │Cain│Qual-Kehk│Nihlathak│         │
+│        │       │└────────────────────────┴────┴─────────┴─────────┘         │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│722     │3 bytes│unknown                                                     │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│725     │8 bytes│Introductions repeated for Nightmare difficulty.            │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│733     │8 bytes│Introductions repeated for Hell difficulty.                 │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │It would appear that bits 1-6 of byte 741 get set after you │
+│        │       │take the caravan to Act II in Normal difficulty. Bit 7 of   │
+│        │       │byte 741 through bit 1 of byte 743 get set after you sail to│
+│        │       │Act III. On entering Act IV, bits 2, 5, 6, & 7 of byte 743  │
+│        │       │and bits 0, 3, & 4 of byte 744 get set.                     │
+│        │       │                                                            │
+│        │       │When you return to a previous act and talk to the NPC's,    │
+│741     │1 byte │these bits are cleared.                                     │
+│        │       │                                                            │
+│        │       │You have yet to be welcomed back by:                        │
+│        │       │┌──────┬───┬──────┬──────┬──────┬─────┬─────┬───┐           │
+│        │       ││  7   │ 6 │  5   │  4   │  3   │  2  │  1  │ 0 │           │
+│        │       │├──────┼───┼──────┼──────┼──────┼─────┼─────┼───┤           │
+│        │       ││Warriv│?  │Charsi│Warriv│Kashya│Akara│Gheed│   │           │
+│        │       │└──────┴───┴──────┴──────┴──────┴─────┴─────┴───┘           │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │┌─────┬──────┬──────┬───────┬───┬────┬───────┬───┐          │
+│        │       ││  7  │  6   │  5   │   4   │ 3 │ 2  │   1   │ 0 │          │
+│742     │1 byte │├─────┼──────┼──────┼───────┼───┼────┼───────┼───┤          │
+│        │       ││Greiz│Jerhyn│Meshif│Geglash│?  │Fara│Drognan│?  │          │
+│        │       │└─────┴──────┴──────┴───────┴───┴────┴───────┴───┘          │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │┌─────┬──────┬───────┬────┬────┬────┬────┬─────┐            │
+│        │       ││  7  │  6   │   5   │ 4  │ 3  │ 2  │ 1  │  0  │            │
+│743     │1 byte │├─────┼──────┼───────┼────┴────┼────┼────┼─────┤            │
+│        │       ││Alkor│Hratli│Asheara│         │?   │?   │Elzix│            │
+│        │       │└─────┴──────┴───────┴─────────┴────┴────┴─────┘            │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│        │       │┌─────┬─────┬─────┬─────┬─────┬─────┬─────┬─────┐           │
+│        │       ││  7  │  6  │  5  │  4  │  3  │  2  │  1  │  0  │           │
+│744     │1 byte │├─────┴─────┴─────┼─────┼─────┼─────┴─────┼─────┤           │
+│        │       ││                 │?    │?    │           │Ormus│           │
+│        │       │└─────────────────┴─────┴─────┴───────────┴─────┘           │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│745     │4 bytes│unknown                                                     │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│749     │8 bytes│Greetings repeated for Nightmare difficulty.                │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│757     │8 bytes│Greetings repeated for Hell difficulty.                     │
+└────────┴───────┴────────────────────────────────────────────────────────────┘
+
+Character Statistics
+
+The character statistics begin with 2-character identifier:
+
+┌────────┬───────┬────────────────────────────────────────────────────────────┐
+│  Byte  │ Size  │                          Contents                          │
+│Position│       │                                                            │
+├────────┼───────┼────────────────────────────────────────────────────────────┤
+│765     │2 chars│The string identifier "gf".                                 │
+└────────┴───────┴────────────────────────────────────────────────────────────┘
+
+From this point on, the contents of the file are variable, because character
+stats are stored in packed format and certain stats may be absent (if the stat
+is absent in the save file, its value is 0.
+
+Starting from patch version 1.10 Diablo II stores stats differently than it
+used to be in previous game version. Every character stat is stored as a
+two-value pair. These pairs (and even the values inside them are not
+byte-aligned. They may start in the middle of one byte, and continue to the
+second. Here is the basic structure of the pair (note that field sizes are
+given in bits):
+
+┌────────┬────────────────────────────────────────────────────────────────────┐
+│ Field  │                            Description                             │
+│  Size  │                                                                    │
+├────────┼────────────────────────────────────────────────────────────────────┤
+│        │Stat Id. This field determines the stat whose value is stored in the│
+│9       │value-pair and, more importantly, the size of the next field in the │
+│        │pair.                                                               │
+├────────┼────────────────────────────────────────────────────────────────────┤
+│        │The value that is to be assigned to the corresponding stat. The size│
+│variable│of the field, in bits, is determined by the stat itself. Read on to │
+│        │find out where this information can be obtained.                    │
+└────────┴────────────────────────────────────────────────────────────────────┘
+
+The stats list is terminated by the 9-bit value of 0x1FF (all 9 bits are set),
+i.e. the entire list is read in a loop, where you read the Id first and, if
+that Id is 0x1FF, you exit the loop, otherwise you read the next n bits as a
+stat value and repeat the loop.
+
+The Ids of stats (and sizes of values) are determined by the data-tables
+normally stored inside the game archive (the MPQ files). The file for this
+specific purpose is named ItemStatCost.txt, which is a kind of CSV file, but
+with tabulation characters used as separators instead of commas. The game
+actually uses the ItemStatCost.bin one, which is sort of a compiled version of
+the corresponding text file.
+
+Here is an Excel-formatted ItemStatCost.xlsx file that contains the data for
+1.13d patch with some nice formatting and extra comments. This file actually
+contains data from two tables, the one needed for the purpose of reading
+character stats is given on the ItemStatCost sheet.
+
+The column ID specifies the Id of the stat, as stored in the 9-bit field of the
+two-value pair. The row containing that Id describes the stat. There is a
+textual name of the stat in the Stat column, as well as the size of the value,
+in bits, that follows the Id in the two-value pair. This size is specified by
+the CSvBits column. Only values that have value 1 in the Saved column (first 16
+stats) are actually saved in the character stats section of the save file.
+
+The stats described by the ItemStatCost table are as follows (in table below
+Stat Name corresponds to the value in the Stat column from the data table):
+
+┌──────────┬───────────────────────────────────────────────────────────────────┐
+│Stat Name │                              Details                              │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│strength  │                                                                   │
+├──────────┤                                                                   │
+│energy    │                                                                   │
+├──────────┤These stats are self-explanatory. They are always present.         │
+│dexterity │                                                                   │
+├──────────┤                                                                   │
+│vitality  │                                                                   │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│          │The number of Stat Points earned but not distributed. This stat may│
+│statpts   │be absent from the save file if you have distibuted all stat       │
+│          │points.                                                            │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│          │The number of Skill Choices earned but not distributed. This stat  │
+│newskills │may be absent from the save file if you have distibuted all skill  │
+│          │points.                                                            │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│          │Current amount of Life points.                                     │
+│          │                                                                   │
+│          │These 6 stats are (usually) always present. (There is an exception:│
+│          │if your character is dead, the current Life stat will be gone!)    │
+│          │They are also not plain integer values! Instead, each field is a   │
+│          │fixed-point binary number, with a 24-bit integer part and an 8-bit │
+│hitpoints │fraction part. For example, if the Current Life stat contains the  │
+│          │value 0x020AC0, then to get the amount of life remaining you take  │
+│          │that value and divide by 256.0 to get 522.75 (rounding the number  │
+│          │to an integer for display. Note that the current amount of Life,   │
+│          │Mana or Stamina may be more than the base amount, because the base │
+│          │does not take into account any blessings bestowed by magical items │
+│          │you are carrying.                                                  │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│maxhp     │Base amount of Life points.                                        │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│mana      │Current amount of Mana points.                                     │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│maxmana   │Base amount of Mana points.                                        │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│stamina   │Current amount of Stamina points.                                  │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│maxstamina│Base amount of Stamina points.                                     │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│          │Your character's level. This value must be in the range 1-99 (and  │
+│level     │is therefore always present, even on a new character, with a minor │
+│          │exception) and should be the same as byte 43 in the file header.   │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│          │The amount of experience your character has. If you haven't killed │
+│experience│a single monster in the game, your experience will be 0, and this  │
+│          │field is not stored. Otherwise, this field is always present.      │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│          │The amount of gold you are carrying with you (in your inventory or │
+│          │backpack). Just as a helpful reminder, the maximum amount of gold  │
+│gold      │you may carry is directly proportional to your level, at 10,000    │
+│          │gold per level. Thus, a new character can only carry 10,000 gold   │
+│          │pieces, but a level 99 character (the maximum) can carry nearly a  │
+│          │million in gold (990,000).                                         │
+├──────────┼───────────────────────────────────────────────────────────────────┤
+│          │The amount of gold you have stowed away (in stash). Just as a      │
+│goldbank  │helpful reminder, starting from the 1.13c patch onwards, the       │
+│          │maximum amount of gold in your stash does not depend on your       │
+│          │character's level, and is now a flat cap of 2,500,000 instead.     │
+└──────────┴───────────────────────────────────────────────────────────────────┘
+
+As it was specified above, the stats list is terminated with a stat Id with a
+special meaning (the Id has value 0x1FF in this case), and the stat value for
+this stat Id is not stored (you may view it as a stat whose stat value is 0
+bits in size). After that the remaining bits are padded with 0-bits to the
+nearest byte-boundary so that the next section is byte-aligned.
+
+Character Skills
+
+The character skills section begins with the 2-character header, "if". This is
+followed by 30 bytes, each byte corresponding to one of the character's special
+skills. To save space, Trevin listed the skills in a separate table.
+
+Item List
+
+The next major section of the save file is the item list. It begins with the
+following header:
+
+┌───────────────┬─────────────────────────────────────────────────────────────┐
+│     Size      │                          Contents                           │
+├───────────────┼─────────────────────────────────────────────────────────────┤
+│2 chars        │The string identifier "JM".                                  │
+├───────────────┼─────────────────────────────────────────────────────────────┤
+│               │The number of items your character has. This includes items  │
+│               │equipped, tucked in your belt, stored in your inventory,     │
+│short          │stored in your stash, and hidden in the Horadric Cube. It    │
+│               │does not, however, include gems, runes, or jewels which have │
+│               │been inserted into a socketed item. (Those are counted as    │
+│               │part of the item.)                                           │
+└───────────────┴─────────────────────────────────────────────────────────────┘
+
+This header is followed by a list of items. The format of the items is
+described on the Item Format page.
+
+After the list of items, you will find another item list header similar to the
+one shown above; only this time the item count will be either 0 or 1. The value
+0 means that your character is currently alive. If the value is 1, then that
+means your character is dead (if you load this save, a corpse will be lying at
+your feet in town), in which case 12 bytes of (unknown) data will follow, after
+which there will be another items list header (the one with the identifier "JM"
+and item count) and item list for items on your corpse. Sadly, the meaning of
+the 12 bytes is unknown.
+
+If you have an Expansion character, then the corpse item list (if there is one)
+will be followed by the 2-character identifier "jf". If and only if you have a
+mercenary (alive or dead), this header is followed by an item list header and
+(possibly empty) item list containing items equipped on the mercenary. This
+item list is followed by the 2-character trailer "kf".
+
+If you have a necromancer, it is possible for you to have an Iron Golem that is
+preserved when your game is saved and restored. The Iron Golem is based on an
+item. Following the mercenary item list, there will be a single byte that is
+0x00 if there is no golem, or 0x01 if there is. If there is a golem, this byte
+is followed by a single item.
+
+<html>
+<h1 align="center">Diablo II Item Format</h1>
+<h3 align="center">for Diablo II v1.13d Expansion Set: Lord of Destruction</h3>
+<div align="center">Updated June 23, 2012<br/></div>
+<p>This file was originally written by Trevin Beattie, whose site is no more (his latest version of this file is available
+<a href="https://web.archive.org/web/20161225040510/http://web.archive.org/web/20070829095341/http://www.xmission.com/~trevin/DiabloIIv1.09_Item_Format.shtml">here</a> though).</p>
+<h3>Welcome!</h3>
+<p>Thanks for showing an interest in my Diablo II Item Format page. While
+you're browsing, be sure to check out the preview of my <a href="https://web.archive.org/web/20161225040510/http://www.xmission.com/~trevin/DiabloIIv1.09_Editor.shtml">game
+editor</a> for unix+Motif. I currently have the item editor in
+development!</p>
+<h2>Introduction</h2>
+<p>Having searched the web, I found very few references to the Diablo II
+<tt>.d2s</tt> file format, and most of them covered the old (pre-1.08)
+version. Diablo II v1.09 has significantly changed the file format.
+I have started another page which details <a href="Save_File_Format.xhtml">the
+layout of the major parts of the <tt>.d2s</tt> file.</a> This document
+focuses specifically on the item structure &#x2014; all those pieces of the file
+tagged &quot;<tt>JM</tt>&quot;.</p>
+<p>Rather than describe everything in terms of byte offsets, I'm going to define
+the layout as a series of variable-length bit fields. This is a critical
+part of the item format, because the position of many of the fields can change
+depending on what comes before it. If I say a certain value is a 3-bit
+field starting at bit position 150, for example, this translates to bits 6 and 7
+of the byte 18 and bit 0 of byte 19 in the data structure. You can read an
+arbitrary bit field programatically using the following code (in C):</p>
+<pre>#define read_bits(start,size) \
+    ((*((unsigned long *) &amp;data[(start) / 8])
+      &gt;&gt; ((start) &amp; 7)) &amp; ((1 &lt;&lt; (size)) - 1))</pre>
+<h2>Item List Header</h2>
+<p>An item list begins with the following simple header:</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="10%">Byte Position</th>
+    <th width="10%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">0</td>
+    <td align="middle">2 <tt>char</tt>s</td>
+    <td>Identifier string &quot;<tt>JM</tt>&quot; { 0x4A, 0x4D }</td>
+  </tr>
+  <tr>
+    <td align="middle">2</td>
+    <td align="middle">16 bits</td>
+    <td>The number of items your character has. This does not include
+      gems or jewels which have been glued into socketed items.</td>
+  </tr>
+</tbody>
+</table>
+<p>Your item list ends with another 4-byte structure similar to the above,
+except the second field is zero (i.e.,
+{&#xA0;0x4A,&#xA0;0x4D,&#xA0;0x00,&#xA0;0x00&#xA0;}).</p>
+<p>In the Expansion Set, your hireling has his/her own item list. This
+list is separated from yours by the 2-character identifier &quot;<tt>jf</tt>&quot;. This is
+followed by an item list header for the hireling, and then his/her items.
+The second item list is <i>not</i> terminated with the same 4-byte structure as
+the first; instead, it is followed by the 2-character identifier &quot;<tt>kf</tt>&quot;.</p>
+<h2>Item Structure part 1: Simple Items</h2>
+<p>There are still many fields in the item structure which I haven't figured out
+yet, but I'll leave placeholders for them in case I find out what they mean in
+the future. All sizes are in bits unless otherwise specified.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="10%">Bit Position</th>
+    <th width="10%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">0</td>
+    <td align="middle">2 <tt>char</tt>s</td>
+    <td>Identifier string &quot;<tt>JM</tt>&quot; { 0x4A, 0x4D }</td>
+  </tr>
+  <tr>
+    <td align="middle">16</td>
+    <td align="middle">4</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">20</td>
+    <td align="middle">1</td>
+    <td>Item has been identified</td>
+  </tr>
+  <tr>
+    <td align="middle">21</td>
+    <td align="middle">6</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle"><a name="27">27</a></td>
+    <td align="middle">1</td>
+    <td>Item is <a href="#sockets">Socketed</a></td>
+  </tr>
+  <tr>
+    <td align="middle">28</td>
+    <td align="middle">1</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">29</td>
+    <td align="middle">1</td>
+    <td>This bit is set on items which you have picked up since the last time
+      the game was saved. <i>Why?...</i></td>
+  </tr>
+  <tr>
+    <td align="middle">30</td>
+    <td align="middle">2</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">32</td>
+    <td align="middle">1</td>
+    <td>
+      <div>Item is a <a href="#ear">Player Ear</a></div>
+      <div><i>Thanks go to Mike of Denmark for identifying this bit.</i></div></td>
+  </tr>
+  <tr>
+    <td align="middle">33</td>
+    <td align="middle">1</td>
+    <td>"Newbie" item. This bit is set on the weapon and shield your
+      character is given when you start the game. Apparently, this gives
+      the item the property of having a repair cost of 1gp, as well as a sell
+      value of 1gp.</td>
+  </tr>
+  <tr>
+    <td align="middle">34</td>
+    <td align="middle">3</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle"><a name="37">37</a></td>
+    <td align="middle">1</td>
+    <td>
+      <div>Item is simple (only 111 bits {14 bytes} of item data)</div>
+      <div><i>Thanks go to Guillaume Courtin of France for discovering the
+      meaning of this bit.</i></div></td>
+  </tr>
+  <tr>
+    <td align="middle">38</td>
+    <td align="middle">1</td>
+    <td>Item is Ethereal (Cannot be Repaired)</td>
+  </tr>
+  <tr>
+    <td align="middle">39</td>
+    <td align="middle">1</td>
+    <td><i>unknown; this bit is 1 on the items I've looked at</i></td>
+  </tr>
+  <tr>
+    <td align="middle"><a name="40">40</a></td>
+    <td align="middle">1</td>
+    <td>Item has been <a href="#personalized">personalized</a> (by Anya in Act V)</td>
+  </tr>
+  <tr>
+    <td align="middle">41</td>
+    <td align="middle">1</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle"><a name="42">42</a></td>
+    <td align="middle">1</td>
+    <td>It looks like this bit indicates the item has been given a <a href="#runeword">Rune Word</a>.</td>
+  </tr>
+  <tr>
+    <td align="middle">43</td>
+    <td align="middle">15</td>
+    <td><i>unknown; some of these bits may be set</i></td>
+  </tr>
+  <tr>
+    <td align="middle">58</td>
+    <td align="middle">3</td>
+    <td>
+      <div><a name="58">Item location.</a> Actually, I have only seen a few
+      values for these bits, so I'm not 100% certain of its validity. If
+      you see any other value here, let me know what it is and where the item is
+      located.</div>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <td align="middle" width="20%">0</td>
+          <td width="60%">Item is stored (see <a href="#73">bit field 73</a>)</td>
+        </tr>
+        <tr>
+          <td align="middle">1</td>
+          <td>Item is equipped (somewhere on your body)</td>
+        </tr>
+        <tr>
+          <td align="middle">2</td>
+          <td>Item is tucked in your belt (or sash)</td>
+        </tr>
+        <tr>
+          <td align="middle">4</td>
+          <td>Item is being moved (i.e., has been picked up by the mouse).</td>
+        </tr>
+        <tr>
+          <td align="middle">6</td>
+          <td>Item is glued into a socket.</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">61</td>
+    <td align="middle">4</td>
+    <td>
+      <div>If the item is equipped, this field tells where it is. Possible
+      values are:</div>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <td align="middle" width="20%">1</td>
+          <td width="60%">head (helmet)</td>
+        </tr>
+        <tr>
+          <td align="middle">2</td>
+          <td>neck (amulet)</td>
+        </tr>
+        <tr>
+          <td align="middle">3</td>
+          <td>torso (armor)</td>
+        </tr>
+        <tr>
+          <td align="middle">4</td>
+          <td>right hand (weapon)</td>
+        </tr>
+        <tr>
+          <td align="middle">5</td>
+          <td>left hand (shield)</td>
+        </tr>
+        <tr>
+          <td align="middle">6</td>
+          <td>right finger (ring)</td>
+        </tr>
+        <tr>
+          <td align="middle">7</td>
+          <td>left finger (ring)</td>
+        </tr>
+        <tr>
+          <td align="middle">8</td>
+          <td>waist (belt)</td>
+        </tr>
+        <tr>
+          <td align="middle">9</td>
+          <td>feet (boots)</td>
+        </tr>
+        <tr>
+          <td align="middle">10</td>
+          <td>hands (gloves)</td>
+        </tr>
+        <tr>
+          <td align="middle">11</td>
+          <td>alternate right hand (Expansion Set only)</td>
+        </tr>
+        <tr>
+          <td align="middle">12</td>
+          <td>alternate left hand (Expansion Set only)</td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+  </tr>
+  <tr>
+    <td align="middle">65</td>
+    <td align="middle">4</td>
+    <td>
+      <p>Column number of the left corner of the item, counting from 0.
+      Your inventory has ten columns (numbered 0-9), your stash has six, and the
+      Horadric Cube has four.</p>
+      <p><strong>Note:</strong> Your belt is considered (for the purposes of the
+      item format) to have no rows, but either 4, 8, 12, or 16 columns. If
+      you prefer, you can divide this field and use the 2 bits at position 67-68
+      for the row (but only for belts).</p>
+      <p><strong>Note 2:</strong> If the item is equipped, glued to a socket, or
+      in transit, then this field appears to contain old data from the last time
+      the item was stored. I.e., it may be non-zero, but the value is
+      unused.</p></td>
+  </tr>
+  <tr>
+    <td align="middle">69</td>
+    <td align="middle">3</td>
+    <td>
+      <p>Row number of the top of the item, counting from 0. Your
+      inventory has four rows (numbered 0-3), your stash has four in normal
+      characters or eight in Expansion Set characters, and the Horadric Cube has
+      four. (In the belt, this field is always zero.)</p>
+      <p><strong>Note:</strong> If the item is equipped, tucked in your belt,
+      glued to a socket, or in transit, then this field appears to contain old
+      data from the last time the item was stored. I.e., it may be
+      non-zero, but the value is unused.</p></td>
+  </tr>
+  <tr>
+    <td align="middle">72</td>
+    <td align="middle">1</td>
+    <td><i>unknown</i></td>
+  </tr>
+  <tr>
+    <td align="middle">73</td>
+    <td align="middle">3</td>
+    <td>
+      <div><a name="73">Actually</a>, bit 74 seems to always be 0, but since bits
+      73 and 75 are related I just lump them all together. If the item is
+      neither equipped nor in your belt, this field tells where it is.
+      Possible values are:</div>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <td align="middle" width="20%">0</td>
+          <td width="60%">not here <i>(check <a href="#58">bit field 58</a>)</i></td>
+        </tr>
+        <tr>
+          <td align="middle">1</td>
+          <td>inventory</td>
+        </tr>
+        <tr>
+          <td align="middle">4</td>
+          <td>Horadric Cube</td>
+        </tr>
+        <tr>
+          <td align="middle">5</td>
+          <td>stash</td>
+        </tr>
+      </tbody>
+      </table>
+      <div><u>If you find an item having any other value in this field, let me
+      know what the value is and the item's location!</u></div></td>
+  </tr>
+  <tr>
+    <td align="middle">76</td>
+    <td align="middle">4 <tt>char</tt>s<br/>(8 bits ea.)</td>
+    <td><a name="76">Item's type.</a> The type is 3 lower-case letters or
+      numbers followed by a space; e.g., &quot;<tt>amu&#xA0;</tt>&quot; (Amulet) or &quot;<tt>2hs&#xA0;</tt>&quot;
+      (Two-Handed Sword). I have started a list of item identifiers (not
+      posted; sorry), but it is by no means complete; I'm sure I don't even have
+      half of what's out there!<br/><strong>Warning:</strong> This field is
+      <em>not</em> byte-aligned! It starts in the middle of byte 9 and
+      runs to the middle of byte 13.</td>
+  </tr>
+  <tr>
+    <td align="middle">108</td>
+    <td align="middle">3</td>
+    <td>The number of gems (or skulls or jewels) which have been glued to this
+      item (if <a href="#27">socketed</a>).
+      There will be this many additional item structures for the gems
+      immediately following this item, in the order that the gems were inserted.</td>
+  </tr>
+</tbody>
+</table>
+<h2><a name="ear">Item Variant: Player Ears</a></h2>
+<div><i>The following information was provided by Mike of Denmark.</i></div>
+<p>If the item is a Player Ear, its structure is slightly different than the
+Simple Items above. The last two fields in the Simple Item structure are
+replaced by the following:</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="10%">Bit Position</th>
+    <th width="10%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">76</td>
+    <td align="middle">3</td>
+    <td>Character class of the ear's former owner. The defined classes
+      are:<br/>&#xA0;&#xA0;&#xA0;&#xA0; 0&#xA0;
+      Amazon<br/>&#xA0;&#xA0;&#xA0;&#xA0; 1&#xA0;
+      Sorceress<br/>&#xA0;&#xA0;&#xA0;&#xA0; 2&#xA0;
+      Necromancer<br/>&#xA0;&#xA0;&#xA0;&#xA0; 3&#xA0;
+      Paladin<br/>&#xA0;&#xA0;&#xA0;&#xA0; 4&#xA0;
+      Barbarian<br/>&#xA0;&#xA0;&#xA0;&#xA0; 5&#xA0; Druid (Expansion character
+      only)<br/>&#xA0;&#xA0;&#xA0;&#xA0; 6&#xA0; Assassin (Expansion character
+      only)</td>
+  </tr>
+  <tr>
+    <td align="middle">79</td>
+    <td align="middle">7</td>
+    <td>Character level of the ear's former owner.</td>
+  </tr>
+  <tr>
+    <td align="middle">86</td>
+    <td align="middle">7</td>
+    <td>First character of the former owner's name.</td>
+  </tr>
+  <tr>
+    <td align="middle">93</td>
+    <td align="middle">7 &#xD7; <i>N</i>-1</td>
+    <td>Second character of the former owner's name; Repeat until you get the
+      whole name (15 characters maximum).</td>
+  </tr>
+  <tr>
+    <td align="middle">86 + 7 &#xD7; <i>N</i></td>
+    <td align="middle">7</td>
+    <td>0&#xA0; (this indicates the end of the name)</td>
+  </tr>
+</tbody>
+</table>
+<p>Following the end of the name, the rest of the final byte will be padded with
+0's if necessary, and the Player Ear structure ends there.</p>
+<h2>Item Structure part 2: Extended Items</h2>
+<p>By &quot;extended items&quot; I mean any items which are not <a href="#37">simple.</a>
+Simple items are those which need no further information than that given
+above &#x2014; such as gems, potions, and small quest items &#x2014; and their structure length
+is fixed at 14 bytes. Everything else has an extended structure with a
+possibly variable length set of bit fields. First, I'll describe the part
+of the structure that appears to be the same for all extended items. From
+that point on, there will be no more &quot;bit positions&quot;; only &quot;this field follows
+that field, if it exists&quot;.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="10%">Bit Position</th>
+    <th width="10%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">111</td>
+    <td align="middle">32</td>
+    <td>Unique identifier. Diablo II randomly generates a value for this
+      field in order to discourage cheaters from &quot;duping&quot; items.
+      Supposedly, if it detects more than one extended item with the same unique
+      Id, it will delete the duplicates. (It hasn't done that for me in
+      single player mode, though.)</td>
+  </tr>
+  <tr>
+    <td align="middle">143</td>
+    <td align="middle">7</td>
+    <td>
+      <div>This appears to be the item's level; i.e., the level with which the
+      item was created (or 'dropped'). The item level is based on the
+      level of the monster who dropped it, the level of the area you're in if
+      found in a chest, or, in rare cases, your characters level. The item
+      level determines what modifiers are allowed on the item.</div>
+      <div><i>Note: this is just a theory at this point, but it seems to hold
+      for the items I've examined.</i></div></td>
+  </tr>
+  <tr>
+    <td align="middle">150</td>
+    <td align="middle">4</td>
+    <td>
+      <div>Item quality. This field can be one of the following values,
+      which determines the quality-specific bit fields that follow:</div>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <td align="middle" width="20%">1</td>
+          <td width="60%"><a href="#low_quality">low quality</a></td>
+        </tr>
+        <tr>
+          <td align="middle">2</td>
+          <td><a href="#normal_data">normal</a></td>
+        </tr>
+        <tr>
+          <td align="middle">3</td>
+          <td><a href="#high_quality">high quality</a></td>
+        </tr>
+        <tr>
+          <td align="middle">4</td>
+          <td><a href="#magic_data">magically enhanced</a></td>
+        </tr>
+        <tr>
+          <td align="middle">5</td>
+          <td><a href="#set_data">part of a set</a></td>
+        </tr>
+        <tr>
+          <td align="middle">6</td>
+          <td><a href="#rare_data">rare</a></td>
+        </tr>
+        <tr>
+          <td align="middle">7</td>
+          <td><a href="#unique_data">unique</a></td>
+        </tr>
+        <tr>
+          <td align="middle">8</td>
+          <td><a href="#crafted_data">crafted</a></td>
+        </tr>
+      </tbody>
+      </table>
+      <div><i>Thanks go to Guillaume Courtin of France for finding the value of
+      crafted items.</i></div></td>
+  </tr>
+</tbody>
+</table>
+<h2 align="center">WARNING: DATA BELOW THIS POINT MAY CONTAIN ERRORS</h2>
+<h3><a name="ring_data">Ring Data</a></h3>
+<p>After the above data, if the item is a ring, amulet, jewel, or charm, then it
+has a 1 bit followed by three more bits. All other items (that I've seen)
+have just a single 0 bit.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th colspan="2">Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td colspan="2">If this bit is set, the item has one of multiple pictures
+      associated with it; the next field determines which picture a particular
+      item uses. If this bit is 0, the next field is absent. The
+      picture field is used for rings, amulets, jewels, and charms.</td>
+  </tr>
+  <tr>
+    <td align="middle">3</td>
+    <td>Picture. <i>Optional; only present if the previous bit is 1.</i>
+      This field chooses the particular graphic used to display the ring.</td>
+    <td width="179"><img height="75" src="/web/20161225040510im_/http://www.coreyh.org/diablo-2-files/documentation/images/Ring_of_the_Leech.jpg" width="179"/></td>
+  </tr>
+</tbody>
+</table>
+<p>From this point on, my information is very iffy.</p>
+<h3><a name="unknown_11bit_data"><i>Unknown Field</i></a></h3>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>This bit apparently is set for certain class-specific Expansion Set
+      items. It indicates the presence of the next 11-bit field. If
+      this bit is 0, the next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>
+      <div><i>Credit for the discovery of this field's meaning goes entirely to
+      Guillaume Courtin of France. Thanks!</i></div>
+      <div>This field indicates magic properties which are inherent in certain
+      class-specific items. A given class-specific item will (almost)
+      always start with the same set of properties, even if its quality is
+      &quot;normal&quot;. Other quality ratings may add more properties to the
+      standard set. It appears that items which will have this field
+      are:</div>
+      <ul>
+        <li>Amazon-only bows, spears, and javelins</li>
+        <li>Voodoo heads (Necromancer-only shields)</li>
+        <li>Paladin-only shields</li>
+        <li>Orbs (Sorceress-Only wands)</li></ul></td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="low_quality">Low Quality Item Data</a></h3>
+<p>If the item is one of low quality, it has 3 more bits that give the quality
+details:</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th colspan="2">Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">3</td>
+    <td>
+      <div>Quality:</div>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <td align="middle" width="20%">0</td>
+          <td width="60%">Crude</td>
+        </tr>
+        <tr>
+          <td align="middle">1</td>
+          <td>Cracked</td>
+        </tr>
+        <tr>
+          <td align="middle">2</td>
+          <td>Damaged</td>
+        </tr>
+        <tr>
+          <td align="middle">3</td>
+          <td>Low Quality</td>
+        </tr>
+      </tbody>
+      </table>
+      <div><i>I haven't recorded any instances of other values, but that doesn't
+      mean there won't be any. Also, I'm certain the value has something
+      to do with mods on an item's inherent (non-recorded) properties, such as
+      weapon damage, but I haven't figured out yet what the correlation is.</i></div></td>
+    <td width="173"><img height="121" src="/web/20161225040510im_/http://www.coreyh.org/diablo-2-files/documentation/images/Crude_Heavy_Boots.jpg" width="173"/></td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="normal_data">Normal Item Data</a></h3>
+<p>Normal items have no extra quality data.</p>
+<h3><a name="low_quality">High Quality ("Superior") Item Data</a></h3>
+<p>If the item is one of high quality, it has 3 additional bits.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">3</td>
+    <td><i>unknown. I'm certain the value has something to do with mods
+      on an item's inherent (non-recorded) properties, such as weapon damage,
+      but I haven't figured out yet what the correlation is.</i></td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="magic_data">Magically Enhanced Item Data</a></h3>
+<p><img src="/web/20161225040510im_/http://www.coreyh.org/diablo-2-files/documentation/images/Sturdy_Spiked_Shield_of_Spikes.jpg" align="right"/>
+Magically enhanced items have two 11-bit fields representing the item's prefix
+and suffix. Either one (but not both) may be omitted. The prefix and
+suffix each are used in choosing the <a href="#enhancements">magical
+enhancements</a> for an item (although the enhancements are modifiable), and can
+also increase the minimum level required to use them item and affect the item's
+color.</p><img src="/web/20161225040510im_/http://www.coreyh.org/diablo-2-files/documentation/images/Mesh_Belt_of_the_Mammoth.jpg" align="left"/>
+<br clear="both"/>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>Item prefix (i.e., &quot;Gold&quot; or &quot;Tangerine&quot;). I've started a <a href="Magic_Names.html#prefix">list
+      of prefix identifiers</a>, but it is very sparse at this time. If
+      this field is 0, the item has no prefix.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>Item suffix (i.e., &quot;of Greed&quot; or &quot;of Life&quot;). I've started a <a href="Magic_Names.html#suffix">list
+      of suffix identifiers</a>, but it is very sparse at this time. If
+      this field is 0, the item has no suffix.</td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="set_data">Set Item Data</a></h3>
+<p></p>Set items have a 12-bit field containing the ID of the set.
+<em>(Not the set member, but the whole set.)</em> The set member is
+identified by cross-referencing the <a href="#76">item
+type</a> with the set Id. Also note that set items have <a href="#set_extended_data">an
+extra field</a> following the <a href="#specific">item-specific data</a>.
+<p><!-- @ --></p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th colspan="2">Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">12</td>
+    <td>
+      <div>Set identifier; i.e., all items which are part of the set will have
+      the same value in this field. Since I've only identified a few set
+      items, I'll give their ID's here:</div>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <td align="middle" width="20%">2</td>
+          <td width="60%"><span color="#004000">Cleglaw's Brace</span></td>
+        </tr>
+        <tr>
+          <td align="middle">3</td>
+          <td><span color="#004000">Iratha's Finery</span></td>
+        </tr>
+        <tr>
+          <td align="middle">4</td>
+          <td><span color="#004000">Isenhart's Armory</span></td>
+        </tr>
+        <tr>
+          <td align="middle">6</td>
+          <td><span color="#004000">Milabrega's Regalia</span></td>
+        </tr>
+        <tr>
+          <td align="middle">7</td>
+          <td><span color="#004000">Cathan's Traps</span></td>
+        </tr>
+        <tr>
+          <td align="middle">11</td>
+          <td><span color="#004000">Berserker's Arsenal</span></td>
+        </tr>
+        <tr>
+          <td align="middle">12</td>
+          <td><span color="#004000">Death's Disguise</span></td>
+        </tr>
+        <tr>
+          <td align="middle">13</td>
+          <td><span color="#004000">Angelic Raiment</span></td>
+        </tr>
+      </tbody>
+      </table></td>
+    <td width="245"><img height="250" src="/web/20161225040510im_/http://www.coreyh.org/diablo-2-files/documentation/images/Deaths_Hand_Leather_Gloves.jpg" width="245"/></td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="rare_data">Rare Item Data</a></h3>
+<p><img height="294" src="/web/20161225040510im_/http://www.coreyh.org/diablo-2-files/documentation/images/Loath_Song_Battle_Axe.jpg" width="253" align="right"/> This is by far the worst beast to decode. Rare items have a
+variable number of bits before we get to the item contents, and this number can
+vary anywhere from 55 to 88!</p>
+<p><img height="156" src="/web/20161225040510im_/http://www.coreyh.org/diablo-2-files/documentation/images/Eagle_Mark_Amulet.jpg" width="331" align="left"/> <i>Update 3/14/2002:</i> <strong>EUREKA!!</strong> I've
+finally figured out the variable fields!; See the table below.<br clear="both"/></p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">8</td>
+    <td>This is the Id for the <a href="Magic_Names.html#rare_first_name">first
+      word of the item's name</a> (i.e., &quot;Stone&quot; or &quot;Doom&quot;).</td>
+    </tr>
+  <tr>
+    <td align="middle">8</td>
+    <td>This is the ID for the <a href="Magic_Names.html#rare_second_name">second
+      word of the item's name</a> (i.e., &quot;Finger&quot; or &quot;Shroud&quot;).</td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>First <a href="Magic_Names.html#prefix">magic
+      prefix</a> <i>(optional)</i>. Although this &quot;prefix&quot; isn't actually
+      shown in the item name, it is used in determining the magical properties,
+      required level, coloring, and other attributes of the rare item.</td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>First <a href="Magic_Names.html#suffix">magic
+      suffix</a> <i>(optional)</i>. Although this &quot;suffix&quot; isn't actually
+      shown in the item name, it is used in determining the magical properties,
+      required level, coloring, and other attributes of the rare item.</td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>Second magic prefix <i>(optional)</i></td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>Second magic suffix <i>(optional)</i></td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>Third magic prefix <i>(optional)</i></td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>Third magic suffix <i>(optional)</i></td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="unique_data">Unique Item Data</a></h3>
+<p>Unique items have an additional 12 bit field, which in <em>most</em> cases is
+the unique item ID. The few exceptions are certain quest items (e.g., the
+Horadric Malus).</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th colspan="2">Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">12</td>
+    <td>
+      <div>Item identifier. Since I've only identified a few unique items,
+      I'll give their ID's here:</div>
+      <table cellspacing="0" width="80%" align="center" border="1">
+      <tbody>
+        <tr>
+          <td align="middle" width="20%">13</td>
+          <td width="60%"><span color="#8b6914">Ume's Lament</span> Grim Wand</td>
+        </tr>
+        <tr>
+          <td align="middle">31</td>
+          <td><span color="#8b6914">Hellplague</span> Long Sword</td>
+        </tr>
+        <tr>
+          <td align="middle">75</td>
+          <td><span color="#8b6914">Wormskull</span> Bone Helm</td>
+        </tr>
+        <tr>
+          <td align="middle">77</td>
+          <td><span color="#8b6914">Undead Crown</span> Crown <i>(no, that is not a typo!)</i></td>
+        </tr>
+        <tr>
+          <td align="middle">91</td>
+          <td><span color="#8b6914">Goldskin</span> Full Plate Mail</td>
+        </tr>
+        <tr>
+          <td align="middle">120</td>
+          <td><span color="#8b6914">Nagelring</span> Ring <i>(not a typo either; I checked)</i></td>
+        </tr>
+        <tr>
+          <td align="middle">123</td>
+          <td>Amulet <span color="#8b6914">of the Viper</span></td>
+        </tr>
+        <tr>
+          <td align="middle">125</td>
+          <td><span color="#8b6914">Horadric</span> Staff</td>
+        </tr>
+        <tr>
+          <td align="middle">126</td>
+          <td><span color="#8b6914">Hell Forge</span> Hammer</td>
+        </tr>
+        <tr>
+          <td align="middle">4095<br/>(0xFFF)</td>
+          <td><span color="#8b6914"><i>(other; probably a quest
+          item)</i></span></td>
+        </tr>
+      </tbody>
+      </table>
+    </td>
+    <td width="332"><img height="310" src="/web/20161225040510im_/http://www.coreyh.org/diablo-2-files/documentation/images/Hellplague.jpg" width="332"/></td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="crafted_data">Crafted Item Data</a></h3>
+<p>Crafted items appear to be coded exactly like rare items, having a rare name
+(two parts) and six optional prefixes / suffixes.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">8</td>
+    <td>This is the Id for the <a href="Magic_Names.html#rare_first_name">first
+      word of the item's name</a> (i.e., &quot;Stone&quot; or &quot;Doom&quot;).</td>
+  </tr>
+  <tr>
+    <td align="middle">8</td>
+    <td>This is the Id for the <a href="Magic_Names.html#rare_second_name">second
+      word of the item's name</a> (i.e., &quot;Finger&quot; or &quot;Shroud&quot;).</td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>First <a href="Magic_Names.html#prefix">magic
+      prefix</a> <i>(optional)</i>. Although this &quot;prefix&quot; isn't actually
+      shown in the item name, it is used in determining the magical properties,
+      required level, coloring, and other attributes of the crafted item.</td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>First <a href="Magic_Names.html#suffix">magic
+      suffix</a> <i>(optional)</i>. Although this &quot;suffix&quot; isn't actually
+      shown in the item name, it is used in determining the magical properties,
+      required level, coloring, and other attributes of the crafted item.</td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>Second magic prefix <i>(optional)</i></td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>Second magic suffix <i>(optional)</i></td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>Third magic prefix <i>(optional)</i></td>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td>If this field is 1, the next 11-bit field is present. If 0, the
+      next field is absent.</td>
+  </tr>
+  <tr>
+    <td align="middle">11</td>
+    <td>Third magic suffix <i>(optional)</i></td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="runeword">Rune Word</a></h3>
+<p>If the item has a rune word (indicated by <a href="#42">bit
+42</a> being set), there is an additional field at this point.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">12</td>
+    <td>This <em>appears</em> to be an index to the rune word, although I
+      can't say what the index is based on. The first rune word,
+      &quot;Ancient's Pledge&quot;, has a value of 27. The next rune word, &quot;Black&quot;,
+      has a value of 32. etc.</td>
+  </tr>
+  <tr>
+    <td align="middle">4</td>
+    <td><i>Unknown; the value is 5 on all items I've looked at.</i></td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="personalized">Personalization</a></h3>
+<p>The following segment is present if and only if the item is personalized
+(i.e., <a href="#40">bit
+40</a> is set). Only armor and weapons (except for quest items) can be
+personalized.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">7</td>
+    <td>First character of the owner's name (just plain ASCII!)</td>
+  </tr>
+  <tr>
+    <td align="middle">7</td>
+    <td>Second character of the owner's name</td>
+  </tr>
+  <tr>
+    <td align="middle">7 &#xD7; <i>N</i>-2</td>
+    <td>Repeat until you get the whole name (15 characters maximum)</td>
+  </tr>
+  <tr>
+    <td align="middle">7</td>
+    <td>0&#xA0; (this indicates the end of the name)</td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="unknown_11bit_data"><i>Unknown Field</i></a></h3>
+<p>All items have this field between the personalization (if it exists) and the
+item-specific data:</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">1</td>
+    <td><i>unknown; this usually is 0, but is 1 on a Tome of Identify.
+      (It's still 0 on a Tome of Townportal.)</i></td>
+  </tr>
+</tbody>
+</table>
+<h2><a name="specific">Item Structure part 3: Item-Specific Data</a></h2>
+<p>The presence of the following fields depends on the item type. Fields
+which are present will be stored in the order shown. Unfortunately there
+is no means of telling which fields are present from the item data itself; you
+need to look up the <a href="#76">item
+type</a> in a table to figure out whether it is a weapon, armor, or stack, and
+read the fields accordingly.</p>
+<h3>Armor: Defense Rating</h3>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">10</td>
+    <td>Defense value +10. i.e., a defense rating of 23 would be
+      stored in this field as 33; thus the maximum defense value you can store
+      is 1013 (although I haven't tried it). Note that this is the base
+      defense rating, before applying any magical enhancements (i.e., the number
+      shown in white).</td>
+  </tr>
+</tbody>
+</table>
+<h3>Armor and Weapons: Durability</h3>
+<p>Even though stacked weapons don't show any durability rating in the game,
+they still have two 8-bit fields in the same spot. This includes bombs
+(exploding and gas potions). The values in such cases are very small, so
+I'm not sure what they mean.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">8</td>
+    <td>Maximum Durability. Note that this is the base durability,
+      before applying any magical enhancements (i.e., the number shown in
+      white).<br/><i>Note: </i>I've found an indestructable item, and it appears
+      that in such a case the maximum durability field is zero!</td>
+  </tr>
+  <tr>
+    <td align="middle">8</td>
+    <td>Current Durability. This may be greater than the maximum
+      durability if the item is magically enhanced.<br/><i>Note: </i>I've found
+      an indestructable item, and it appears that in such a case the current
+      durability field is missing!</td>
+  </tr>
+</tbody>
+</table>
+<h3><a name="sockets">Armor and (non-stacked) Weapons: Sockets</a></h3>
+<p>The following field is present if and only if the item is socketed (i.e., <a href="#27">bit
+27</a> is set).</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th colspan="2">Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">4</td>
+    <td>Number of sockets<br/><i>Note that even though this field is 4 bits
+      wide, each item type has a built-in upper limit to the total number of
+      sockets. This limit is built into the game. The most I've ever
+      seen is 6 for, e.g., a gothic axe.</i></td>
+    <td width="179"><img height="137" src="/web/20161225040510im_/http://www.coreyh.org/diablo-2-files/documentation/images/Socketed_Mask.jpg" width="179"/></td>
+  </tr>
+</tbody>
+</table>
+<h3>Tomes:</h3>
+<p>Tomes have an extra 5 bits inserted at this point. I have no idea what
+purpose they serve. It looks like the value is 0 on all of my tomes.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">5</td>
+    <td><i>unknown</i></td>
+  </tr>
+</tbody>
+</table>
+<h3>Stacked Weapons, Quivers, Keys, and Tomes: Quantity</h3>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">9</td>
+    <td>Quantity</td>
+  </tr>
+</tbody>
+</table>
+<h2><a name="enhancements">Item Structure part 3: Magical Enhancements</a></h2>
+<h3>Item Structure part 2<sup>bis</sup>: <a name="set_extended_data">Set Item Data
+Revisited</a></h3>
+<p>Items which are part of a set have an additional 5 bits following the
+item-specific data.</p>
+<table width="100%" border="1">
+<tbody>
+  <tr>
+    <th width="20%">Size</th>
+    <th>Contents</th>
+  </tr>
+  <tr>
+    <td align="middle">5</td>
+    <td>This appears to be an indicator of how many lists of magic properties
+      follows. The first list are the properties the item has if you do
+      not have any other members of the set. Following lists are applied
+      once you equip other items in the set. The value is 1 if there are
+      two (total) property lists, or 3 if there are three property lists.</td>
+  </tr>
+</tbody>
+</table>
+<p>Following the item-specific data are a variable number of variable length bit
+fields describing any magical enhancements placed on the item. Each
+property begins with a 9-bit identifier. An identifier of <tt>0x1FF</tt>
+(all 1's) indicates the end of the property list ... except in the event the
+item belongs to a set, in which case there will be another one or two groups of
+magical properties following, depending on whether the set item data (above) is
+1 or 3, respectively. Also, if an item has been given a <a href="#42">Rune
+Word</a>, it appears that the Rune Word's properties begin with a <tt>0x1FF</tt>
+identifier (presumably to set them apart from the item's normal properties...
+but I need to examine more items to be certain.)</p>
+<p>Because the number of bits (and fields) after the 9-bit identifier varies, I
+do not give a field width here. Instead, check my <a href="Magic_Properties.html">table
+of magic properties</a> for field sizes. I'm sure it's not complete, but
+it does have most of the common properties.</p>
+<p>Following the last 9-bit value of 0x1FF, the rest of the final byte will be
+padded with 0's if necessary, and the item structure ends there. For
+example, if the item had 341 bits of data, the last (43<sup>rd</sup>) byte will
+be 0x1F. If the item had 248 bits of data, the last (31<sup>st</sup>) byte
+will be 0xFF.</p>
+</body>
+</html>