Not *ALL* base changes should result in a 24 hour hold on using base for challenge

[gamul1]

Hi,

I totally understand the value of not allowing new or modified bases to be used for 24 hours. We dont want people to be able to practice on enemy war bases until they perfect it. Fair play.

However, some changes should not trigger the 24 timer on a challenge. Some example where I think a base should not trigger that are:

• Switching two different level walls in the same positions. For example, As I work on my walls I work on them in my normal base. But they dont end up where i want in my war base. I dont need the higher level wall on some insignificant wall location. If we swap two walls of different levels that should not trigger the timer.
• Same thing for different level defenses of the same type. Upgrading some cannons for example. In camp I spread them around. But it always seems like in the war base the newly upgraded ones are bunched up. I'd like to swap two cannons of different levels for better effectiveness.
• I would like to also argue that if we change xbows from ground only to ground/air, without moving them, then that does not trigger a change. I have a war base and I am trying to assess what combo of ground/ground-air works best. each time I toggle the setting it triggers the timer and I have to wait 24 more hours. This sort of defeats the purpose here.
• Similarly for Infernos on multi vs single.

In short - if the base hasnt really changed in some significant way, we should still be able to use that base for a challenge right away so we can properly test the changes.

[mymolnar]

Agreed, these aren't even real base changes. Changing settings, or swaping same buildings/walls and waiting 24 hours is annoying and it barely makes a difference.

[SharkyFinn]

I think most players would agree. Supercell is already working on adjusting it so small changes don't trigger a cooldown.

[gamul1]

I think most players would agree. Supercell is already working on adjusting it so small changes don't trigger a cooldown.

Thanks. You've been my voice of reason on these forums so I was waiting to see if you had input here. Feared you might come in with 20 reasons why this was a dumb idea (and if you had it probably would have been).

[pacomius]

You have 6 spaces to save Base designs that can be challenged. What else do you want? Before moving anything simply copy the Base to another slot; the copied Base will be open for challenges. Things that seem like minor changes Che trigger some chain reactions in the long run into bigger issues.

[gamul1]

You have 6 spaces to save Base designs that can be challenged. What else do you want? Before moving anything simply copy the Base to another slot; the copied Base will be open for challenges. Things that seem like minor changes Che trigger some chain reactions in the long run into bigger issues.

You must not be using your saved based spaces very interestingly. I actually have 3 different war bases that I switch between depending on the strengths I perceive from the likely opponent that will attack me. As I am always at or near the top, its not hard to figure out who will attack my base and then evaluate their strengths. I also have two non war bases that I switch between depending on what I am trying to achieve. I am currently using that last spot as well. I'm exploring another base option. Its not finalized or useful but I tinker with it from time to time.

So, no - I dont have 6 spaces to play with. I have 1.

[SharkyFinn]

Thanks. You've been my voice of reason on these forums so I was waiting to see if you had input here. Feared you might come in with 20 reasons why this was a dumb idea (and if you had it probably would have been).

Haha. Not for this one. It's been my complaint ever since the Friendly Challenge was announced and before it came out. I hoped they'd put a percentage on it, so you could changed up to, let's say, 30% of the base and not trigger a cooldown. But just moving a decoration or a single wall piece triggers it. There have even been reports that the cooldown gets triggered even when changes aren't saved. That should never happen.