of     1   

neverhammer
#104671550Monday, July 08, 2013 11:29 PM GMT

os.clock pretty much means operating system clock. Currently we are not able to use os.clock in a script. Benefits/Things we can create with os.clock: -Seasonal places that switch as time passes -Functioning calendars showing the m/d/y -Accurate clocks! -real time day/night cycles (if it's dark out where you are, its dark in game) -In-game weather (snowing in winter, raining in spring, etc.) Cons/Downsides to os.clock - Please unlock os.clock for all us robloxians to use in a script! Thanks for reading
mikeyman10ash
#104671850Monday, July 08, 2013 11:31 PM GMT

Timezones When the sun is rising in EST(around 7 or 8 AM currently, IIRC), it would be 4 or 5 AM in the Pacific Time Zone, meaning the sun SHOULD still be down there but in game it would be in the sky "Fell deeds awake! Now for wrath! Now for ruin! AND A RED DAWN!"
neverhammer
#104672141Monday, July 08, 2013 11:34 PM GMT

I'm pretty sure there's a way to account for time zones and such.
mikeyman10ash
#104672383Monday, July 08, 2013 11:36 PM GMT

No, the problem is. ROBLOX clocks are in pacific time zone(I think.) People using the clock from their OS will be using the clock in THEIR time zone. So in game in a separate time zone, say EST, a script written for Pacific Time would be 3 hours behind the EST OS clock "Fell deeds awake! Now for wrath! Now for ruin! AND A RED DAWN!"
neverhammer
#104672757Monday, July 08, 2013 11:39 PM GMT

Ahhh yes I see what your saying... could you somehow make the script local and run it through the player's os clock?
Lukekneenew
#104674766Monday, July 08, 2013 11:55 PM GMT

They already have this. Put a local script in a place where you can get the local player. (Backpack or Character, etc.) Then, use the tick() function to get the number of seconds in UNIX time. :D
Vrathis
#104674974Monday, July 08, 2013 11:57 PM GMT

Support. This was already suggested in a different manner.

    of     1