Unfair advantage for some dishonest people

[Twistom]

I wanted to post an official thread/response from Supercell on the issue that many of you have brought up. That issue is the use of airplane mode to exploit the game and gain a tactical advantage over opposing clans during Clan Wars.

It is very important for us that Clash is fair for all our players, and that no-one has an unfair advantage in the game. We are already working on a solution for this, but unfortunately the problem is hard to solve without causing problems for the majority of players, who choose to play fairly.

We have taken steps in the past in order to ensure players with poor connections can continue their attack even if they have issues with their connection. This reduces the amount of players getting kicked out of the game while attacking, but unfortunately some have chosen to abuse this feature in order to gain an unfair and unethical advantage.

It is difficult to detect if the connection was cut on purpose by the player, or if it was lost due to a slow or weak internet connection. Still, we are working hard to get this issue fixed, and we are trying out several different alternatives. We realise that the current situation must be very frustrating for clans that value fair gameplay and we apologize for any inconvenience.

Thank you guys for bringing this to our attention, and for your patience on this matter.

Clash On!

-Steve

I have an idea to solve the issue.

Supercell can add a verification process on the client and server. Whenever the player place the FIRST troop on the ground. The client will automatically sent sever a verification code to verify connection. After receive the verification code from client, the server will send back a confirmation code to client to ensure the attack. If the confirmation code doesn't receive from the server after certain seconds, the game will automatically restart.


Next I will explain how this WORK

1. When the player click attack and place the first troop (whatever troops or spells on the ground), the client will send server a code, when the server receive code, the server will automatically send the confirmation code back.

Situation 1: Player continuous to attack

The client will receive the confirmation code and keep working.

Situation 2: Player activate flight mode

When player place the first troop, even he activate the flight mode, the client will still send out the verification code. However, due to disconnection from the server, the client will NOT receive any confirmation code back. After a designated delay, the game automatically reload.

Situation 3: Player with weak connection

In this situation, player can still send out verification code and receive confirmation code because he is not completely d/c from server.



NEXT, The reload delay time

As I talked above, if the client didn't receive any confirmation back. It will reload automatically and immediately. The reload delay can be designated upon consideration of average pings. I suggest the delay time can be set at 500ms.



Delay time consideration

Short delay: Short delay make more accurate adjustment to players' behavior. For weak internet connection user, it is also fair. Their game reload immediately if the internet is too weak to receive confirmation. In fact, they didn't make the attack. They also have no loss.

Long delay: Long delay allows weak internet player to have a smooth experience. However, drawbacks is the delay time can be used to cheap like before even it is short.



Do you guys have any comments, please let me know. I will explain more.

Hope this will help to keep the game FAIR and FUN!!!!!

[Twistom]

I have an idea to solve the issue.

Supercell can add a verification process on the client and server. Whenever the player place the FIRST troop on the ground. The client will automatically sent sever a verification code to verify connection. After receive the verification code from client, the server will send back a confirmation code to client to ensure the attack. If the confirmation code doesn't receive from the server after certain seconds, the game will automatically restart.


Next I will explain how this WORK

1. When the player click attack and place the first troop (whatever troops or spells on the ground), the client will send server a code, when the server receive code, the server will automatically send the confirmation code back.

Situation 1: Player continuous to attack

The client will receive the confirmation code and keep working.

Situation 2: Player activate flight mode

When player place the first troop, even he activate the flight mode, the client will still send out the verification code. However, due to disconnection from the server, the client will NOT receive any confirmation code back. After a designated delay, the game automatically reload.

Situation 3: Player with weak connection

In this situation, player can still send out verification code and receive confirmation code because he is not completely d/c from server.



NEXT, The reload delay time

As I talked above, if the client didn't receive any confirmation back. It will reload automatically and immediately. The reload delay can be designated upon consideration of average pings. I suggest the delay time can be set at 500ms.



Delay time consideration

Short delay: Short delay make more accurate adjustment to players' behavior. For weak internet connection user, it is also fair. Their game reload immediately if the internet is too weak to receive confirmation. In fact, they didn't make the attack. They also have no loss.

Long delay: Long delay allows weak internet player to have a smooth experience. However, drawbacks is the delay time can be used to cheap like before even it is short.



Do you guys have any comments, please let me know. I will explain more.

Hope this will help to keep the game FAIR and FUN!!!!!

[Twistom]

Guys please like!! we need to make it FAIR

[Rational1]

