Knowing which games use Easy Save 3 helps you recognize when an ES3 save editor is useful. Popular examples include:
If you ever see a save file ending in .es3 or a folder named EasySave3, you know exactly what tool to reach for.
As Unity evolves, so does Easy Save. Version 3.5+ introduced more efficient binary serialization and improved encryption defaults. This means future games will be harder to edit with basic ES3 save editors. However, the modding community always adapts.
We are already seeing ES3 save editors with built-in JSON export/import, allowing users to edit in friendly tools like VSCode before re-importing. Others are adding diff viewers to compare save files before and after in-game actions—making it easier to reverse-engineer variable names.
Not all editors are created equal. When looking for or using an ES3 Save Editor, ensure it offers the following features:
Look for tags that make sense. Common tags include:
The tree structure will often mirror the game’s code objects. For example, a PlayerStats tag might contain strength, agility, and intellect as child nodes.
Developing an ES3 editor requires parsing the specific binary structure of the Morrowind save file.
Easy Save 3 uses tags to identify different pieces of data. For instance, a file might contain tags like @playerLevel, @inventory, and @worldSeed. A dedicated editor will parse these tags into an expandable tree view.
A save editor designed for ES3 files bridges the gap between the binary code and the player. Its primary functions usually include:
