Stronghold bug and network errors in WW

alfabobz

New member
Joined
Mar 14, 2017
Messages
1
I have never had a network error or crash in world wars until just recently. It is not my connection, as there is no yellow spinner present when this happens. I was 2+ minutes into a world war battle with 4 stars, when I then deployed my stronghold troops and got an instant network error stating my player ID. I've also been getting this error frequently in normal battles, around 1 or more a day (these may be related to the stronghold issue, but I cannot confirm). When this happens, I've been checking my internet connection and everything is up and running. In fact, the only time I've been able to pinpoint a network issue on my end is when I get a yellow spinner.

1. You guys need to implement a resume feature for when people's games crash or disconnect. This will stop the complaints, keep players from quitting and fixes future issues that will arise as performance continues to drop over time. Having to wait a minute while restarting the game... not a problem. Being set back by several hours due to something beyond our control... unacceptable.

2. As mentioned in #1, the game has become more unstable over time likely due to memory limitations of older devices (in addition to new bugs). It wouldn't hurt to include settings that could be changed to increase performance or decrease memory usage, for example lowering graphics or special effects.

3. The compensation for those who experience the world war stronghold bug is not acceptable. It costs ~100 crowns just to instant train the barrack troops lost. What about generals, tactics, stronghold armies, air troops, resource costs, coalitions, ect?
 

ELITE JAG

Approved user
Joined
Dec 8, 2015
Messages
146
Alfabobz, it is not your connection. It must be some kind of code corruption Nexon/BHG inadvertently introduced with their latest update. Tons of players have been submitting CS tickets, but of course, all we get is the same response: check your wifi, reboot your device... we feel for you, but... just never ending excuses and not a word about what the developers may or may not be doing to correct this code error...
 
Top