**KNOWN AW ISSUE**
Please be aware, there is a known issue with Saga badging when observing the AW map.
The team have found the source of the issue and will be updating with our next build.
We apologize for the inconvenience.
Options

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

World EaterWorld Eater Posts: 3,640 ★★★★★
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

  • Options
    PantherusNZPantherusNZ Posts: 1,813 ★★★★
    Yeah i've seen the same thing several times, just ignore it now
  • Options
    BringPopcornBringPopcorn Posts: 3,632 ★★★★★
    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?
  • Options
    DukenpukeDukenpuke Posts: 658 ★★★
    Just google "Epoch time."
  • Options
    SkyLord7000SkyLord7000 Posts: 3,999 ★★★★★
    It’s the start date for most internal computer clocks
  • Options
    MikeHancho31MikeHancho31 Posts: 247 ★★★

    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
  • Options
    yeah he time travelled
  • Options
    World EaterWorld Eater Posts: 3,640 ★★★★★
    Maybe this can be fixed in the next update


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


  • Options
    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
  • Options
    Adri5846Adri5846 Posts: 48
    Was Kang in your alli? Lol
  • Options
    World EaterWorld Eater Posts: 3,640 ★★★★★
    Time keeps on slippin’…….


  • Options
    CrcrcrcCrcrcrc Posts: 7,942 ★★★★★
    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.
  • Options
    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).
  • Options
    (Title correction).
    Just noticed you said 57 years in this Title.
    Actually that # in game message calculates (correctly) to 53+ years, not 57, lol.
  • Options
    World EaterWorld Eater Posts: 3,640 ★★★★★

    (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



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




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


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


This discussion has been closed.