Fixed Wait Command Behaving Strangely

[Jarylan]

Hello, standard apology if this was already reported, saw no similar thread, etc.

For reasons unknown, lately the wait command has been acting weird. As an example, when attempting to wait 12 hours, the command will instead somehow force the current time to 12:00, without altering the date. This happens with other times as well, 1 hour setting to 1:00.

The error does not happen /every/ time, but it is fairly pervasive. Sometimes the command will work correctly for a bit before going back to setting the time rather than waiting.

If on the Cheat/Debug menu, advancing time there always works as it should.

Game version is 0.9.138-BACKER-ANDROID#6328

Save file is enclosed.

 

[Jacques00]

Sorry, I can't seem to replicate this issue. I've tried looking through the code and can't find where it would break how it advances time as both the cheat and the regular resting functions all use the same base function to process time--though the time cheat does do calculations prior to advancing that time, depending on which option you select, they both still use the same function.

Are you sure you're not misinterpreting the time readout? The clock is actually in 24-hour notation (00:00 - 23:00), so that may cause confusion if you are not already aware of that. On the developer side, there is an option to convert the clock to 12-hour format (AM/PM), but it isn't set for release quite yet since we'll need to go in and translate a lot of the in-game time mentions to match that format for it to be useful.

Aside from that though, setting the actual hours and minutes isn't something the Rest function does. However, looking at it again, I think I see where there might be a potential problem. I'll make some minor edits and hopefully that will fix it for the next release.

 

[Jarylan]

Honestly, I haven't been able to replicate lately either.

It's quite possible I wasn't reading the time right on the 24 hour clock, but I could swear the day wasn't changing.

Since it's not replicable, I will take a mea culpa, and say I must have been reading the clock wrong.

Terribly sorry for the trouble.

 

[Jacques00]

No worries. If it indeed happened, it might have had something to do with clashing variables since I did notice the use of some local variables that had the same spelling as the more global variables, so I'm chalking it up to that. So like I mentioned previously, hopefully the edits I made for the next release will future-proof that from happening again.