Official Raid Times changed??

[Fred]

According to the pinned post raid times are 20:00-22:00 Local Server Time. On US-C 4122 it is 8:46 Local Server Time and the raid window has already closed. Is this a bug, or a change for Memorial Day weekend?


Official Server Raid Times
I've seen a little confusion about this right now, so until we get it more prominently displayed in game I'm just putting this information up everywhere players are looking.


The standard settings on Official servers are as follows:

Weekend PvP Raid Times are...

Saturday & Sunday 20.00 - 22.00 Local Server Time

For reference, Official Server Regions and Time Zones:

EU-C:
UTC+2
EU-W:
UTC+1
US-W:
UTC-7
US-C:
UTC-6
US-E:
UTC-4
CN:
UTC+8
AU:
UTC+10
BR:
UTC-3
JP:
UTC-9

[Handbanana]

Your time is off. If its -6 on that server that means whatever clock you are looking at is off by an hour.

[Fred]

Originally posted by Handbanana:

Your time is off. If its -6 on that server that means whatever clock you are looking at is off by an hour.

Except raiding started on time at 8:00 Central and then ended at 8:41.

[Handbanana]

Except when you posted this it wasn't even 8:00 yet. If you go off UTC-6 it is currently 20:26. So what you are saying is the raid ended 14 minutes before it was even supposed to start.

Sounds like the server time was configured wrong and maybe someone updated it or they accidentally launched raid timer early. I remember something like that happening once in early access.

[PhoenixFyre]

