Alliance member left ……. 57 years ago!?? Strange in game message.

World EaterWorld Eater Member Posts: 3,756 ★★★★★
edited March 26 in General Discussion
Obviously not a big issue but it’s def been good for a few laughs.

I thought it was a one time thing but it’s happened a few times this month






Post edited by Kabam Jax on

Comments

  • PantherusNZPantherusNZ Member Posts: 2,199 ★★★★★
    Yeah i've seen the same thing several times, just ignore it now
  • BringPopcornBringPopcorn Member Posts: 5,211 ★★★★★
    Dukenpuke said:

    January 1, 1970 should be a very familiar date to anyone that has done any kind of database development.

    Isn't that the date that was turning Iphones into bricks?
  • DukenpukeDukenpuke Member Posts: 658 ★★★
    Just google "Epoch time."
  • SkyLord7000SkyLord7000 Member Posts: 4,000 ★★★★★
    It’s the start date for most internal computer clocks
  • MikeHancho31MikeHancho31 Member Posts: 247 ★★★
    World Eater said:

    PantherusNZ said:

    Yeah i've seen the same thing several times, just ignore it now

    How can I ignore that my alliance mates have learned to time travel!?

    Glad I’m not the only one seeing this.

    Side note: it looks like the date it brings me back to is December 31st, 1969.
    Nice
  • AdarshClashesAdarshClashes Member Posts: 43 ★
    yeah he time travelled
  • World EaterWorld Eater Member Posts: 3,756 ★★★★★
    Maybe this can be fixed in the next update


  • RiderofHellRiderofHell Member Posts: 4,659 ★★★★★
    Who let the tardis in. 🤣
  • World EaterWorld Eater Member Posts: 3,756 ★★★★★
    edited November 2023
    New month , still happening. Members left my alliance 19,675 days ago. Def dates back to Jan 1 , 1970


  • SummonerNRSummonerNR Member, Guardian Posts: 12,817 Guardian
    So the code for that line above of “Members Left Alliance” is displaying the difference between 2 variables in code.
    One being the current time (OK, easy enough).

    Other being a variable in code that is supposed to indicate when Alliance Member(s) have left.
    But that variable looks like it is never being set to anything at the time members leave. Leaving it as the default of “0”.
    So when it calculates the difference, it comes out to people having left 1/1/1970 (or 12/31/1969, probably depending on timezones and how you see your current time).

    As that is a “beginning of time” point for some types of software “Time” variables.
    Aka, TIME = 0
  • Adri5846Adri5846 Member Posts: 86 ★
    Was Kang in your alli? Lol
  • World EaterWorld Eater Member Posts: 3,756 ★★★★★
    Time keeps on slippin’…….


  • CrcrcrcCrcrcrc Member Posts: 7,964 ★★★★★
    Finally figured this out, it’s the programming Unix time standard, which is basically just a timestamp system that started January 1st, 1970, that helps keep timers in computer programs on track by having a baseline. Looks like the system just uses the entire counter as a placeholder for the member left counter.
  • SummonerNRSummonerNR Member, Guardian Posts: 12,817 Guardian
    Crcrcrc said:

    Finally figured this out, it’s the programming Unix time standard, which is basically just a timestamp system that started January 1st, 1970, that helps keep timers in computer programs on track by having a baseline. Looks like the system just uses the entire counter as a placeholder for the member left counter.

    Oh, so it's Unix time variable that uses 1/1/1970 ? Nice.

    Knew that some system or language used that as a starting date, see a few replies up above, wasn’t sure which might have used 1970 or 1980, or earlier (as below).

    Knew it wasn’t quite as recent of a starting point as C++ time variable (which isn’t that something like 1901 ??, without getting into how that system had originally miscalculated one of the Leap Year days, so there's some “quirk” to that one).

    So yes, the more days go on here, that # will be ever increasing, since “current” date keeps growing, but “zero” date is fixed at (well, ZERO).
  • SummonerNRSummonerNR Member, Guardian Posts: 12,817 Guardian
    (Title correction).
    Just noticed you said 57 years in this Title.
    Actually that # in game message calculates (correctly) to 53+ years, not 57, lol.
  • World EaterWorld Eater Member Posts: 3,756 ★★★★★
    SummonerNR said:

    (Title correction).
    Just noticed you said 57 years in this Title.
    Actually that # in game message calculates (correctly) to 53+ years, not 57, lol.

    Forgive my miscalculation.

    This message continues to appear



  • World EaterWorld Eater Member Posts: 3,756 ★★★★★
    edited February 13
    Still happening 5 months later …. My alliance mates are time travelers




  • Sundance_2099Sundance_2099 Member Posts: 3,429 ★★★★★
    Time? Don't talk to me about time! We don't have the time!
    ....
    What was I saying?
  • World EaterWorld Eater Member Posts: 3,756 ★★★★★


    Maybe it will be fixed in the next update ;) but I’m not counting on it
  • World EaterWorld Eater Member Posts: 3,756 ★★★★★
    Time keeps on slippin ….


This discussion has been closed.