Same goes for all you highly skilled lets blue up nobody has any respect for you DNS loser.

The really damning issue for me is that a few months ago I sniped 2 KEQ districts on the same day. KEQ ticketed CCP when our battle fell last in the order (the one which would have been efficacious and would have resulted in their previous battles being nullified) because we didn't hit it first so CCP refunded the pack and said try again.

And then DID NOT REPORT it when the later battle on the same day had us going first but was obviously nullified due to a battle that occurred after.

Of course, having no knowledge at the time...I reported it to CCP but was unable to articulate exactly what happened, I blame myself for not recognizing the insidious nature of why they would report one set of clone packs hitting....but not report the other in the same manner. Now it seems to make perfect sense.

It was assumed I simply hadn't tried to re-attack after the win, and CCP only changed the clone count to reflect their battle loss.

KEQ reported the bug when it benefited them...and did not when they knew it favored them and that our win wouldn't count due to the glitch.

Disappointing. No need for anything more than CCP editing their district to remove the 150 clones and implementing the reattack I intended to send.

Hope to see KEQ on the battlefield soon.

Abusing 'working as intended' bad mechanics like district locking is indeed different than double, triple, or quad locking districts, and reporting it only discriminately.

I could be totally off, just the way it felt after everything that has happened. I'm wrong a lot.

If they did submit a ticket for yesterdays battle BEFORE it took place, than bravo to them and I think we all owe KEQ an apology.

But sadly I'm almost positive they will conjure some excuse why they did not "well we've reported it so many times before and so we decided not to report these cause they don't do anything about it...except when an enemies battle is last..."

Why anyone would want to join a corporation that has thrived off of gltiching everything possible just to hold land is beyond me.

As a person who watched all of this happen I cannot express enough how this is 100% true in every way.

KEQ should feel ashamed of themselves for not reporting this.

Why anyone would want to join a corporation that has thrived off of gltiching everything possible just to hold land is beyond me.

............really long post........

Why anyone would want to join a corporation that has thrived off of everything possible just to hold land is beyond me.

LOL
Isn't that what FA and all the other add-on corps did by joining DNS?
The amount of irony in this thread is incredible; exploiters calling out exploiters, cowards calling out cowards, etc, etc.
I am sure DNS corps will now quad-lock "so CCP will fix it".

sometimes to dispense justice, you have to do unjust things.

