Seferia here, she is about to do something that might be extremely mean to many. However, this is in the interest of finding out exactly how many of what type of base we have.
At the time of this posting, I am too tired to put much into this post, so I shall say this much: try to make certain you get build bots! Build bots will help you keep up with the changes in the alliance.
Also, for anyone above lvl 10 bases, make certain you get your motars and beams up. They will help out.
Onto the roll call! I want to know how many of what we have!
Level 12 Bases -3 (soon to be 4)
Level 11 Bases – 5 (soon to be 4)
Level 10 Bases – 15
Level 9 Bases (get up to 10 ASAP) – 14 (soon to be 15)
Level 8 Base (under construction) – 1
Now, this is more level 9 and below than what I would like. However, it does show that OVER HALF OF OUR ALLIANCE IS ABOVE LEVEL 9. There should be no given reason why a war line-up should be composed of all level 9 bases.
Once again, please try to get your bases to our min as quickly as you can. However, also do so without sacrificing too much in the process. Build bots are your friend.
11 thoughts on “Alliance Roll Call!”
I will be lvl 11 in about 24 hours, what is the best base to copy?
Build bots cost 10 bucks, I spent every free cyber coin trying (and failing) to get a bot above 2* so I refuse to give this game any money.
Time to whack at my spam settings and tell them to back down. Sorry about that.
Also, yea, they cost ten bucks. It was mostly a suggestion to aim for them since they help out a lot. It’s not a rule set in place, just a recommendation to all.
I will be lvl 11 in a few hours, what base should I copy?
A build bot costs 10 bucks…
Sorry about that! I found the reason why it didn’t show. Been a while since I’ve used this site for anything outside of my personal study tools, lol. I’ll poke at the settings for comments a bit more to clean things up a bit.
Testing again with google.
WordPress definitely works.
Does wordpress work? Where is the comment for this test?
I can see it all now, nice fix.
Yea, it acted up on my third set of tests. So, that lead me to the issue.