Talk:LlGetTime

The last edit lost the point that llGetTime returns results more precise than whole seconds, such as results that differ by more than zero yet less than one. -- Ppaatt Lynagh 13:26, 24 October 2007 (PDT)

svc-3293

is there any special reason we're keeping a reference to this jira (which was marked expected behavior)?
-- Void ^{(talk|contribs)} 03:50, 17 October 2011 (PDT)

Template:Issues/SVC-3293 just needed updating so that it would only show in the All Issues section. The reason for keeping dead bugs listed in the documentation is so that anyone who knew about the bug can find out from the documentation the status of the bug. -- Strife ^{(talk|contribs)} 11:47, 17 October 2011 (PDT)

P.S. We should also prune them periodically but only as needed.

that makes sense, and now I know what to change to keep it in the deep notes, thanks =)
-- Void ^{(talk|contribs)} 22:11, 19 October 2011 (PDT)

It isn't advertised but there is a field that can force it to show in Caveats or for it to not show in Caveats. Everything always shows up in Deep Notes. -- Strife ^{(talk|contribs)} 20:40, 21 October 2011 (PDT)

Conflict in descriptions

The page for llGetRegionTimeDilation says "affects llGetTime & llGetAndResetTime". However, the pages for llGetTime & llGetAndResetTime say that "script time [as returned by these two functions] is unaffected by time dilation. Unless I misunderstand something, these two statements conflict. Len Lectar 19:17, 14 November 2012 (PST)

Honestly don't know why why it says that... one of them is wrong, someone can feel free to test which by comparing to a time/date function under heavy lag and report back.
-- Void ^{(talk|contribs)} 16:40, 10 May 2019 (PDT)

Accuracy loss

"at Best" implies that it can be worse. Suggest wording change to "x/y Sec under z days" with no qualifiers. Don't have time for an edit war over minutiae
-- Void ^{(talk|contribs)} 16:40, 10 May 2019 (PDT)