Remove in-game time

[thesourceofsadness]

Fair point. Why is there a particular reason everything can't just change over to ingame time for consistency of conversion?

Well, as I said above, some things are actually specified in terms of real time, so it seems to make sense to present them that way. I guess you could argue for forgoing that just for the sake of consistency, and that's not necessarily a bad point. I guess my main problem with it is that, since the real-to-ingame time factor isn't exactly 3, but 3.29, those times would be just... ugly. For instance, realm challenges take two real-time hours, which would then be presented as 6:34:48, a completely unacceptably un-numerological value.

I'unno. Probably the fix that would make the most sense would indeed be to discard the hypothetical scenario above, remove in-game time and just present everything as real time. Arguably, my main problem with doing so isn't even discarding the hypothetical expedition scenario, but just that I like, and am quite attached to,the idea that the in-game day/night-cycle is specified in terms of 24 in-game hours. If you just give me a few months, I might be able to cry myself out of the illusion that I can have nice things. ;_;

Why don't you make every timer in in-game time and adjust numbers to look pretty? Like 6:34:48 to 6:00 or 6:30. If someone will cry that it's not comfortable - c'mon, game immersion is more valuable and rare thing these days. We really need in-game day to be 24 hours, not some ugly ammount of real-life hours.

[Aceb]

Or simply to make things funnier - apart from having both times different font, just put the in-game time as "in nights" like "this construction can be built after 3 nights passes" or "this should be ready soon" etc. etc., having only real-time hours accurate. I hope You can get the idea.

[Granger]

Aceb has reasonable idea, I think. Custom clients would still show exact time wherever they would be able to do that.

But honestly, in case you want consitency have all times internal as ingame time (so you don't do the mars lander thing where they faceplated it by doing the math in feet and the code in meters - or the other way around, forgot, it's just confusing) and one (!) function to format time for output.
And a toggle in the client options, so the user can decide if he want's to live on realtime or the ingame one.

[noindyfikator]

I'd agree with you, but the problem is that all durations are set in ingame time terms. That would require a pretty significant rewrite of things.

If all durations are set in ingame time why do you display them randomly as in-game hours or real-life hours? I think you are wrong my friend

[SnuggleSnail]

I'd agree with you, but the problem is that all durations are set in ingame time terms. That would require a pretty significant rewrite of things.

I feel like this sentiment can only come from you guys misunderstanding what people want. We don't care if in-game time moves at x3.29 real time. Totally fine. Everybody's down.

Literally all anybody wants is for the tooltips/inspect information to be accurate real time. It would not be a major rewrite. It would be {time} >> {time/3.29}.

Also bump

[SavageFox]

sure there is something you can do in the way of programming to convert that calculation to display real time sometimes things have to be ugly to get the job done

[Luno]

For me the problem is not that ingame time exists, but that some things are ingame time and some are real time, and the game never tells you which is which.
Battering rams, localized resources etc are all real time iirc, but stuff like curios in study report and star gazing are iirc ingame time.
please just pick one and use it for all cases.

[Delamore]

Keep your time however you want internally, just always present it to the player as real time.
The fact that the multiplier is 3.29 rather than a round number is even more reason to present it to the player as real time.