Jump to content

GameDaysPassed Precision bug past 64 days


Recommended Posts

Posted

Hello!

 

I have looked into this, and it appears that both GetCurrentGameTime() in Papyrus and the GameDaysPassed global variable in F4 have a bug. After 64 in-game days, in theory, their evolution slows down, and they are only updated on save/load/rest/travel. 


Is there any known fix for this? I would love a GameDays Passed feature that is accurate beyond the 64-day mark.

 

Is the only way to create my own global equivalent and update it via perpetual papyrus script with a looped gametime timer in a script?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...