Post: #1

Hi, just wanted to ask:

Were there any changes to serv.time regarding the max value? In our current (pretty old) version of .56b the maximum value of serv.time is the max value of a 32bit integer (2.147.483.647) which causes the server to totally fuck up after some years.

We're close to the maximum again, but we're also planning on upgrading our sphere so I'd like to know if I still have to worry about the serv.time problem (which causes our timers and all our scripts that use serv.time to malfunction).

Thanks for reading!

Post: #2

On our server we had to restart times about 3 years ago. I think today is still so.

Post: #3

Thanks for your reply -.-