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
"crackfed;c-2076151" wrote:
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?
Wow, I missed all these comments. Dealt directly with the developer and never came back to check.. but I am back now for yet another reason involving the SAME guy/alliance...
But let's answer your questions real quick first:
Those images were from bases not close enough to attack thus the attack button is grayed out (second image) showing what it SHOULD look like. The base was NOT under attack, even recently at that time... but instead showed "Spectate combat" but that base was not in combat.
Understand, this base (then named Randy Savage, now Toxic Love), continued to always be in "spectate combat mode"... every time you logged in and looked at the base, it showed "Spectate combat"... no other base showed this. And this base was never under attack (no red line across to indicate an attack). This went on for WEEKS afterwards.
After a recent update, suddenly Toxic Love is no longer stuck in "spectate combat". Hmm.. maybe their script/hack finally got disabled.
Your other points are moot as again, never claimed the image was from the base attacking him.
Sorry in the middle of battle, I am not saving screenshots, esp when the issue is persistent even after the battle.
