Hello,

For about the past 3 weeks I occasionally have my play in Idle Battle stopped and I get a DC displayed. What does DC stand for and why does this happen?

Appreciate your help.

DC means DisConnected, and it happened because either the connection to the WZ servers was interrupted, or you got such a large lag spike, that one of the two sides automatically disconnected.

Edited 10/23/2022 13:21:17

DC stands for disconnect. Sometimes the computer/Warzone lags out and WZ servers think your computer is not responding and you get disconnected as a result.

Beat me to it

Thanks for your help.

What are some of the root causes for lag out?

I want to fix the issue if I can determine the root cause.

What are some of the root causes for lag out?

Playing Idle.

What can I do to reduce lag out?

I have an 11 1/2 year old Apple iMac computer. Could that be part of the problem?

My computer is wifi connected.

137 - 210 Mbps download 15 -20 Mbps upload

Is this okay?

I was getting disconnected more often when I was playing two idle maps at the same time. It's better now that I'm only playing one Idle map. Does that mean it's my computer or internet speed or both?

Edited 11/9/2022 19:37:45

To reduce lag the first thing you can (and probably should) do is turn of all animations and balloons.

Are you using the standalone client (https://www.warzone.com/wiki/Standalone_Client) or your browser?

If you're using the standalone, try increasing the FPS to 120, that should in theory increase performance.
If you're using your browser, switch to the standalone.

I was getting disconnected more often when I was playing two idle maps at the same time. It's better now that I'm only playing one Idle map. Does that mean it's my computer or internet speed or both?

Wdym by playing 2 maps at once? Using multi level? Or using idle in multiple browser/app windows? Cause using idle in multiple windows is definitely a source for problems.

Edited 11/9/2022 19:40:41

I use Chrome as my browser. This problem began about 3 months ago. I realize I'm playing larger Idle maps now. Not sure if that has anything to do with it. Not sure how to turn off animations and balloons but I will research that and see if I can do that.

I will try the stand alone client as well. I was not aware of that.

Thanks for your help!

Edited 11/9/2022 23:13:07

For reference, I have my app settings set like this (on both phone and standalone app):
• 120 FPS


If you open idle and/or a game (yes, only in those 2 cases) you get the App Settings in dropdown menu under your user name:


On the app, you can find your settings here:

My problem is when I play on my desktop computer and when I hit Time Warp. It is at Legendary level. I get disconnected every time I use it.

does that only happen on browser or also on the standalone?

browser tabs are protected against all sort of errors, so if the game suddenly goes into overdrive the browser might block a few things which would cause you to DC

For me it is more or less the following situation.

Playing in browser: many lag spikes, auto-conquer is much slower to use the armies than my camps produce them. This may even lead to disconnects.

Playing in standalone: performance is great, no significant spikes, all nice. But I can't play during work as I need my monitor.

Playing in mobile app: super fast and responsive, no lag spikes, no disconnects. Maybe even a bit better performance compared to standalone. Only disadvantage: either wzib or chatting - it is just not enough screen for both. But I can even join a battle and let the phone laying unattended and later have a look what my result was :)

Thanks.

Is the speed of auto conquer dependent on my computer processing speed?

Sounds like I should download the stand alone app and play from there.

I dont think that the computer itself is the issue (I am running both the browser and the Standalone client on the same machine). It is more the additional browser layer making it slow.

Is the speed of auto conquer dependent on my computer processing speed?

I suppose it does at least a little bit, however like otto pointed out, its really the extra JavaScript layer in your browser thats slowing things down.

Give standalone a shot and let us know how thats going for you :)