[TERA PC & Console] En Masse is closing, but TERA lives on! We will continue to support TERA PC (NA) and TERA Console until service is transferred. Stay tuned for more information.
[TERA Console] The Grotto of Lost Souls update (v85) is now live! Read the patch notes here: https://bit.ly/TERACon_v85
[TERA PC] The 64-bit update (v97) is now live. Check out all the changes delivered on August 11 here: https://bit.ly/tera64_patchnotes
[TERA PC & CONSOLE] Summerfest Part 2: The Beach Bash is on from August 11 until September 1! Participate in event activities to earn tokens redeemable for costumes, consumables, mounts, and more! Details: https://bit.ly/tera_sf20
Comments
The product team is still looking into why some things are not resetting as usual. It's something Bluehole will have to advise us on because it appears to be a server-side issue introduced with the latest update. Hopefully we have an answer soon.
Ping 700+
I'm getting confirmation on this (and an updated chart of the times, if I can), but it looks like the daily times have unexpectedly changed for VG resets.
> Montblanck wrote: »
>
> FYI - the Vanguards daily (which should have resetted around 4 hours ago) have not reset as well.
>
>
>
>
> I'm getting confirmation on this (and an updated chart of the times, if I can), but it looks like the daily times have unexpectedly changed for VG resets.
Thank you for keeping everyone posted, dear. I figure the reset times with the update simply weren't switched to NA time zones. Wish the tech support team all the best for speedy resolutions.
Sounds like a fun time bug. Isn't Korean Standard Time = UTC + 0900? or put another way, KST - 0900 = UTC?
Wasn't the Civil Unrest issues at the start a time bug?
Yeah, Korean time is UTC+9, but the other thing is that they don't have Daylight Savings. But yeah, it does seem to somehow all tie back to time zones in the end. For some reason they must have changed the way something was aligned for whatever reason and neglected to mention it. (And yeah, Civil Unrest was also related to time, but unlike this one it wasn't merely offset, but plain didn't work.)
I mean, in the grand scheme of all the issues, it's probably not the brightest-burning fire right now, but still -- a fascinating study on the perils of delivering software for various markets (and why *all* servers and all time settings should always be in UTC).