Difference between revisions of "GetCurrentGameTime - Utility"
Jump to navigation
Jump to search
imported>Rasikko (→Notes: Shortened and simplified my note about the fast travel bug.) |
imported>Rasikko m (→Notes: Use the global variable for faster processing.) |
||
| Line 24: | Line 24: | ||
== Notes == | == Notes == | ||
* A bug occurs anytime you fast travel 4 hours or less before midnight and the distance is long enough that it takes over a day to get there. This results in the day of the week falling out of sync and the date being skipped(23 loredas becomes, 25 sundas instead of 24 sundas). In calendar terms, you're basically using a whole new calendar for the year, every time this bug occurs. | * A bug occurs anytime you fast travel 4 hours or less before midnight and the distance is long enough that it takes over a day to get there. This results in the day of the week falling out of sync and the date being skipped(23 loredas becomes, 25 sundas instead of 24 sundas). In calendar terms, you're basically using a whole new calendar for the year, every time this bug occurs. | ||
*It is much faster to use the GlobalVariable "GameDaysPassed" instead. | |||
== See Also == | == See Also == | ||
Latest revision as of 05:47, 7 March 2021
Member of: Utility Script
Obtains the current game time in terms of game days passed (same as the global variable)
Syntax[edit | edit source]
float Function GetCurrentGameTime() nativeParameters[edit | edit source]
None.
Return Value[edit | edit source]
The current game time in terms of "game days passed".
Examples[edit | edit source]
; What is the current in-game time?
Debug.Trace("The current time is: " + Utility.GetCurrentGameTime() + " in game days passed")Notes[edit | edit source]
- A bug occurs anytime you fast travel 4 hours or less before midnight and the distance is long enough that it takes over a day to get there. This results in the day of the week falling out of sync and the date being skipped(23 loredas becomes, 25 sundas instead of 24 sundas). In calendar terms, you're basically using a whole new calendar for the year, every time this bug occurs.
- It is much faster to use the GlobalVariable "GameDaysPassed" instead.