Combat lock - Reporting software hack
It seems a player on our server is using a software hack to create a "combat lock" on their base, so that you cannot target them. Even when they are bubbled, they are in combat lock: instead of having...
Forum Discussion
Does anybody else see something fishy in that screenshot? According to my calculation, a CP cost of 17 at 3+1 per field means that base is 14 spaces distant from yours. Now how can that be if I'm not mistaken that the maximum attack distance is 10 spaces? Here's what I get in the identical situation (per distance) http://prntscr.com/oc9083
I can see you have The Movement loaded which is a script that stopped working for me some months ago. I also see the CNCOPT button is greyed out which it seems like it shouldn't be since the base is within 20 spaces of you. The "spectate combat" button would be expected if he was attacked my your alliance in the past few minutes. The fact that the other base does not have it would mean that the last attack was more than a few minutes ago. Looking at the amount of time remaining under protection indicates very clearly that this player moved their base after the first attack on it by your alliance which gives him an hour window of protection. Now I see the problem and the solution is very simple: don't get distracted and let your 30 timer fall to 0 before you launch the next attack.
I can see you have The Movement loaded which is a script that stopped working for me some months ago. I also see the CNCOPT button is greyed out which it seems like it shouldn't be since the base is within 20 spaces of you. The "spectate combat" button would be expected if he was attacked my your alliance in the past few minutes. The fact that the other base does not have it would mean that the last attack was more than a few minutes ago. Looking at the amount of time remaining under protection indicates very clearly that this player moved their base after the first attack on it by your alliance which gives him an hour window of protection. Now I see the problem and the solution is very simple: don't get distracted and let your 30 timer fall to 0 before you launch the next attack.
