Not a fan of 3 bases. It is hard enough to built ONE good base that is uncommon. 1 attack per participant is a much simpler, robust solution. It's math, you can't beat it.
Not a fan of 3 bases. It is hard enough to built ONE good base that is uncommon. 1 attack per participant is a much simpler, robust solution. It's math, you can't beat it.
Completely maxed th10+ | 2B GG | 7.8m HH | 4753 cups
Our recruitment thread
Originally Posted by cnaf
Blocking Scouting:
The problem with this as other have said is who is going to attack without knowing what is he going to attack? I won't attack blindly especially against maxed th10s. It will be fair yes but very annoying. I will stop warring indeed at least on my th10 account
1 attack per player:
I can see one failed attack because of connection causing loss of war for the whole clan especially where score normally come close. This would work in low townhall levels but not in higher ones as the probability of failure is higher.
Make everyone equal:
Give everyone the ability to try the base they need to attack. This will make 3 stars more common so add more to stats of defenses in war base(change the way the base is copied from regular base). This should balance things & make 3 stars harder for anyone who wants to go for 3 stars(still doable) but easy enough to get 2 stars for people who aren't interested in trying for 3 stars
Bored from full inbox messages? Want to get exactly the results you want? Here is the beta version of
your best chance to get players and clans you want!
The only way is to let everyone attack the base a million times like the mod players do if everyone can simulate attacks it ends the use of the mod as a infair tool that alot of players have
So, punish everyone who is part of the fair play community because other people suck?
Lame!
Completely maxed th10+ | 2B GG | 7.8m HH | 4753 cups
Our recruitment thread
Originally Posted by cnaf
This forum is a tiny portion of the CoC gaming community and not everyone here views this solution as “moving forward”.
One attack per war base would rule out so many reasons to war. Two attacks can mean you have a chance to trial new attacks, the second attack sometimes allows lower players to gain experience against higher war bases, the second attack allows a clan to designate a cleanup attacker, the second attacks lets a clan give a new th a crack at a target knowing someone higher will be there as backup attacker, the second attack allows people to loot for one star when a win is assured. These are just a few.
Your “move forward would” kill wars for many clans, reduce the number of clans warring and increase the number of threads on mismatches as warring clans diminish.
So we just brain storming here yes.
So i suggest to add 2 options when you start the war.
- blind war (OP proposal): you ticked it if you dont want to face che**ters
- one attack per base: you ticked and you just can attack a base one time
No tick means wars as before and everybody is happy. thats your choice. end of the topic.
This doesn’t fly either. It requires both clans to tick the same boxes.
Not ticking boxes does not mean your clan flaunts the ToS (and it doesn’t mean you want to face ch**ters eithrr thanks very much) but if a clan *does* set out to che@t they will NEVER tick the boxes.
Situation unchanged but legitimate players are asked to change for no real gain.
It is fair yes but does it make game better? no imo
We need the problem solved but with minimal damage to gameplay. As a leader in clan I will need to be really more strict in who goes to war. I would mostly go with 15 - 20 instead of 30 because I have no room for error. It would be same problem for both clans but it is still a problem that needs a fix. We end up with fixing one problem & making another one imo
Bored from full inbox messages? Want to get exactly the results you want? Here is the beta version of
your best chance to get players and clans you want!
How about SC change the ToS just like they did for Blew Stacks. Use it if you want, don't use if you don't want to. If you do choose to use, you get no tech support. Simple easy fix.![]()