Combat lock - Reporting software hack

Yes, "Spectate combat" is only available for same alliance's members.
And yes, if a forgotten base attack any base "Spectate combat" is enabled too for his partners.

sweet i screwed up the words and yet some how was still right on the point , much better than what i wrote first thought for some reason the date saying bubbled till "Tomarow" ment he just sector jumped lol but for like the 15th time i opened the screen shot before i hit go on the com mment seen everything said tommarow

"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.

"M8u8r4r4a0796;c-2078172" wrote:
while bubbled his base alerted, not under attack. it is just from the defnese needing to heal from a repsawn, not like an attack lock from a current attack whats **** weird about that picture though is a red coloured player to have a "visit base" button when i thought it was only "visit" when looking from inside the your own allaince anything outside should always be attack buttonthen grayed out if a reason it cant current be attacked

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"

"justinsaidso;c-2079137" wrote:
KeJorn/GreyMouser is clearly faking screen shots or cheating himself. Ignore that fool. He is looking to cause problems and harass me daily. He also has the passwords to 12 accounts of other players so he likely gets confused easily.

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.

The stuck in combat mode was a server side error. It probably cleared when they restarted the server after the 19.3 update.

"gamerdruid;c-2084474" wrote:
The stuck in combat mode was a server side error. It probably cleared when they restarted the server after the 19.3 update.

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...