I am getting a lot of errors contacting codename games. I play on steam.(it is OK) I rebooted the computer. Cleared the DNS cache. Cleared the flash cache. Ran cCleaner.


AND it still has contact errors on your end

I'm playing on mobile (Android) and haven't been able to connect for a number of hours. My internet connection is solid and the game is fully updated, and I can't think of anything else that might be wrong on my end. I got a late start on this event, too, so I'm really missing a lot of potential progress.

I just lost a buttload of rubies because the server didn't respond when I tried to complete a mission. No more "Ready" message, no additional rubies in inventory, no still-continuing mission, nothing. Poof, gone. Can only guess what else I've lost.

Same here!

It's happened to me several hours before and now several hours after, but never during, the whole dumb bee thing.

I suspect the massive amount of reprogramming they had to do to introduce their bugs spanned every part of their code.

I've had these issues across KongregateChrome/Windows10, Steam/Windows10, and Android5.X

In addition, I haven't seen a word from any Dev all weekend. When instituting such a major programming change for the B thing, not a smart management decision to leave both the ships helm (server/programing monitoring and bug fixing) and com systems (Forums/Facebook/ingame messages ) unmanned.

All these Kind of management decisions are starting to make me wonder if all my investment choices in this game through Kongregate Kreds are worthwhile.

With all the time I haven't been able to spend on the game, I've started looking for other games to fill my CotLI time.

this issue has nothing to do with the MINOR programming needed to change some text across multiple characters.
it has everything to do with server issues, and these Devs rent space on Amazon servers so there's nothing that they actually can do, and mostly they do not work weekends anyway. and i bet their own internal diagnostics see nothing wrng whatsoever.

if not their servers it is everyone's computers. I think Microsoft came out with a dns change or tcp/ip stack change and that is affecting a lot of people.

i have had luck with doing a ipconfig/flushdns and
ipconfig/release and
ipconfig/renew, along with
netsh winsock reset catalog and
netsh int ipv4 reset reset.log and
netsh int ipv6 reset reset.log

all this from a command prompt with admin privileges, then a reboot on the computer not just restart, and a reboot of my wifi router not simply turning off and on but going to in my case 10.0.0.1 and performing some advanced things...
did this friday and have not had a single retrying request, or request failed... error at all. will cross my fingers and report if there are any of those errors again but so far 40+ hours without any.