Arch Linux User Repository

The link to holocure-bin-0.4.1662745659.zip appears to be dead (at least in its current form)

If you've played on holocure on a different wine prefix before, you can migrate your save with a few steps.

First, start holocure and let it generate a new save file. It should be located at $HOME/.local/share/holocure/wine/drive_c/users/$USER/AppData/Local/HoloCure/save.dat.

The first 80 bytes of this file is a unique identifier generated by collecting system data and is compared at launch. You'll get an error message "Data structure with index does not exist." if this identifier isn't correct or if your save data is corrupt. Otherwise, these 80 bytes do not do anything else.

The remaining data is base64-encoded JSON. This is your save data.

This means if you only replace the newly generated save data with your old save data but retain the newly generated identifier, you can effectively transfer your data (and perhaps "mangle" it to your benefit in the process):

# In $HOME/.local/share/holocure/wine/drive_c/users/$USER/AppData/Local/HoloCure/
truncate save.dat -s 80
tail <OLD_SAVE_FILE_LOCATION> -c+81 >> save.dat

This file is probably generated by GameMaker: Studio's ds_map_secure_save function. If a Wine update causes the identifier string to mismatch, you'll likely need to just migrate your save.

Aside: That function name is an ludicrous misnomer as save migration is supposedly one of the things it should be "secure" against.