Under the hood, Resurrected still uses the .d2s format, albeit with extensions for the shared stash (now stored in SharedStashSoftCoreV2.d2i ). The original binary layout remains untouched for character data. Blizzard wisely knew that touching the save format would break a generation of mods, editors, and speedrunning tools. A Diablo II: Lord of Destruction character save file is a digital palimpsest. It holds the story of every Mephisto run, every accidental death to a Lightning Enchanted beetle, every Ral-Tir-Tal-Sol inserted into a breast plate. It is a format born from constraints—small memory footprints, slow hard drives, and dial-up Battle.net—yet it achieved a level of transparency and hackability that modern game save files (often encrypted, cloud-locked, or obfuscated) have abandoned.
Next comes the attributes block . This section stores the raw numeric statistics: strength, dexterity, vitality, energy. But it goes deeper. It also tracks life (current vs. base), mana , stamina , and gold (both on-hand and in the stash). Notably, Diablo II stores experience as a massive 32-bit integer, which is why reaching level 99 requires a masochistic grind of billions of experience points. One of the most elegant features of the .d2s format is how it handles quest progression. There is no verbose list; instead, the game uses a bitmask system . For each act, a 16-bit or 32-bit integer represents which quests have been triggered, completed, or failed. For example, setting a specific bit might give you the quest reward for the Den of Evil without actually killing Corpsefire. Waypoints are similarly compressed: a simple array of bytes, where each bit toggles a specific waypoint’s active status. diablo 2 lod character save files
This checksum is not encryption—it is integrity. It prevents simple byte-swapping hacks. However, because the algorithm was reverse-engineered long ago (a standard CRC-32 with a known polynomial), it only stops accidental corruption, not determined modding. The original Diablo II: LoD .d2s format was so robust that when Diablo II: Resurrected launched in 2021, one of its most celebrated features was backward compatibility . You could copy your 20-year-old save file from a dusty USB drive, paste it into the new Saved Games folder, and launch the game. The remastered graphics engine would render that same level 87 Sorceress, still wearing the same imperfect Shako, with the same half-finished Hell quest log. Under the hood, Resurrected still uses the
The corpse block is perhaps the most anxiety-inducing data in the file. When a hardcore character dies, the corpse block is ignored. But for softcore, the game maintains a pointer to your body on the ground. If you die multiple times, the save file holds a chain of corpses. Corruption often occurs here: if the game writes a new corpse before fully clearing the old one, the file can become desynchronized, leading to the dreaded "failed to join game" error. With the introduction of Lord of Destruction came the PlugY mod and later the official Resurrected shared stash, but the original .d2s file only controls the personal stash . This is a simple, linear chunk of data: 100 slots (for the original 6x8 grid), each slot defined by a 4-byte item code, followed by a variable-length item attribute list. A Diablo II: Lord of Destruction character save
The community’s response was ritualistic: backup your Save folder every hour. Tools like ATMA (the seminal muling program) gained popularity not just for transferring items, but for their ability to repair corrupted headers and recalculate checksums. The most sophisticated part of the .d2s format is the checksum . At a specific offset (usually near the end of the header), the game writes a 32-bit CRC (Cyclic Redundancy Check) of the rest of the file’s critical data. If you open a save in Hero Editor and change your gold from 10,000 to 1,000,000, the editor automatically recalculates this checksum. If you try to manually hex-edit without updating it, the game will reject the file with the infamous "Bad inventory data" error.