Cantr II Discussion Forum

Doug R. wrote:Tick timings appear to be approximately 20 seconds fast.

I have to resist the urge to say "Aww, muffin".

Doesn't joo's site have a ±5 minutes disclaimer

20 seconds are with in the +- 5 minute disclaimer, which is dependant on script running time. Each server script need between 15 seconds and 5 minutes (worst case) to complete, and when "your" tick appears within that timeframe is impossible to say.

Doug R. wrote:Tick timings appear to be approximately 20 seconds fast.

I'm quite relieved to hear that they're so accurate. If you noticed that they're consistently 20 seconds "fast," though, then they could be adjusted.

Ah. I never saw the disclaimer, I just downloaded the software from his link. Nevermind then.

Starvation is off by...3 hours slow. They just happened at 6:30, and it's now 7:4 so that's 10 cantr mins = 50 real mins + 2:10 on the tick timer = 3 hours off.

You saw someone starving to death at 6:30?

3056-6.30: You see xxx die.
This body seems to be at most half a year old. The body shows clear signs of starvation.

I knew it was slow when I first installed it, but I wasn't sure how slow.

Right. I had that down as 7:30 for some reason.

(Fixed)

After the reboot today They are delayed 11 (Cantr-)minutes.

Sailing: x.18
Land travel: x.23
Projects: x.29-30

These are confirmed so far.

Eating is at 5:34.

Hmm... alright, that seems vaguely consistent. Adjusted.

It seems my host is 503ing at the moment, though. If you're desperate you can also access the local copy hosted on my machine at http://joseph.uk.to/CantrTicks/,

The timings seem to be way off again for some reason (perhaps due to the timeouts?)

Travel happens at :23, which is about 50 mins from now, but the timer says 1:45.

Yeah, the Cantr midnight offset had changed since I last checked it, probably due to the downtime. That should be corrected now.

One of these days I'll write a script that adjusts that automatically at regular invervals (or I could have the front-end do that with each page request, but that could lead to the Cantr frontpage being flooded with requests... and I'd have to work out the cross-domain permissions somehow).

It would be better with a non-public API for those kind of things.

EchoMan wrote:It would be better with a non-public API for those kind of things.

That would be wonderful, if someone would implement it on the server-side. Do you want to?