That one wouldn't work either, the message it gives me is:
We should see if it's problem with the site or a xenforo issueThat one wouldn't work either, the message it gives me is:
>Please enter a number that is no more than 4294967295.
It's a UNIX timestamp, like the thing used for sharty filenames that starts with 17 and then a bunch of numbersThat one wouldn't work either, the message it gives me is:
>Please enter a number that is no more than 4294967295.
Apparently that's the highest possible 32-bit integer.
what if they come back when they're 104Make any future permaban 88 years.
I feel like they'd have learned their lesson by then.what if they come back when they're 104
what if... what if they dont....I feel like they'd have learned their lesson by then.
Ban 'em another 88 years idkwhat if... what if they dont....
what if they drink from the fountain of youthBan 'em another 88 years idk
its probably 2 billion seconds or somethingIt gave me a huge error number that wasn't a date, I'm not sure how I'd be able to calculate it into a date so I'm not sure what the maximum limit is on years.
just make it like 40 years. Not like this site will last that long.It gave me a huge error number that wasn't a date, I'm not sure how I'd be able to calculate it into a date so I'm not sure what the maximum limit is on years.
Make it 5 years if that's the casejust make it like 40 years. Not like this site will last that long.
>we should measure time in seconds since uhhh 1970 or something... yeah that sounds goodIt's a UNIX timestamp, like the thing used for sharty filenames that starts with 17 and then a bunch of numbers
Apparently it tops out at 2106 (number being seconds since Jan 1 1970 iirc)
View attachment 54098
>starts with 17It's a UNIX timestamp, like the thing used for sharty filenames that starts with 17 and then a bunch of numbers
Apparently it tops out at 2106 (number being seconds since Jan 1 1970 iirc)
View attachment 54098
thats the easiest way to explain it>starts with 17
nusoycacas...