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.

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.

Actually, Wolfica made a thread complaining about the specific incident before we had a talk with your officers. We had our chat, your officers were disrespectful and rude and refused to solve the issue in a fair way. After that we did a bit of digging for evidence on the matter and found the gold mine that shows not only that you have exploited this glitch, but have been doing it for months flagrantly. We then unleashed the kraken.

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.

I didn't report anything about the first one because before I could the next morning I was contacted my a GM saying I would be refunded for both of the packs.

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.

This is incorrect. I was, as previously stated contacted the next day, I can grab a pic of the communication if you'd like proof.


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.

So you relocked a district that had an attack on it when they had rescheduled it once already. :/

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.

This is incorrect. I was given a message that both clone packs would be refunded, and both were later, because it was not the first attack scheduled.

the battle that was first in the que, and thus should have been the only one to occur, was the 2nd battle to happen that night for us. That battle we did indeed win while losing 34 clones in the process. The district remained 'under attack' in the same manner as last night and the clones lost were not reflected on the star map.

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.

This is incorrect. Because our battle was the first to be scheduled, it was allowed to go through, according to the GM. We won that battle but due to you locking it again after first 'losing' the locking war by coming in AFTER our battle, the battle you later scheduled should have been nullified as well.

Proof that this was the intention is documented in the ticket I filed. He reduced the district by the amount of clones lost (around 130) and nullified the results of your battle later. However he didn't understand that I was unable to send a reup after the win BECAUSE of your later attacks.

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 this portion has nothing to do with my post because it was on a separate unrelated district? Awesome sauce.

Let's focus on the 2 districts being referenced bud.

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?

So let me get this straight... You lost 100 mllion isk every few days and you didn't find a better way to do it?
I don't believe it for a second. You could have just set your corp wallet to 37 million isk and it would only register one attack.

What you are saying is disconnected from the frequency of occurrence in the evidence. Even if you weren't smart enough to figure out to set your corp wallet like that, you would at the very least figure to only have one guy locking it... Losing nearly a weeks worth of clone generation ISK surely isn't worth that.

Not buying it.

No it is not. Take another look at the "evidence". We were smart enough to figure out if multiple guys lock it increases our chances of locking rather than getting sniped. When you have to lock multiple districts on the same timer, setting the wallet to 37 million isk is not an option.

And we did not lose 100 million isk every few days, as the glitch occurs randomly.

Are you sure you are looking at all of the notifications?

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.

Lmao these guys are printing isk like nobodies business and at the same time having a hissy fit over locking. Holy **** you guys are a joke.

I would like to apologize for any insult intentional or not I may have given...on condition that proof is offered that pre locking fix if you were able to double, triple, or quad lock...that you lost isk on the district for the other clone packs.

I hadn't considered this and despite having my own thoughts about how you could have evaded this...I'm open to being wrong (as always) and owe you an apology for assuming if you're able to prove it.

Actually, Wolfica made a thread complaining about the specific incident before we had a talk with your officers. We had our chat, your officers were disrespectful and rude and refused to solve the issue in a fair way. After that we did a bit of digging for evidence on the matter and found the gold mine that shows not only that you have exploited this glitch, but have been doing it for months flagrantly. We then unleashed the kraken.

Less than a 1/3 now?

Our accounts on this jibe- I'll apologize for being incendiary about the situation. It rustled my jimmies that you leaped to accusations of cheating and selective petitioning without the whole scenario, especially after the work I put in that day to try to get things fixed before the battles happened. A scenario, mind, that I didn't intend to have a gigantic public discussion over before today since it entailed a game-breaking bug. It's incredible to me that Kane wouldn't let this situation be handled properly by the GM's and instead decided to attempt to make it some political pissing match.

If anyone is to blame for the **** storm, it is me. I tried to get everything resolved as privately as possible, but got told off by KEQ directors. I then said "**** it, if they don't want to make this right privately, we are going to do it publicly", and urged everyone involved on. Maybe not the right way to go about it, but I am still pretty sure you guys were doing this intentionally.

If anyone is to blame for the **** storm, it is me. I tried to get everything resolved as privately as possible, but got told off by KEQ directors. I then said "**** it, if they don't want to make this right privately, we are going to do it publicly", and urged everyone involved on. Maybe not the right way to go about it, but I am still pretty sure you guys were doing this intentionally.

Sorry but I find this very entertaining that despite the fact that KEQ had nothing to do with the bug that occurred when Eternal Beings attacked us that there is such a tantrum going on within multiple threads. I am sure no one would rebuke the fact that we would have gladly re-fought you win or lose as KEQ does not walk away from a fight.
Rather than spending all this effort in QQ, present evidence this or evidence that. Just simply re attack us and try and take the district. You may get it although on the other hand you may not. You all seek PC battles so badly yet you complain when a bug happens that isn't in your favor. KEQ as many of the officers have stated had nothing to do with this crap.
I'm sorry I may be a newer member to the corp, but I know these guys fairly well from being in Molon for over six months and yeah guess who many of us will believe. They right out said in this post what occurred step by step nearly.

So end the damn bickering it's a video game for Christ sake. Remember it's a video game where you are suppose to have FUN! Happy hunting everyone :)

Our accounts on this jibe- I'll apologize for being incendiary about the situation. It rustled my jimmies that you leaped to accusations of cheating and selective petitioning without the whole scenario, especially after the work I put in that day to try to get things fixed before the battles happened. A scenario, mind, that I didn't intend to have a gigantic public discussion over before today since it entailed a game-breaking bug. It's incredible to me that Kane wouldn't let this situation be handled properly by the GM's and instead decided to attempt to make it some political pissing match.

What the French are a problem. PC isn't broken yet, teach everyone a PC breaking bug... that ought to do it.

Viola!!! PC 2.0!!!

Everything else is mere redirection , and propaganda...

The Art of Distraction...

FA was prolly legit about their feelings, so collusion is not likely as a whole.

However, how the ideas were introduced and handled is quite evident.

Golden opportunities and all that...

Perhaps I give to much credit to off-the-cuff stratagem...

Facts could not really be twisted without the assistance of the Notifications... however full review of those lead to a self evident conclusion that does not line up with the accusations.

Deluded eyes may see only what they wish, thus only those outside parties may see facts with true clarity....

Let this be a lesson, for anyone who decides to glitch in the future. CCP does NOT take any **** when it comes to intentionally exploiting things and violating the EULA.

They will drop the ban hammer on you instantly and if they don't they will go through the logs and give us the attack as well as strip all the isk you made using the exploit until you are broke or worse, in the hole. CCP does not give a crap!

Anyone who plays Eve will tell you they make examples out of such people. Stop with your crappy attitudes and lose with some honor.

I actually think it's quite funny that EB lost the district due to a double attack in one day (lots of credit to the KEQ team also, you won the matches fair and square). Yet you don't see any EB people here calling KEQ out. Seems like DNS is ran by a bunch of immature children. Just launch another attack DNS with your unlimited supply of ISK! I mean realistically you could attack that district millions of times over and still make ISK.

Play this 'war game' the way it's meant to be played. At this point you all just look like sobbing children.

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.

It's not that, but you have to do it on purpose and its cheating per ccp and EULA. You win or lose, you dont cheat.

Since everyone's here lets hold hands =ƒÖê=ƒÖë=ƒÖè