Posting here because I do need a solution.
I got a racing type game that needs to run off milliseconds.
Floating point stuff is giving me a headache (0.1 = 0.099etc).
Can't use the, every x seconds because every 0.01 seconds doesn't play nice.
[quote:4brktgh9]Time leaderboards present scores in hours / minutes / seconds / hundredths of a second format. You must submit scores as milliseconds, so 66032 would be interpreted as 1:06.03.
Quote from Google Play Games Services for Publishing Android Games.
If anyone has any experience with c2 to google play, handling hundredths of seconds, I'd love to hear about it.
Also working on another game where I want to accumulate revenue over time regardless of whether or not the app is running.
Correct me if I'm wrong but Construct 2 doesn't have native support for 'system time' ?
I was just going to search for a unix time addon but got cold feet wondering if it would work on the million different types of android phone. I want to be able to work with hundredths of seconds and days all in the same equation. Elapsed time.
e.g. this thingo will give revenue 3 times per second, and this thingo will give revenue about once every 3 hours and if the app is closed, it will check on startup, using last stored times, how much has been earned since last revenue gained and calculate/display the progress towards next revenue for each thingo.