[EFFx]

Discovered it while making a VIP Expire system privately. Searched the date on the google and found this information: https://en.wikipedia.org/wiki/Year_2038_problem

Well... interesting

[Bugsy]

Yeah, known issue, by then hopefully everything will be running on 64 bits.

[EFFx]

I've never heard of this issue before, I knew that there's a max number supported but not a date. Discovered it by accident, marks the game's last date.

[Bugsy]

You'd probably only be aware if you've worked with and understand how Unix timestamps work. Basically once we reach the largest value in seconds that can be stored in a 32-bit signed integer, you are at a dead-end from a timestamp/time tracking perspective. It's 'easy' to overcome the issue, but requires work nonetheless. Either use an unsigned 32-bit integer or ideally a 64 bit integer: signed or unsigned doesn't matter as the world will probably end before we reach the boundary/cap of a 64 bit signed integer.

https://ximalas.info/2015/03/10/when..._t-really-end/

When we gather all the bits and pieces, the end date might be December 4th, 292,277,026,596 AD, at 20:10:55 UTC. Or maybe it’s December the 3rd, or the 5th.

[EFFx]

Interesting thing to acknowledge.

[TheDS1337]

Originally Posted by Bugsy Yeah, known issue, by then hopefully everything will be running on 64 bits.

Well, if we don't get the mess of a world war 3, that should be more than enough )

[kww]

It was very interesting for me to discover this, too
I learned this from a random 4-5 years ago video .