Revenge Solution: Inspection List

So, you probably all know that there isn't often a chance to revenge. When I click on all revenge buttons in my defense log, there are maybe 3 or 4
players who are not online or have no shield. And of course the ones who you could attack, have no loot. So I thought about that problem a while.

Of course it would destroy the game balance if you could revenge everybody, even if he has a shield. It would be very dangerous to attack, and that shouldn't happen. So this is my idea of a balanced revenge system solution:

You can put ONE player of your defense log on an inspection list. If this player is offline and doesn't have a shield, you will get a notification. If you hurry up, you can attack this player before he gets a shield again. So you can look which player would be worth to attack and then put him on your inspection list.

Balancing:
1. You can use your list only once a day for one player.
2. You can't use your list if you are a champion or above, because you would attack simply anybody who is destroyable.

Hope you like it! Please comment!

That is ruled out.

Quote:

---

Originally Posted by MustafaNation

That is ruled out.

---

? Nope. It's only ruled out to share revenges with your clan mates.

This still doesn't fix the underlining issue that created the current state of Revenge.

The reason revenge was nerfed was to prevent Cheap Shielding. Your feature would only bring that feature back, the only difference is you basically made it GUARANTEED that you'll get the Cheap Shield while before, you at least had to time things right and still heavily relied on luck.

Good try, back to the drawing board...

Quote:

---

Originally Posted by AxionXD

This still doesn't fix the underlining issue that created the current state of Revenge.

The reason revenge was nerfed was to prevent Cheap Shielding. Your feature would only bring that feature back, the only difference is you basically made it GUARANTEED that you'll get the Cheap Shield while before, you at least had to time things right and still heavily relied on luck.

Good try, back to the drawing board...

---

Sorry I don't understand why this feature would give you shields easier? Maybe you misunderstand the idea? Sorry my wording is sometimes a bit bad

So you could put one player of your defense log on a watch list, your device will give you a notification if this player is ready to be attacked by you.

Quote:

---

Originally Posted by pixlon

Sorry I don't understand why this feature would give you shields easier? Maybe you misunderstand the idea? Sorry my wording is sometimes a bit bad

So you could put one player of your defense log on a watch list, your device will give you a notification if this player is ready to be attacked by you.

---

You put your clan mate on that list and give them a shield when they are ready. If You'd like a more indept explanation of what Chield Shielding through Revenge is, search for similar threads on the forum.

Quote:

---

Originally Posted by AxionXD

You put your clan mate on that list and give them a shield when they are ready. If You'd like a more indept explanation of what Chield Shielding through Revenge is, search for similar threads on the forum.

---

Of course you can only put people on the list who attacked you and where you can have revenge. Clan mates cannot attack each other and even if possible it would be extremely unlike.

Quote:

---

Originally Posted by pixlon

Of course you can only put people on the list who attacked you and where you can have revenge. Clan mates cannot attack each other and even if possible it would be extremely unlike.

---

What the other person is implying is that up in the high leagues (Titan 1- Legend) it is quite common for people to attack one another who know each other or even attack their own accounts. Many people that high have more than one account. They could easily attack one of their accounts, put it on a watch list, go offline, and immediately attacking it and drop one troop. There cheap shielding. This idea will bring that back very easily.

Quote:

---

Originally Posted by pixlon

Of course you can only put people on the list who attacked you and where you can have revenge. Clan mates cannot attack each other and even if possible it would be extremely unlike.

---

I forgot I had this pre-made in my saved folders:


__________________________________________________ __________________________________

Revenge was modified in the past to combat "Cheap Shielding".

Cheap Shielding
What is it? This was a major issue in higher league game play. With there being lower population and thus a low pool for potential matchmaking, higher league (Champions) players would routinely see the same bases multiple times. Some creative clasher(s) discovered a way to take advantage of this phenomena.

A member of a clan who wanted a free shield without risk losing his loot would coordinate with a clan mate (and now a days can easily use an alternate account) and expose his TH while leaving the clan. He would then time it so as he exited the game and became available for attack, his friend or alt would begin searching. Noting that there's so little bases available in the higher leagues, it was quiet common and almost too easy to find this base.

So now this player got a free shield but it doesn't end there. The second player, or alternate account, now has this player on his defense log. So now when the second player wanted a free shield, it was even easier to get it because all he had to do was leave the clan and time it so the first player, or alternate account, would revenge him immediately.

This kept everyone's loot and trophies safe but made the Cloud (matchmaking) problem even worse.

Revenge - As It Is Today
So how did this affect revenge? Supercell added a 5-7 minute buffer so when someone logs out, they are placed in queue for regular matchmaking. Revenge is NOT available during this 5-7 minute period.

With anyone in Crystal or above, where league bonuses for TH sniping is profitable, you are unlikely to survive matchmaking longer than the 5-7 minute buffer. As an exposed TH9 in Crystal 2, I get sniped within 30 seconds. So there are probably dozens if not hundreds of defense logs that I appear on with players just like you hitting my revenge button and can never get to me.

How many players do you think are also hitting your revenge button but are unable to get through?

The current revenge system protects you as much as it protects them.

Notifications of User Status
I know a common question and concern, even to the extent of accusing players of h@cking, is how could one second a player is "online" then all of the sudden he has a shield.

The answer to this question is, the status of being online over rules the status of having a shield. Just because a user is online doesn't mean he broke his shield. He could be using his war attacks, logged on to build troops for future use or otherwise not breaking his shield. As he logs out, the message then becomes "shielded" without seeing "currently under attack"

Easier Revenges
Do we really want easier revenges? Some suggest bypassing shields or online protection.

Let me ask you this:

How many people have you attacked today? This week? This month?
How many people have attacked you and took enough loot for you to get Nesson Angry?

Any decent farmer will have far more people wanting to revenge them then they have to revenge. By making it easier, or making it so revenges can bypass shield, imagine what you may wake up to the next day after a full day of farming. Imagine all 10 people that you rocked for 350k each and 2k of dark elixir are all able to study your base, build the perfect war army, bypass your shield and take it all back. ALL 10 OF THEM. Now imagine if you did more. Attacked 20, 30, 40 people....

I would not want to open myself up to that. The pandemonium that would result for something like this would be equivalent to the internet's reaction the day after Game of Throne's Red Wedding episode aired.[/QUOTE]

The notification that is placed could cause unnecessary strain on SC's servers, therefore I see no reason to implement this.