Combat lock - Reporting software hack
June 27, 2019 6:15AM
edited June 2019
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 a grayed out option for attack, it says spectate combat. See image.
Because it happens when they are bubbled, it is a clear software hack, not an actual "lockdown attack" from another alliance (with no diplo).
I have a screenshot: https://prnt.sc/o79o5j
Because it happens when they are bubbled, it is a clear software hack, not an actual "lockdown attack" from another alliance (with no diplo).
I have a screenshot: https://prnt.sc/o79o5j
0
This discussion has been closed.
Howdy, Stranger!
Replies
Sometimes a player can end up in perpetual attack until they refresh their screen. Maybe this is what has happened.
Certainly an interesting observation.
Well if you gave us the option to delete our posts, I could have. With this account, I could post the screenshot. I could not with the other.
This is not an issue of my scripts.
He has it applied to one of his bases and remains on that base wherever he moves it. Other players have seen the exact same thing on THAT base. He has something applied, that is evident. Screen refresh is not the issue either. I have tried everything to see if it is just a visual glitch. It's not.
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.
While you are here, you should feel free to shed some light onto the issue here and give me your side of the story. Here or via PM.
And yes, if a forgotten base attack any base "Spectate combat" is enabled too for his partners.
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.
Yes, another point of using that image: A BUBBLED PLAYER CANNOT BE ATTACKED.
Yet it literally says, " SPECTATE COMBAT"...
Therefore we know:
(1) He is not under attack by another player
(2) There is something very suspicious about why it shows up on a bubbled player.
Again, as I stated to the other guy, this was after the attacks.
This was not in the heat of battle.
He is bubbled, because I finally killed him, despite his attempt to prevent an attack.
Also, Where are you seeing a visit button?
Looking at the images, there is not "visit button"
Allow me to introduce (belatedly) JustinSaidSo. Come to our server, Wrath21 and ask anyone not in (or formerly in) Syndicate and you will find nearly everyone on that server knows Justin to not only lie, but intentionally deceive, and deflect the very things he is guilty of onto others. Don't take my word for it... seriously, ask around. Even some of his former players have left and are fed up with his lies. The fact he uses cheats only seems to prove his character.
But about the 30s exploit you talk about in you other thread that give 30s to the other alliance when you are attacking them it's a known exploit that is here since 1 year : https://forums.ea.com/en/commandandconquer/discussion/218694/post-combat-lock/p1
I can't give more details on it since I don't know what they are using to do this, but I know it exist, I was fighting an alliance that started to use this exploit, I was angry against them since they were already winning this world, no need to cheat, I received a message from CIC who apologized for using that exploit, and it stopped.
This problem has never been taken seriously
No doubt, it would be server side... ANY thing that can be exploited must first be exploitable on the server side.
The real question, is what caused the issue in this specific case. A random fluke? Or an intentional effort to exploit it? Judging by the things we have seen from this particular alliance/player, my gut tells me it is an intentional exploit initiated by them (via script or whatever).
Saying it was resolved server side does not remove culpability of the player one bit. Just says, yes, this is something the devs can fix from their end. Sadly, in the process, other useful scripts became disabled. In the end features vs vulnerabilities becomes the issue the devs have to weigh...