It seems that a majority of people are exploiting this update, in a fact every big update in any game has a chance of these exploits, I do have a hope this will be fixed soon though.

The last three wars we have had people ghosting and the last war all of their players were ghosting we went to visit them, as we do everyone at the end of each war and they were amazed we weren't doing it they said everyone they had had a war with was doing it. This may have started as a small minority ghosting but more and more people are starting to use it as it will be the only way to win. We have taken a stand not to ghost and will not go to war until this is fixed by supercell. Honest clans will stop playing clan wars and all that will be left is the ghosting clans.

[storii]

I have an idea to solve the issue.

Supercell can add a verification process on the client and server. Whenever the player place the FIRST troop on the ground. The client will automatically sent sever a verification code to verify connection. After receive the verification code from client, the server will send back a confirmation code to client to ensure the attack. If the confirmation code doesn't receive from the server after certain seconds, the game will automatically restart.


Next I will explain how this WORK

1. When the player click attack and place the first troop (whatever troops or spells on the ground), the client will send server a code, when the server receive code, the server will automatically send the confirmation code back.

Situation 1: Player continuous to attack

The client will receive the confirmation code and keep working.

Situation 2: Player activate flight mode

When player place the first troop, even he activate the flight mode, the client will still send out the verification code. However, due to disconnection from the server, the client will NOT receive any confirmation code back. After a designated delay, the game automatically reload.

Situation 3: Player with weak connection

In this situation, player can still send out verification code and receive confirmation code because he is not completely d/c from server.



NEXT, The reload delay time

As I talked above, if the client didn't receive any confirmation back. It will reload automatically and immediately. The reload delay can be designated upon consideration of average pings. I suggest the delay time can be set at 500ms.



Delay time consideration

Short delay: Short delay make more accurate adjustment to players' behavior. For weak internet connection user, it is also fair. Their game reload immediately if the internet is too weak to receive confirmation. In fact, they didn't make the attack. They also have no loss.

Long delay: Long delay allows weak internet player to have a smooth experience. However, drawbacks is the delay time can be used to cheap like before even it is short.



Do you guys have any comments, please let me know. I will explain more.

Hope this will help to keep the game FAIR and FUN!!!!!

Latency can often be far worse than that (having worked on a major MMO title I've seen it quite a bit)... The delays need to be pretty long.. Many seconds at least to avoid a lot of disconnects for people with bad connections.

However, a round-trip message to confirm the client is still connected to the server is still a good idea. Instead of disconnecting, just pause the battle if the message doesn't come back after a second or two. Cover the battlefield with some message so the player can't study what is going on and gain an unfair advantage. After the message comes back the player can finish the battle without any more interruption.


OR,

Supercell could store the number of times a player disconnects after pressing attack but before sending in troops and the number of times they disconnect after sending in troops. As the former gets larger relative to the latter, you know the connection is likely being tampered with deliberately. At that point you could make pressing attack final and disconnect a loss. Focusing on detection rather than prevention would have the benefit of unfairly hurting players with poor connections, but at the cost of letting it go a few times first. There's any number of other detection methods that might be better.

Lets face it, there are dozens of good solutions. Supercell, please pick one and get it in ASAP. Or give everyone that "practice" button someone mentioned above, until you find a solution you like. The present situation is intolerable.

[Quantor]

It's wearing a bedsheet over your head while doing Clan Wars.

what's up with you SSofJetlife ? Trying to scam forum users by giving them incomplete informations ?

you've forgotten to tell him about the most important thing: old rusty chains..... For ghosting you need also old rusty chains...

it isn't real ghosting if you don't have chains....

[Gavman2000]

[PeterPunk]

Quit whining! This is not a problem. If you can't beat them, join them. When we discovered that we are being ghosted, we started ghosting right back. Now we ghost all the time ha-ha.

If you wanna whine about something, whine about real issues, like the sucky loot that keeps on sucking month after month. And bunny hoppers, which are a big reason why loot sucks for the rest of us. These are the real problems that I hope SC concentrates on.

[J1M808]

Our clan are currently being ghosted by the clan "haarknödel" ! Please fix this quick SC!

[zellnera]

To complicated! And to much traffic between server and client involved.

Better solution:
In clanwars and revenge you have anyhow the possibility to scout the base. So the easiest way would be to count the attack as soon the attack button is pressed. That insures that ghosting would stop imidiettly on clanwars and revenge.
For normal attacks the behaivior could stay like it is since the likelihode of been matchted with the same opponent is very small.