0.10.0
Files
| Name | Size | OS | SHA-256 |
|---|---|---|---|
| savetailor_0.10.0_amd64.deb | 10.42 MB | linux | ad16d3dfdd73dca11abcf2827fd1de7c14ef13eda8040612bb1c4d675c29cadd |
| savetailor-0.10.0-linux-x86_64.tar.xz | 9.18 MB | linux | df60ef3525f2f3f056d00f2e1f900639bf50c1b9a445316183181972bf926631 |
| savetailor-0.10.0-windows-amd64.zip | 9.72 MB | windows | 81a6d2f8d5bbee74d335f21f32616ee4cd5e43c48b98fcfde1920e086ce6b9b0 |
Release Notes
Common for all components is compatibility with older Linux distributions such as Debian 10 and Ubuntu 18.04.
App - 0.9.0
Fixed
- An error observed on Windows 10 Enterprise LTSC 2021 with non-English system language/locale (Korean) without the "Unicode UTF-8" (beta) feature enabled.
Plugin: Dying Light 2 Save Editor - 0.10.0
Changed
- Avoids the error "Attempting to get pointer by zero ID".
Regarding Error "Attempting to get pointer by zero ID"
This was a data integrity check added in version 0.8.0 of the standalone Dying Light 2 Save Editor released on August 11, 2025, accompanied by a fix for a data corruption bug causing some unknown campaign state to be lost.
Maybe the data was important, or maybe it wasn't. In any case, the game loaded these saves without complaints, so the problem went unnoticed for some time.
Since then, the editor would reject affected saves, and would instead show an error message to highlight the problem: Attempting to get pointer by zero ID
By popular request from affected users, the editor will now attempt to ignore that the problem exists so that these problematic saves can continue to be edited, hopefully without any further complications.
If possible and convenient, please consider restoring a backed up save.