Kicked and connection failed, no warning

[Tripi]

Time to finish that SA now and load up the barracks queue.

[ZADSRAVEN]

YIPPEE!!!
New patch/update/etc etc. New lvls, new quests, new adventures..
And still I can't use it live.
...yay....
Thanks team, another stunning update, true to form as expected

[Psychokilla]

for how long lol

[ZADSRAVEN]

...were they waiting for my patience to finally break before they restarted? Typical that I post a bit of sarcasm, then all starts up again..

[kismajom]

Aha working again ) yipiiiiiiiiii

[Xibor]

Sandycove came back up approx. 30 minutes ago.

[Xibor]

or you can keep going and get no where.............................

That of course can be true as well

[Nogbad2]

Err, the same update was inflicted on the French servers last week, and none of this happened.
Besides which, they've had ample time to absorb a lot of the issues with this update but have ignored the feedback on test server and most of us can no longer test it there anyway as the Halloween event killed our accounts.

Update, the version we have here is not the same as the one inflicted on French servers last week.
BB currently have 3 different rollouts on the go, no wonder it's a mess.
Of course lucky germans have had theirs delayed for "database maintenance", code for "they wouldn't be expected to put up with this"

[Bunnios]

Dear BB,

Please kindly let me know when performing any action does *not* result in a spinning hourglass for several minutes (or, in fact, indefinitely, as I am experiencing now).

Thanks.

[Xibor]

Dear BB,

Please kindly let me know when performing any action does *not* result in a spinning hourglass for several minutes (or, in fact, indefinitely, as I am experiencing now).

Thanks.

That comes and goes for me, normally (fortunately) it isn't that often. It's the worse when the wife and I are on the same adventure - something seems confused by the orders to the generals (troop counts) especially. It acts to me like my computer is waiting on some kind acknowledgement and doesn't get it. I normally just cancel the window and do the action again and that often solves it - for that instance. It's just as likely to do it again it seems.