123123

[M3D1CN1]

Hi again so in my next bit of useless information how about this
at the end of this year the date will be wait for it

12.31.23

now we do need a a gift stone to mark this day

[GreenBar]

now we do need a a gift stone to mark this day

Perhaps a stone like the t-shirt one where it marks the time created; A bonus for those that can create there's at 12:31:23

[Alibaster]

now we do need a a gift stone to mark this day

Perhaps a stone like the t-shirt one where it marks the time created; A bonus for those that can create there's at 12:31:23

However, 12/31/23 is the way we display it in the US. Doesn't Europe do 31/12/23?

[Silent]

However, 12/31/23 is the way we display it in the US. Doesn't Europe do 31/12/23?

yes we do, but a free ugly and itchy Christmas sweater is a free ugly and itchy Christmas sweater!

[GreenBar]

Doesn't Europe do 31/12/23?

Dates in UO, such as the [time command, event dated items, etc, are displayed as month, day, year. Assume this is because Richard Garriott, while born in England, was raised in Texas and at the time of developing UO worked for EA, a US company.

[arrow]

That grandfather clock that C+ made out of 4 pieces was a fantastic creation - Would love to see a repeat of that!

[Durocius]

That grandfather clock that C+ made out of 4 pieces was a fantastic creation - Would love to see a repeat of that!

I agree. It’s a prized item in my castle.

[+Colibri]

The gift is ready, and the giftstone will become available just a few minutes before Sunday midnight.

The gift also displays the time of when it was created... so, some of you might want to aim at it having a time 00:00:00 or 12:31:23 or 12:34:56 or whatever. So I have made an area with a bunch of practice giftstones, so that you can figure out how to time the doubleclicking of the giftstone. These practice items look like clock parts, the actual gift will be different.

The actual giftstone will be in the same area. ... but there will be just 1 giftstone at the end of the hallway and you will only have one chance

Btw you can right-click the gift and select "Options" and then set what timeformat should be displayed. So even if you don't get a perfect time, you can still have it display either just the date, or the date and hour, or date and hour:minute, or if you get it perfectly then you'll probably want to go for date hour:minute:second

[MagicUser]

No millisecond option? I can track to ~116 ms accuracy.

[+Colibri]

Oh right, i added the Millisecond precision to the Enum, but didn't code it elsewhere. I'll add that (i'll be back in a few hours, but you should still have a few hours to try it out... i'll make new test giftstones).

[+Colibri]

Ok the clocks can now display sub-second precision (tenths or hundredths of a second, or milliseconds). The practice giftstones were refreshed so you can now try calibrating your scripts again. The practice stones will be removed today at 23:30 shard time.

Btw, on sunday the probably most desired exact time will be at 12:31:23. If you manage to get the gift at exactly that time, the clock will display "Obtained on 12/31/23 at exactly 12:31:23". If you're off by just a few seconds, it will still display "Obtained on 12/31/23 at about 12:31:23"

[MagicUser]

Love that you're having so much fun with this.

Ok the clocks can now display sub-second precision (tenths or hundredths of a second, or milliseconds). The practice giftstones were refreshed so you can now try calibrating your scripts again. The practice stones will be removed today at 23:30 shard time.

Btw, on sunday the probably most desired exact time will be at 12:31:23. If you manage to get the gift at exactly that time, the clock will display "Obtained on 12/31/23 at exactly 12:31:23". If you're off by just a few seconds, it will still display "Obtained on 12/31/23 at about 12:31:23"

[+Colibri]

Yeah it's fun
Ok for those who want to really get into it... There was some lag many years ago and as I was figuring it out, I made this logging of how much the server time drifts from the NTP server... it logs every 10 minutes.

It looks like every day around 5am, the Windows Time service synchronizes the server time with a NTP server.

File:

timedrift.zip

(4.27 KiB) Downloaded 75 times

Description of the columns in the file
Time: The server time that the reading was taken
Offset: the difference between server time and NTP time server. Offset = NTPserverTime - CurrentServerTime
Delay: latency how long it took for the request to go to the NTP server and back.

Code: Select all

ServerTime,Offset,Delay
2023-12-29T05:00:07:477Z,1.4968002,0.0435289
2023-12-29T05:10:03:350Z,1.5071196,0.0587057
2023-12-29T05:20:02:994Z,1.5179781,0.0386928
2023-12-29T05:30:00:117Z,-0.0287399,0.0475262
2023-12-29T05:40:03:060Z,-0.0087983,0.0570498
2023-12-29T05:50:00:923Z,0.0013923,0.0450141
2023-12-29T06:00:07:930Z,0.0114911,0.0604984
2023-12-29T06:10:00:799Z,0.0221071,0.0396091

So it looks like that the server's clock is slow. By about 1.5 seconds in 24 hours. I don't know why it drifts so quickly though, a casio wristwatch keeps better time.

[Wil]

So it looks like that the server's clock is slow. By about 1.5 seconds in 24 hours.

Yeah, Windows timekeeping is crap. Ntp in Linux actually adjusts the local PC clock's tick rate to closely align with NTP time. When running properly, it never steps the clock again after the initial step at boot. The PC's clock crystal is somewhat inconsistent, so NTP does tend to minutely speed up or slow down the clock at each check, but outside of a major fault, the drift is measured in single-digit milliseconds.

[Johnny Warren]

Hey +c is it possible to make this clock rotatable with the interior decorator? The other timestamped clock can be rotated. Hard to display them together without this.

Also, very cool item design mate. I couldn't be around for the sequential times so I grabbed it at 04:20