Jump to content
Sign in to follow this  
You need to play a total of 5 battles to post in this section.
Finnkax

WG - clanbattle problems

10 comments in this topic

Recommended Posts

204
[PIZZA]
Members
1,034 posts
11,701 battles

I and some other persons are from different timezone so we cannot participate in clan battles. 31 mins or similar left. Or is it NA side which make different timezone? 

  • Cool 1

Share this post


Link to post
Share on other sites
65
[PLPT]
Members
214 posts
9,961 battles

If you're trying to play in the EU time zone, you're not alone. We cannot launch, several other clans reporting the same problem.

  • Cool 1

Share this post


Link to post
Share on other sites
2
[DEV_X]
Members
20 posts
13,259 battles

Cant Que in? we rdy up hit battle and it unready us! were on NA trying EU server time

Edited by Get_of_Fenris

Share this post


Link to post
Share on other sites
65
[PLPT]
Members
214 posts
9,961 battles
1 minute ago, Get_of_Fenris said:

Cant Que in? we rdy up hit battle and it unready us! were on NA trying EU server time

I think everyone is having that same issue

  • Cool 1

Share this post


Link to post
Share on other sites
1,156
[N-W-T]
Members
1,923 posts
7,591 battles

WG has posted this pic of the coder they brought in for this project, as proof they are hard at work on a fix. 

Spoiler

gettyimages-712-37-640x640.jpg.04df0a35719aed0ec26277ded0c3ff30.jpg

 

  • Cool 1

Share this post


Link to post
Share on other sites
512
[90TH]
Members
1,107 posts
10,013 battles

FFS NA should just boycott any cross-server CB.  WG has failed us what, 4 or 5 times in a row now?

Share this post


Link to post
Share on other sites
512
[90TH]
Members
1,107 posts
10,013 battles
24 minutes ago, bgog97522 said:

It's working now, although it started an hour late which makes me think it's a daylight savings issue.

It’s clear they have cheap junior developers who used time offsets (UTC-8) instead of proper time zones from the Olson time zone database (America/Los_Angeles)

Classic junior programmer mistake.  Hamsters at the wheel here.

But what’s worse, they haven’t been able to fix it even though it’s been a repeated problem for at least the last three sessions...

DONT MAKE US TEST SOMETHING THAT HAS BUGS WE REPORTED LITERALLY A YEAR AGO

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×