Play Free War Battle Games Online, Multiplayer Games, Strategy Games, Top MMORPG

immortalisllc · **Joined:** Tue Nov 29, 2011 10:22 pm **Posts:** 68

What is up with the clocks on this server?

I told Seth about it and he said the IT people said we were basically imagining things.

It happened again yesterday and this time I was chatting with other NA people who saw it to.

It just happened again to everyone in chat and there are players in several places in the United States, Hawaii, Israel, Aussie, Europe, and one in Canada so it's not a local issue or a client issue. Tick jumped 3 1/2 mins.

Time to trade in the crappy Tandy server.

ARF · **Posted:** Thu May 03, 2012 2:10 pm

This has pretty much always been a problem on BD. The clock is almost always faulty on every server.

However the ticks are usually consistent. So they should happen at the same time every hour.

saibaba60 · **Joined:** Fri Jul 31, 2009 11:36 am **Posts:** 393

The faulty time could be anywhere from 10 secs-2.5 minutes(usually 10-50 secs). Any EOT attacks you want to make, it's best to do so 5 mins on the clock. My alliance has also had problems with this :/
You just gotta play around it

Elric · **Posted:** Thu May 03, 2012 3:01 pm

immortalisllc wrote:

What is up with the clocks on this server?

I told Seth about it and he said the IT people said we were basically imagining things.

It happened again yesterday and this time I was chatting with other NA people who saw it to.

It just happened again to everyone in chat and there are players in several places in the United States, Hawaii, Israel, Aussie, Europe, and one in Canada so it's not a local issue or a client issue. Tick jumped 3 1/2 mins.

Time to trade in the crappy Tandy server.

It has to do with the strength of the server all together. Battle dawn has a runtime check that occurs at the end of each tick, and its universal for all worlds. Think of it like a massive equation that the game has to go through inorder to update everyone movements, resources, scores, etc.

While ideally it would be great if each world had its own process for this, the current set up is probably cost effective.

I'm sure as Battledawn continues to expand, and develop - this will eventually improve.

henry700 · **Posted:** Thu May 03, 2012 3:33 pm

Indeed. i noticed that since the first time i played. for that to happen too early i think the battledawn server has a sort of preview programming to start making the equations a bit before so the ticks do not get late, or it is too busy receiving/sending to clients and is not updating the timer it sends to the client propperly, if they are two separate variables that is.

I don't have clue on how the BD devs programmed the server, but this is a problem that can be easily circunvented, and i wouldn't call the BD servers "junk" for that. they can handle over like 500 people logged on at a time with minor lag. if that is junk i don't know what good means anymore.

ARF · **Posted:** Thu May 03, 2012 3:38 pm

saibaba60 wrote:

The faulty time could be anywhere from 10 secs-2.5 minutes(usually 10-50 secs). Any EOT attacks you want to make, it's best to do so 5 mins on the clock. My alliance has also had problems with this :/
You just gotta play around it

forget the clock. The server seems to tick at the same time regardless of what the clock says, so once you figure out the time, it shouldnt matter.

krazedkid101 · **Posted:** Thu May 03, 2012 11:44 pm

He mad xD

Elric · **Posted:** Fri May 04, 2012 12:10 am

It is clearly the traffic on the servers as Kongregate servers, il server, de server, es server, and galaxy, never gave me these problems

henry700 · **Posted:** Fri May 04, 2012 12:15 pm

And remembering well it rarely happened last round for me, as i had those who launches and refreshes faster battles with Sun Devil and i launched my squads around 5 secs left and the timer never missed.

sabnc · **Posted:** Fri May 04, 2012 3:07 pm

Strange for me the ticks usually go behind the countdown timer.

Junk Battledawn Servers