Whatever you have to say to justify your own actions (while condemning other players' actions).

The really damning issue for me is that a few months ago I sniped 2 KEQ districts on the same day. KEQ ticketed CCP when our battle fell last in the order (the one which would have been efficacious and would have resulted in their previous battles being nullified) because we didn't hit it first so CCP refunded the pack and said try again.

And then DID NOT REPORT it when the later battle on the same day had us going first but was obviously nullified due to a battle that occurred after.

Of course, having no knowledge at the time...I reported it to CCP but was unable to articulate exactly what happened, I blame myself for not recognizing the insidious nature of why they would report one set of clone packs hitting....but not report the other in the same manner. Now it seems to make perfect sense.

It was assumed I simply hadn't tried to re-attack after the win, and CCP only changed the clone count to reflect their battle loss.

KEQ reported the bug when it benefited them...and did not when they knew it favored them and that our win wouldn't count due to the glitch.

LOL
Isn't that what FA and all the other add-on corps did by joining DNS?
The amount of irony in this thread is incredible; exploiters calling out exploiters, cowards calling out cowards, etc, etc.
I am sure DNS corps will now quad-lock "so CCP will fix it".

You're completely incorrect on what went down, Zat, which is understandable because you were able to see all of 1/3 of the information related to the corporations involved. I own the corporation which was locking KEQ's districts at the time, and which was party to many of the attacks in this particular instance.

The multiple attacks which engaged were completely unintentional. The attempt was to prevent you from sniping the lock from the districts, so naturally there were multiple directors online in the locking corporation who were spamming attacks immediately when the districts became unlocked. You, similarly, had multiple people online. This was obvious since Fatal Absolution registered two attacks simultaneously against at least one of the districts (the thing which prompted you to report anything in the first place). The way this particular mechanic works, simultaneous attacking of a single district instigates it. Simultaneously attacking a single district is also the most efficient sniping/locking/attacking strategy under conventional mechanics.

Two characters reported everything that went on that night- a director character from KEQ and the CEO character of the locking corporation. Your ticket and ours weren't touched until about 8 hours before the battles were set to occur. When they were, the intervention was mishandled. It turns out that battle SCHEDULING and district LOCKING are handled by two different parts of the infrastructure. Typically these pieces are interlinked in such a way that a district is always deemed UNDER ATTACK if a subsequent battle is scheduled on it.

When GM's intervened, the districts were all but one rescheduled so that only one corp was attacking them. Additionally, each of those districts was forced into ONLINE status by the GM despite battles being scheduled on them. This allowed other corps to schedule MORE battles. This was rather early in the day- STB managed to attack one of the onlined districts, the rest were simply re-locked. Again, we had multiple battles from multiple corporations scheduled on each district.

I filed a SUBSEQUENT ticket immediately and attempted to contact CCP personnel to further resolve these issues. In fact I actually skipped a class that day so that I could do it as fast as possible in order to give everyone the best chance of resolving the issue quickly. No additional administrative action was taken that day.

There were two battles which involved Fatal Absolution. The first had been rescheduled in such a way that FA's attack was the only one against that district. You lost.

The second battle was on a district which had been onlined by GM's. My corp was used to attack the district after it had been onlined in the middle of the day since STB had already attacked a district onlined in this way. Thus there was a battle subsequently scheduled on it for the NEXT day. This nullified the results of the match on that district, which we lost.

That night I filed a THIRD ticket reporting all of these results. The district which STB had attacked didn't have any FA battles on it in the first place. The GM's decided to nullify STB's scheduled attack against that district. For whatever reason, their decision on the second district in line was to allow the current state to hold. Obviously we didn't file any more tickets because this was their last ruling on the entire thing.


So yeah Zatara, it'd be best if you didn't go talking about situations where you know less than 1/3rd of the story. The only thing which was intentional, and ever has been, is using multiple directors to lock districts because it's the only strategy that makes sense. What else are people supposed to do? Allow their opponents to have a head start in aggressive, competitive scenarios because the background mechanics are bugged?

You're completely incorrect on what went down, Zat, which is understandable because you were able to see all of 1/3 of the information related to the corporations involved. I own the corporation which was locking KEQ's districts at the time, and which was party to many of the attacks in this particular instance.

The multiple attacks which engaged were completely unintentional. The attempt was to prevent you from sniping the lock from the districts, so naturally there were multiple directors online in the locking corporation who were spamming attacks immediately when the districts became unlocked. You, similarly, had multiple people online. This was obvious since Fatal Absolution registered two attacks simultaneously against at least one of the districts (the thing which prompted you to report anything in the first place). The way this particular mechanic works, simultaneous attacking of a single district instigates it. Simultaneously attacking a single district is also the most efficient sniping/locking/attacking strategy under conventional mechanics.

Two characters reported everything that went on that night- a director character from KEQ and the CEO character of the locking corporation. Your ticket and ours weren't touched until about 8 hours before the battles were set to occur. When they were, the intervention was mishandled. It turns out that battle SCHEDULING and district LOCKING are handled by two different parts of the infrastructure. Typically these pieces are interlinked in such a way that a district is always deemed UNDER ATTACK if a subsequent battle is scheduled on it.

When GM's intervened, the districts were all but one rescheduled so that only one corp was attacking them. Additionally, each of those districts was forced into ONLINE status by the GM despite battles being scheduled on them. This allowed other corps to schedule MORE battles. This was rather early in the day- STB managed to attack one of the onlined districts, the rest were simply re-locked. Again, we had multiple battles from multiple corporations scheduled on each district.

I filed a SUBSEQUENT ticket immediately and attempted to contact CCP personnel to further resolve these issues. In fact I actually skipped a class that day so that I could do it as fast as possible in order to give everyone (FA, KEQ, and our alliance mates) the best chance of resolving the issue quickly. No additional administrative action was taken that day.

There were two battles which involved Fatal Absolution. The first had been rescheduled in such a way that FA's attack was the only one against that district. You lost.

The second battle was on a district which had been onlined by GM's. My corp was used to attack the district after it had been onlined in the middle of the day since STB had already attacked a district onlined in this way. Thus there was a battle subsequently scheduled on it for the NEXT day. This nullified the results of the match on that district, which we lost.

That night I filed a THIRD ticket reporting all of these results. The district which STB had attacked didn't have any FA battles on it in the first place. The GM's decided to nullify STB's scheduled attack against that district. For whatever reason, their decision on the second district in line was to allow the current state to hold. Obviously we didn't file any more tickets because this was their last ruling on the entire thing.


So yeah Zatara, it'd be best if you didn't go talking about situations where you know less than 1/3rd of the story. The only thing which was intentional, and ever has been, is using multiple directors to lock districts because it's the only strategy that makes sense. What else are people supposed to do? Allow their opponents to have a head start in aggressive, competitive scenarios because the background mechanics are bugged?

Quad attacks don't happen on accident.

I'm sorry but outright cheating to make a match not count is never justified no matter how much you may hate your enemy. Use the tools in the game (no multi-attack exploiting isn't a tool) to accomplish your goals.

