I have three QoL improvements I would love to see and one builder base QoL improvement I could take or leave.
1.(Low priority) Block someone from sending spam friend requests. Or at the minimum remember the request was previously viewed and make it a one time notification. (Like when there is an event...notified once, when viewed, not notified again)
2.(Medium priority) Allow me to set a different war cc request for each war base. This can be done by slot (you write a request assigned to each slot), or by making a request by tapping on the cc in the editor and filling in the request. Rationale: I have three war bases I cycle through, War Base 1(WB1) is designed to use Hound/Loon, WB2 is designed to use IceGolem/Drag, WB3 is designed to use a BabyDrag and three valks. If I change my active war base, my request should automatically update with it. For implementing using cc in editor, if no request has been assigned to this base, default request is last used request like it is now.
3.(pretty please) Saved this for last because it is the least likely to see, but for me, the one I want the most. The easiest way I see to make this improvement is to be able to upgrade a wall (or any building) in editor mode.
I want to choose which wall I upgrade based on its location in my war base without having to suffer a 24 hour cool down. Currently the only way to do this is to copy my war base as a home base, activate it as my home base, then perform the upgrade. However, I use all my home base slots, so I can't copy my war base as a home base. Even if I did, I may have an obstacle I don't want to remove that prevents me from activating my copied war base, ultimately though I don't think I should have to allocate one war base slot and one home base slot to the same layout simply to ensure I upgrading the wall piece I want to. Slots are valuable otherwise additional slots would be free.
A cooldown because I switched two wall pieces frustrates me every time. And maybe I should not be so concerned about where my newly upgraded wall or two goes, but hey if the upgrade didn't matter, why do it?
An alternative to this is to allow a building swap to occur without a cooldown provided they are the same building (but different levels), but that seems like code that will take much longer than next update. Allowing an upgrade while in editor mode seems much more (but still not very) likely.
Just thought of a fourth but its builder base(lowest priority for me)...when I am using clock tower boost and my army is ready but my hero is not, the fact that he is greyed out is not much of an alert. I don't think a "Do you want to heal your hero for x gems?" message is needed, but maybe just add something more visually stimulating.

