BUG: HS3 native Backup Restore = Scripts fail to run when HS3 install path changed

[Ltek]

I installed HS3 in a different path on the rebuilt Windows OS - then I restored the HS3 native backup.

Bugs:


1. HS3 is not changing the Script path in Events to match the new HS3 path. (see screenshot)

2. HS3 is not logging errors on initial HS3 loading or when the events executes. Thus, there is no way to know this is a problem until something simply doesnt happen when you expect it to.


rjh -- another HS3 restore bug that causes pain and manual rework. Come on dude, make restore work properly

[stefxx]

I always wondered why script locations are being stored as absolute paths and not as relative paths. That would solve this issue as well.

[zwolfpack]

I noted the same issue recently while evaluating feasibility of migrating Windows to Linux. All script paths have to be repaired. I used the built-in Backup/Restore functionality.