I’m doing something similar to AwesomeDoud and upgrading towers on multiple maps. Confirming with other alliance members in the realtime chat, maps are not switching while logged in, or when I log out. For me, seems to be stuck on map 1 for enemies and alliance members. I see map 3 when loading/reloading the client. (Private Threepwood is my in game handle) Note that i’ve Reconstructed map 1 to my high defense layout because this is not reliable.
We’ve noticed that other alliance members maps also take a while to change when testing each other’s layouts. We almost kicked a guy 2 wars ago, because he had no towers/defense. we thought he was being difficult, but other members noted that it takes hours or longer sometimes for maps to switch and be visable to others. Is there some server side process for which a user seeing his own maps is stored in one place, but when attacked is sourced/stored/cached somewhere else that the sync is sometimes failing? Or perhaps a sync operation that’s happening async and perhaps out of order updates are occurring when switching quickly?
Here’s some detail we’ve worked out: (should see map 3, but everyone sees map 1)
-Up until a day ago, I never use map 1 (or map 2), only to upgrade towers. However the battle log shows both regular map and war folks seeing map 1. (Map 2 however hasn’t been attacked in over a 40 days) Alliance members in the chat while i’m Logged in with map 3 selected, still see map 1 when testing my defense.
-When I upgrade a tower, I’ll Press the collect button which auto-switches the map. Then initiate the next level upgrade to the same tower, and manually switch back to map 3. Never on map 1 for more than a minute or so.
-Working with alliance members, does a not seem to be a client side issue with them (caching, etc). One member tried logging out on windows and back in, same map. Same member tried using iOS client (which he never uses) and still saw map 1.
-This would seem to indicate a server side issue where either the client is not sending which map, being dropped over the wire, or the server is not syncing/storing/caching the information properly.
-That said, if I completely kill my client in iOS causing the client to reconnect/resync, map 3 still shows up, followed by a “*****?”
Hope that helps @CaptainMorgan and @Madlen