Ideas on Auto Reject clan invites and Donation GUI in Chat

This is minor but:

Auto Reject Clan Invites - Sometimes as we all wait for our troops to finish building and we are currently clanless (with intent to stay that way) we get swarmed with unwanted clan invites from people throwing out invites to anyone who types a letter in global chat, because we say "Hi" in global as we wait and kill time. My suggestion is (similar to the opt out of war feature) a feature where you block/auto-reject all incomming clan invites sent. I have seen quite a few people on global who just dont want a clan and one can easily amass 20 invites in a matter of 3 minutes for just saying "Hi" in global chat

Text or Graphic Depiction on what has been donated all ready (even maybe by whom) - There's a couple of things to this one. A) In clans i have seen requests for (2 Wizards, 3 archers, a jaberwokey and bill gates). Pretty much a specific menu order. People donate but with only the green bar, they dont know what's been donated all ready and what is still needed, so there's a guessing game involved. A text and/or graphic representation of what has been donated would be helpful in these many cases. And B) (just as an added bonus) some sort of representation of who donated when you look at your cc so you can pass your thanks, or try to find the one guy who keeps donating what isn't asked for to up their donation numbers to make themselves look good, while bringing down the team some. The last issue has been a chronic issue in many clans.

Just a few ideas I had. Hope they will be considered! Thanks for the support SuperCell!!! :D

I would expand it the invite idea to maybe a filter..

Accept invites from clans that are a certain level only, a minimum number of members or war wins.

But, great idea none the less.

So I can't request level 7 catapults or level 11 amplifiers?


When it comes to donations, In almost every case you can figure out what's been donated and what's needed by doing a little math, or if it's that important, ask.

On the whole, the features you're requesting would be nice, but in terms of cost/benefit, the amount of coding needed compared to the relatively minor nuisance the cause, it doesn't really seem like the sort of thing that would be a priority.