I'm sure CCP will make the right choices in dealing with the situation.

I dont think you understand yet, everytime we lock we have multiple people locking, everytime we snipe we have multiple sniping. Everytime, without fail, why do you think we have so many people over there.

And we have had multiple people locking too, not once did we come down with a quad attack.

And we have had multiple people locking too, not once did we come down with a quad attack.

The really damning issue for me is that a few months ago I sniped 2 KEQ districts on the same day. KEQ ticketed CCP when our battle fell last in the order (the one which would have been efficacious and would have resulted in their previous battles being nullified) because we didn't hit it first so CCP refunded the pack and said try again.

And then DID NOT REPORT it when the later battle on the same day had us going first but was obviously nullified due to a battle that occurred after.

Of course, having no knowledge at the time...I reported it to CCP but was unable to articulate exactly what happened, I blame myself for not recognizing the insidious nature of why they would report one set of clone packs hitting....but not report the other in the same manner. Now it seems to make perfect sense.

It was assumed I simply hadn't tried to re-attack after the win, and CCP only changed the clone count to reflect their battle loss.

KEQ reported the bug when it benefited them...and did not when they knew it favored them and that our win wouldn't count due to the glitch.

Disappointing. No need for anything more than CCP editing their district to remove the 150 clones and implementing the reattack I intended to send.

Hope to see KEQ on the battlefield soon.

Abusing 'working as intended' bad mechanics like district locking is indeed different than double, triple, or quad locking districts, and reporting it only discriminately.

I could be totally off, just the way it felt after everything that has happened. I'm wrong a lot.

If they did submit a ticket for yesterdays battle BEFORE it took place, than bravo to them and I think we all owe KEQ an apology.

But sadly I'm almost positive they will conjure some excuse why they did not "well we've reported it so many times before and so we decided not to report these cause they don't do anything about it...except when an enemies battle is last..."

And we have had multiple people locking too, not once did we come down with a quad attack.

LOL
Isn't that what FA and all the other add-on corps did by joining DNS?
The amount of irony in this thread is incredible; exploiters calling out exploiters, cowards calling out cowards, etc, etc.
I am sure DNS corps will now quad-lock "so CCP will fix it".

I'm sorry but outright cheating to make a match not count is never justified no matter how much you may hate your enemy. Use the tools in the game (no multi-attack exploiting isn't a tool) to accomplish your goals.

I'm sure CCP will make the right choices in dealing with the situation.

I doubt you are sorry.

Multi-attack...

Kain... the issue here is a Multi-Defense.

KEQ was attacked, and we played the matches.

In the past we locked our districts just as most corps in PC did.

We attacked and we defended, using clones and clone packs.

When multiple locks occur, you LOSE 36 million isk per lock.

This "quad-lock" that is the shining gem of the FA accusations have absolutely NOTHING to do with Fatal Absolution and Eternal Beings attacking KEQ at the same instance.

That "quad-lock" cost us 108 million isk under the normal amount that a single lock would profit.

Now "tri-locks" or "dual-locks" cost KEQ dearly as well.

But that was months ago, and... it has nothing to do with FA and EB attacking KEQ at the same instance.

Nothing.

It is slanderous, and desperate. Plain and simple.

We were attacked, and we fought the battles.

We did not ACTIVELY exploit or glitch.

We played the games on the schedule.

Also, wtf is up with all the crying? Multiple threads? Really?

Seriously, you have most of the top 10% of the leader-board in your alliance... just attack us in a few days maybe?

This ONE TIME glitch that KEQ DID NOT DO... does nothing to stop your plans.

Two day delay... but you all choose to jump on here and act like spoiled brats in a multi-corp, multi-thread tantrum.

Only a few districts left... look how desperate...

---

Honestly, I think this has less to do with the glitch and more to do with the fact that my warchief told the FA directors NO.