US-West raid time should have started 14 minutes ago and has not yet started. :(

[Dribs]

I absolutely love this because that means that for the first time in prob 2 years playing this game I have more tham 30 minutes of raid hours I can enjoy.

Please Stunlock, keep the raid hours as they are now!!!! Pretty please with sugar on top.

[Fred]

I guess the main confusion on our US-C server is that the first week raid times were 20:00-22:00 UTC-6, the second week the raid times were 20:00-22:00 CST (UTC-5), and this week the raid times were 20:00-20:41 CST (UTC-5), then it stopped for 19 minutes and resumed 20:00-22:00 UTC-6.

The US-C designation is a bit of a misnomer since UTC-6 is Mountain Time and not Central Time.

[Sythalin]

Originally posted by Vandykeg:

The US-C designation is a bit of a misnomer since UTC-6 is Mountain Time and not Central Time.

I think your understanding of UTC is the misnomer. Mountain Time by default (aka Standard Time aka CST) is UTC-7, where as Central Time is UTC-6.

It's the antiquated "Daylight Savings Time" that throws people off where everything adjusts by -1 (MT: UTC-6 and CT: UTC-5, respectfully). There's a reason why the majority countries don't use this stupid system, and I wish the stubborn handful that do would get over themselves and join the rest of the world. Same for the metric system, but I digress....

My assumption is that when the config is set to a specific UTC, it doesn't take into account this fact so when it compares the "local time" (currently -5 for CDT) to the server's hard config for -6 CST, it's not exactly sure which time it should be using so it just randomly chooses one of them each time it reboots.

[Fred]

Originally posted by Sythalin:

Originally posted by Vandykeg:

The US-C designation is a bit of a misnomer since UTC-6 is Mountain Time and not Central Time.

I think your understanding of UTC is the misnomer. Mountain Time by default (aka Standard Time aka CST) is UTC-7, where as Central Time is UTC-6.

It's the antiquated "Daylight Savings Time" that throws people off where everything adjusts by -1 (MT: UTC-6 and CT: UTC-5, respectfully). There's a reason why the majority countries don't use this stupid system, and I wish the stubborn handful that do would get over themselves and join the rest of the world. Same for the metric system, but I digress....

My assumption is that when the config is set to a specific UTC, it doesn't take into account this fact so when it compares the "local time" (currently -5 for CDT) to the server's hard config for -6 CST, it's not exactly sure which time it should be using so it just randomly chooses one of them each time it reboots.

Let's try to use a less condescending tone when replying. Notice I used the term Central Time instead of CST or CDT to avoid semantics. My statement is still valid since the server is US-C, which should reflect local time and take CST/CDT into account.

Also... Only countries that use SI vs. Metric have landed a man on the moon, but I digress...

[Sythalin]

Originally posted by Vandykeg:

Originally posted by Sythalin:

I think your understanding of UTC is the misnomer. Mountain Time by default (aka Standard Time aka CST) is UTC-7, where as Central Time is UTC-6.

It's the antiquated "Daylight Savings Time" that throws people off where everything adjusts by -1 (MT: UTC-6 and CT: UTC-5, respectfully). There's a reason why the majority countries don't use this stupid system, and I wish the stubborn handful that do would get over themselves and join the rest of the world. Same for the metric system, but I digress....

My assumption is that when the config is set to a specific UTC, it doesn't take into account this fact so when it compares the "local time" (currently -5 for CDT) to the server's hard config for -6 CST, it's not exactly sure which time it should be using so it just randomly chooses one of them each time it reboots.

Let's try to use a less condescending tone when replying. Notice I used the term Central Time instead of CST or CDT to avoid semantics. My statement is still valid since the server is US-C, which should reflect local time and take CST/CDT into account.

Also... Only countries that use SI vs. Metric have landed a man on the moon, but I digress...

Let's agree on this - I'll be "less condescending" when you remember what you wrote accurately:

Originally posted by Vandykeg:

times were 20:00-22:00 CST (UTC-5), and this week the raid times were 20:00-20:41 CST (UTC-5)

You literally said CST was UTC-5. TWICE

As for the landing on the moon comment, not sure what that has to do with the discussion but if it gave you a proud "'MURICA!!!" moment then go for it. Just keep in mind another fun fact: the US space program standardized metric a while ago, so keep e-thumping that chest kiddo.

[SKAPP]

Raid times are bugged because of daylight savings, wait for a hotfix, this was announced on the v rising discord.

[Fred]

Originally posted by Sythalin:

Originally posted by Vandykeg:

As for the landing on the moon comment, not sure what that has to do with the discussion but if it gave you a proud "'MURICA!!!" moment then go for it. Just keep in mind another fun fact: the US space program standardized metric a while ago, so keep e-thumping that chest kiddo.

"Kiddo" is the go-to when trying to dismiss someone based on perceived age. You definitely aren't old enough to be my father.

SI vs. Metric is for those who don't or can't use both interchangeably. In my line of work, I use metric when speaking with my LA/EMEA counterparts, SI when speaking with my US counterparts, and either SI or Metric based on MIL-STD when dealing with any military contracts.

By all means though, continue on with your semantics and self-righteousness.

[Handbanana]

Originally posted by SKAPPELTON:

Raid times are bugged because of daylight savings, wait for a hotfix, this was announced on the v rising discord.

That doesn't even make sense. Daylight savings was months ago. I remember this happening in the past as well. I forget what caused it but it was something they screwed up with the patching process after an update.

[SKAPP]

Originally posted by Handbanana:

That doesn't even make sense. Daylight savings was months ago. I remember this happening in the past as well. I forget what caused it but it was something they screwed up with the patching process after an update.

To everyone else except for this fellow here. It was announced yesterday on the official v rising discord by the community manager stating that it's a daylight savings issue.

[Handbanana]

Originally posted by SKAPPELTON:

Originally posted by Handbanana:

That doesn't even make sense. Daylight savings was months ago. I remember this happening in the past as well. I forget what caused it but it was something they screwed up with the patching process after an update.

To everyone else except for this fellow here. It was announced yesterday on the official v rising discord by the community manager stating that it's a daylight savings issue.

So do you like being dishonest or do you just not know how to read?

:ALERT: Official Server Raid Times 5/26 - 5/27 :ALERT:
Please be aware that the displayed SERVER TIME may be incorrect! We are going work to adjust this display bug as soon as we can, but the change may not go through before the weekend is over, so for that reason please be aware that your displayed server time might be offset in accordance with daylight savings time.

For instance, the server time for EU-C servers is being displayed as CET(UTC+1) when they should be displaying as CEST(UTC+2) due to daylight savings time. For this reason raid times could potentially be 1 hour later than you might be expecting.

They attempt to blame the timer on daylight saving times but as I mentioned that was months ago and it doesn't make any sense. It also would not account for the fact that raids were randomly ending before the timer was up. Daylight savings literally happened before 1.0 even came out. UTC also accounts for daylight savings so if the server was set it would automatically be adjusted for.

Also this issue did not exist before this weekend so as I said before THEY DID SOMETHING and broke the timers. I remember in gloomroot there was an entire weekend where nobody raided because they did something similar and broke raid timers. Instead of admitting they broke it they try to throw out this lame excuse which may be partly true but its not the root cause of the issue.

[NoxJS]

I'm in UTC+2 and raid time here were 20-22 since last weekend.
This weekend they were 21-23