Thanks heaps, 6502!

There is no one "wrong" value. The defect is not in the particular value stored in this file, but rather in how U7.EXE would interpret the values.

These files store three 16-bit numbers:
- second (1/25 of a minute, 1/1500 of an hour, 1/36000 of a day) within the day
- day (starting from 0 as the first day of a playthrough, i believe)
- time rate (generally 1, but does not seem to be used at all with these timers)

Day values equal to any multiple of 7 are at the start of an in-game week, so setting the day to 0 (or to 7, or 14, for that matter) would give the highest probability of Jaana being able to heal again.

The original, Jaana-no-heal, contents posted above by 6502 show a day value of 0x000D, or 13, which is the last day of an in-game week, which makes perfect sense given what i have explained above.

ed: And, to be clear: the contents of this particular file, GAMETIMK.DAT, represent the last time Jaana used her healing as a party member.

Thanks for your elaboration John, very insightful and enlightning as usual :-D

So basically, if you'd automatically copy a GAMEINTK file consisting of 00 00 00 00 01 00 with each start of the game this bug will never occur. Alternativly, you could probably make it read-only...

Might be nice for people not using your hacks (although it's beyond me why one shouldn't)

: )

no, "with each start of the game" would not suffice. each time Jaana used her healing during a play session - particularly if toward the end of an in-game week - the problem would crop up again. and, i don't know of any way to see the day-of-week in-game, so it's not something that the player could work around through gameplay.

I think I get it. So the automatic copying approach would be more like a workaround, right?

In a sense of: If Jaana stops being able to heal, save you game, restart (copy is done) and Journey onward