Read/write code for timers doesn't match #621

Closed
opened 2025-02-17 14:02:56 +00:00 by CelticMinstrel · 2 comments
CelticMinstrel commented 2025-02-17 14:02:56 +00:00 (Migrated from github.com)

On write it outputs 3 numbers but on read it expects 4 numbers.

On write it outputs 3 numbers but on read it expects 4 numbers.
NQNStudios commented 2025-02-17 15:08:33 +00:00 (Migrated from github.com)

It seems like this would either cause data loss or a crash. Have you seen the bug manifest? Should it be a priority?

It seems like this would either cause data loss or a crash. Have you seen the bug manifest? Should it be a priority?
CelticMinstrel commented 2025-02-17 15:26:12 +00:00 (Migrated from github.com)

I noticed it while reviewing #346, which has a fix for it that can't be cherry-picked due to my tag-file rework. I haven't seen it manifest in actual practice.

It makes sense to prioritize it, since it would indeed lead to timers being lost or corrupted when loading a saved game.

I noticed it while reviewing #346, which has a fix for it that can't be cherry-picked due to my tag-file rework. I haven't seen it manifest in actual practice. It makes sense to prioritize it, since it would indeed lead to timers being lost or corrupted when loading a saved game.
Sign in to join this conversation.
No description provided.