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

Ilona · **Posted:** Mon Jun 20, 2011 10:08 am

I know that all of the BD staff team are doing their best, but it gets to a point now where BD is really unplayable.
The ticks were frozen all weekend and now the ticks are laggy again.

We had an attack last ticks with 150 squads incoming, we decide to defend and ioned in the last 5 minutes 13 times.
100 squads turned at 1 minute, 50 kept on flying .... then the ticks freezed again at 0:00 and he had 6 (!!!) minutes more time to log in and returned those 50.

Now, we can't even load BD (error 503) correctly or just get this :

we have about 30 incomings which we wanted to defend this tick....

oh, last tick now i guess.

Serious, let the ticks freeze, do an anouncment when it will be fixed finally and work on it.
There is no sense in playing like this.

mfreak · **Posted:** Mon Jun 20, 2011 10:11 am

I posted this in another thread, but since this is new lemme repeat:

I am really not sure if this is being addressed at the core. Ticks are getting frozen literally every day. Not only that, the battledawn website itself goes down.

On top of that there are multiple inconsistencies with the tick engine - sometimes ticks ending too early, sometimes ticks getting stuck. Today, we defended an attack and ioned 15 times, and found that at 00:00 one of the attackers - about 50 squads, didn't turn on time. But ticks got frozen, so he could turn his squads completely, and escape. This shouldn't be the case. We wasted so much of resources to do those 15 ions and in the end we didn't have anything to show for it, simply because ticks saved him.

Seth · **Posted:** Mon Jun 20, 2011 11:18 am

Ticks were not frozen all weekend. They were frozen for the better part of 6 hours on Sunday morning. This was an issue with the tick engine getting hung up and was really a simply problem to solve once I rolled out of bed and noticed it. Funny thing was that I went to bed no more than an hour before the ticks stopped. Poor luck really.

As for the downtime, we outsource our server hosting to another company that handles everything for us. This company had some problems last week with their network hardware, but has since addressed the issue. We had no control over that downtime and it was not caused by our systems. At this time, there were actually about 8 thousand websites that experienced downtime at the same time as they used the same provider we did. Our provider has an excellent track record and we trust they are taking measures to prevent any more downtime.

This morning we had around 15 minutes of downtime while we did a preventative reboot to keep the system from having any more issues this week.

Sorry for any inconvenience this may have caused you.

Before this week, we went almost 2 years without any substantial downtime. One would think that a little more leniency from you folks would be in order.

trevor1601 · **Joined:** Tue Dec 22, 2009 1:45 pm **Posts:** 939

this happened on E2 like 3 weeks ago. where 60 or so squads got an extra 20 minutes to return because of ticks freezing. we could have killed them they hadn't returned when we refreshed once ticks froze but then into the freeze they turn and save their squads. very frustrating indeed.

Maybe in the future they can post in advance when there is going to be downtime to re-boot the system.(15-30 minutes would be plenty of time) so that alliances don't have to waste energy in ioning like you guys did. im sure someone logging in would have seen a news feed that said servers down for re-booting!

we didnt complain when the 60 or so squads got a 2nd lease on life. but then again we didnt have to ion 13 times wasting energy.

so i think a solution to this would have been to post a news feed regarding the downtime.

just throwing my 2 cents out there. it does seem like last 2-3 weeks has been bad for the servers i play hopefully things get better and not worse. as E2 is also in war right now. giving other alliances 2nd lives sucks

Seth · **Posted:** Mon Jun 20, 2011 2:23 pm

The problem with that is that we are not psychic. We cant always anticipate when hardware is going to cause problems. These are issues we all deal with at the same time.

If we had known that there was going to be downtime, we would have posted it.

aviturg · **Posted:** Mon Jun 20, 2011 2:28 pm

SETH

you are wrong my friend. the ticks were frozen for 6 hours straight, but we are facing "server busy" that goes for 10-15 minutes like every 2-3 ticks, we face frozen ticks for few minutes every 2-3 ticks, we face early ticks, we face late ticks. this is annoying and it goes on for the last 2 weeks or so. it just got worse to the point where it is almost unbearable.

i myself lost 110 tanks because i couldnt login for like half an hour, getting "server busy", and that was after the 6 hours freeze.

so come on BD guys, you dont see anyone here asking for compensation or anything else but you taking care of this. we dont (Want to be allies? Sometimes I like to pretend I am a princess riding a pony..) for nothing, this has become really bad.

trevor1601 · **Joined:** Tue Dec 22, 2009 1:45 pm **Posts:** 939

Quote:

This morning we had around 15 minutes of downtime while we did a preventative reboot to keep the system from having any more issues this week.

My post was regarding this one. not the 6 hour downtime where obviously it was un-expected downtime. but im guessing if you intentually rebooted the system causing 15 minutes of downtime giving at least a 30 minute warning to everyone via news-feed that these issues of wasting units and energy ioning could have been avoided.

Seth · **Posted:** Mon Jun 20, 2011 3:01 pm

I found out about the reboot after it happened. I just woke up and had not had time to even get my bearings yet. The backend developers were working on this morning's issues and it was a crack decision on their part to do it. I dont think it was even anticipated to do it, and I may have over simplified what may have been going on, because to be hones, I dont know what he was doing at the time or why he did the reboot. The dude knows what he is doing though, and Im sure he had his reasons.

I think you are all missing your own point by now. If your complaint is that we are not addressing the issues, look around. We are. If your complaint is that it was horrible timing at a time when it just so happened all of us were doing something for fathers day and were not in a position to do anything about it as fast as you would have liked, Sorry. Not much we can do about it except address it as soon as we can which, again if you look around, we have done / are doing.

As for the server busy notes, there is a sticky on this board telling you why it most commonly happens, and in as many cases as I have seen and helped or attempted help with, those reasons were 9 times out of 10 at the root.

As for the tick stoppage, there was a hardware issue which will be addressed as soon as we can take everything offline and address it. If you will take note of the news on the server select screen, you will see a good clear warning mentioning the time window of that very issue.

Again, we do our best to let you know when we are going to be having issues regarding hardware. Sometimes we dont know that a stick of RAM is going to fail on Father's Day when no one is around to notice quickly let alone fix it. We are humans, not bots, and these things can happen. All we can do is do our best to address it as soon as it is feasible to have the team together to fix things.

I dont know what else to tell you exept that we apologize for any problems. The recent issues with stability are not any more fun for us then they are for you.

Anarchist69x · **Joined:** Thu Jan 20, 2011 8:30 pm **Posts:** 371

Seth wrote:

Before this week, we went almost 2 years without any substantial downtime. One would think that a little more leniency from you folks would be in order.

Wish it were true but it's unfortunately not.

mfreak · **Posted:** Mon Jun 20, 2011 3:36 pm

I understand the difficulties about anticipating and fixing server crashes or hardware failures. But my whole point is that when you do fix the problem, it will help if these problems are investigated and addressed at the root. If the same kind of issue has been happening for over 3 weeks, I think its high time those issues - whether hardware related, or server service provider related or software related be looked into and fixed for good. I do understand that server downtimes are natural occurrences that happen all the time, be it even Google and other big organizations, but since this issue has been persistent for quite sometime, instead of just reacting to an issue, it will be much more help if the root cause is fixed, whatever that is.

Forum rules

BD is almost unplayable