DUST Search - Any KEQ officers around? Hoping to get something adressed.

All Channels

The War Room

Any KEQ officers around? Hoping to get something adressed.

» Click here to find additional results for this topic using Google

Monitor this thread via RSS [?]

Pages: 1 2 3 4 5 :: [one page]

Author	Thread Statistics \| Show CCP posts - 0 post(s)
Fiddlestaxp TeamPlayers Dirt Nap Squad. 778	Posted - 2014.04.16 03:16:00 - [1] - Quote If you could please contact me in game on the character "Fiddlestax Atruin", we can have a nice polite chat.
21yrOld Knight Pradox XVI 735	Posted - 2014.04.16 03:21:00 - [2] - Quote Fiddlestaxp wrote: If you could please contact me in game on the character "Fiddlestax Atruin", we can have a nice polite chat. You're fun to talk to in local. Sure your trying to kill me, but it is still fun. Mike Ruan Said I was Dust Famous DNS first to use game theory. Neo-Realism. Prisoner dilemma look it up b4 you meta
Fiddlestaxp TeamPlayers Dirt Nap Squad. 778	Posted - 2014.04.16 03:26:00 - [3] - Quote After talking with KEQ officers, they seem to be fine with the glitching that their corp is participating in. CCP has been notified of the situation and we await justice.
Fiddlestaxp TeamPlayers Dirt Nap Squad. 778	Posted - 2014.04.16 03:28:00 - [4] - Quote This isn't the first time they have used this glitch to avoid certain defeat and it likely wont be the last.
21yrOld Knight Pradox XVI 735	Posted - 2014.04.16 03:30:00 - [5] - Quote Fiddlestaxp wrote: After talking with KEQ officers, they seem to be fine with the glitching that their corp is participating in. CCP has been notified of the situation and we await justice. Do you mind telling me, what did they do? Mike Ruan Said I was Dust Famous DNS first to use game theory. Neo-Realism. Prisoner dilemma look it up b4 you meta
yep derrith again Shining Flame Amarr Empire 97	Posted - 2014.04.16 03:31:00 - [6] - Quote 21yrOld Knight wrote: Fiddlestaxp wrote: After talking with KEQ officers, they seem to be fine with the glitching that their corp is participating in. CCP has been notified of the situation and we await justice. Do you mind telling me, what did they do? They listen to this and enjoy it. 'nuff said.
Free Beers Imperfects Negative-Feedback 2337	Posted - 2014.04.16 03:34:00 - [7] - Quote Fiddlestaxp wrote: After talking with KEQ officers, they seem to be fine with the glitching that their corp is participating in. CCP has been notified of the situation and we await justice. Should ban the account of the person did it. Gotta make example of KEQ kids Every mercs life ends the same way. It is only the details of how he lived and died that distinguishes one from another
21yrOld Knight Pradox XVI 735	Posted - 2014.04.16 03:35:00 - [8] - Quote I just did a OB drop against KEQ. How did they glitch there one district. Mike Ruan Said I was Dust Famous DNS first to use game theory. Neo-Realism. Prisoner dilemma look it up b4 you meta
Fiddlestaxp TeamPlayers Dirt Nap Squad. 778	Posted - 2014.04.16 03:35:00 - [9] - Quote Free Beers wrote: Fiddlestaxp wrote: After talking with KEQ officers, they seem to be fine with the glitching that their corp is participating in. CCP has been notified of the situation and we await justice. Should ban the account of the person did it. Gotta make example of KEQ kids I asked them to just let us reattack, Their response was "lifes not fair, I don't care if it is a glitch and we are exploiting it"
Free Beers Imperfects Negative-Feedback 2337	Posted - 2014.04.16 03:39:00 - [10] - Quote Fiddlestaxp wrote: Free Beers wrote: Fiddlestaxp wrote: After talking with KEQ officers, they seem to be fine with the glitching that their corp is participating in. CCP has been notified of the situation and we await justice. Should ban the account of the person did it. Gotta make example of KEQ kids I asked them to just let us reattack, Their response was "lifes not fair, I don't care if it is a glitch and we are exploiting it" yeah send that to ccp Every mercs life ends the same way. It is only the details of how he lived and died that distinguishes one from another

Fiddlestaxp TeamPlayers Dirt Nap Squad. 778	Posted - 2014.04.16 03:41:00 - [11] - Quote https://forums.dust514.com/default.aspx?g=posts&t=43611 Quote: General corporation rules: -Push forward and be aggressive -No racism, be cool to the women -No glitching, exploiting or cheating Unfortunately, they also lie in their recruitment thread.
Free Beers Imperfects Negative-Feedback 2337	Posted - 2014.04.16 03:44:00 - [12] - Quote Fiddlestaxp wrote: https://forums.dust514.com/default.aspx?g=posts&t=43611 Quote: General corporation rules: -Push forward and be aggressive -No racism, be cool to the women -No glitching, exploiting or cheating Unfortunately, they also lie in their recruitment thread. It's also in the EULA Every mercs life ends the same way. It is only the details of how he lived and died that distinguishes one from another
Kain Spero Escrow Removal and Acquisition Dirt Nap Squad. 3328	Posted - 2014.04.16 03:55:00 - [13] - Quote Pretty dumb move on the KEQ leadership's part. Sad hear it sounds like they have been systematically using this for a long time. It's a good thing that CCP can easily go through KEQ's defense notifications and see what they have been up to. Owner of Spero Escrow Services Follow @KainSpero for Dust and CPM news
Dust User KILL-EM-QUICK RISE of LEGION 192	Posted - 2014.04.16 03:57:00 - [14] - Quote KEQ does not negotiate with terrorists.
KenKaniff69 Fatal Absolution 2337	Posted - 2014.04.16 03:59:00 - [15] - Quote Kain Spero wrote: Pretty dumb move on the KEQ leadership's part. Sad hear it sounds like they have been systematically using this for a long time. It's a good thing that CCP can easily go through KEQ's defense notifications and see what they have been up to. Herro. Would you care to look at what I found beside the road? I forwarded it to you. The problem with tanks
Kain Spero Escrow Removal and Acquisition Dirt Nap Squad. 3328	Posted - 2014.04.16 04:08:00 - [16] - Quote A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:20:00 ATTACKING CORPORATION: FATAL ABSOLUTION *********************************** A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:50:00 ATTACKING CORPORATION: ETERNAL BEINGS Owner of Spero Escrow Services Follow @KainSpero for Dust and CPM news
VALCORE72 NECROM0NGERS Caps and Mercs 138	Posted - 2014.04.16 04:10:00 - [17] - Quote but if keq is delt with ,what about the 4 months of district locking that went on ? nothing was done to anyone .
Fiddlestaxp TeamPlayers Dirt Nap Squad. 779	Posted - 2014.04.16 04:11:00 - [18] - Quote Kain Spero wrote: A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:20:00 ATTACKING CORPORATION: FATAL ABSOLUTION *********************************** A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:50:00 ATTACKING CORPORATION: ETERNAL BEINGS This isn't the only time this has happened, it has been happening for months with their attacks. They did 2-3 attacks for nearly every district when clone packs were glitched and refunding... Combined with the "second battle exploit", they may have been generating up to 100million isk per battle. Cheaters that should be banned.
Kain Spero Escrow Removal and Acquisition Dirt Nap Squad. 3328	Posted - 2014.04.16 04:12:00 - [19] - Quote Here's a real gem where they self-attacked 4 times. As you can see KEQ leadership has been systematically exploiting for months: A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:50:00 Attacking corporation: jobless bums with neckbeards ******* A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:10:00 Attacking corporation: jobless bums with neckbeards ********* A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:50:00 Attacking corporation: jobless bums with neckbeards ********* A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:40:00 Attacking corporation: jobless bums with neckbeards Owner of Spero Escrow Services Follow @KainSpero for Dust and CPM news
Tallen Ellecon KILL-EM-QUICK RISE of LEGION 1680	Posted - 2014.04.16 04:13:00 - [20] - Quote Kain Spero wrote: A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:20:00 ATTACKING CORPORATION: FATAL ABSOLUTION *********************************** A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:50:00 ATTACKING CORPORATION: ETERNAL BEINGS KEQ would like an apology. We do not know how this constitutes glitching by us. Please remove the slander from our recruitment thread. Supporter of tiericide, EVE interaction, and a proper NPE SoonGäó514 "No blue tags make Tallen go crazy.

Fiddlestaxp TeamPlayers Dirt Nap Squad. 779	Posted - 2014.04.16 04:16:00 - [21] - Quote Tallen Ellecon wrote: Kain Spero wrote: A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:20:00 ATTACKING CORPORATION: FATAL ABSOLUTION ********************************* A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:50:00 ATTACKING CORPORATION: ETERNAL BEINGS KEQ would like an apology. We do not know how this constitutes glitching by us. Please remove the slander from our recruitment thread. Kain Spero wrote: Here's a real gem where they self-attacked 4 times. As you can see KEQ leadership has been systematically exploiting for months: A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:50:00 Attacking corporation: jobless bums with neckbeards ***** A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:10:00 Attacking corporation: jobless bums with neckbeards ********* A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:50:00 Attacking corporation: jobless bums with neckbeards ********* A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:40:00 Attacking corporation: jobless bums with neckbeards Combine Clone pack refund glitch and second battle glitch and you made over 100 million isk a day doing this. Cheaters.
VALCORE72 NECROM0NGERS Caps and Mercs 139	Posted - 2014.04.16 04:18:00 - [22] - Quote are they attacking them self ? didnt saber say you still could but would't get any isk from it ? if they have the isk guess the could keep it locked down for a while .
Free Beers Imperfects Negative-Feedback 2338	Posted - 2014.04.16 04:19:00 - [23] - Quote Tallen Ellecon wrote: Kain Spero wrote: A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:20:00 ATTACKING CORPORATION: FATAL ABSOLUTION ********************************* A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:50:00 ATTACKING CORPORATION: ETERNAL BEINGS KEQ would like an apology. We do not know how this constitutes glitching by us. Please remove the slander from our recruitment thread. Sure thing. Dear trashy no skill wannabe zerg corp. I regret to inform you that your PCland bus pass has been revoked. Please enjoy pubs where your players belong. Sincerely, * Every mercs life ends the same way. It is only the details of how he lived and died that distinguishes one from another
Kain Spero Escrow Removal and Acquisition Dirt Nap Squad. 3329	Posted - 2014.04.16 04:22:00 - [24] - Quote Tallen Ellecon wrote: Kain Spero wrote: A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:20:00 ATTACKING CORPORATION: FATAL ABSOLUTION *********************************** A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:50:00 ATTACKING CORPORATION: ETERNAL BEINGS KEQ would like an apology. We do not know how this constitutes glitching by us. Please remove the slander from our recruitment thread. You should remove yourself from Dust and biomass your characters in shame. Owner of Spero Escrow Services Follow @KainSpero for Dust and CPM news
Free Beers Imperfects Negative-Feedback 2338	Posted - 2014.04.16 04:22:00 - [25] - Quote VALCORE72 wrote: are they attacking them self ? didnt saber say you still could but would't get any isk from it ? if they have the isk guess the could keep it locked down for a while . 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. Every mercs life ends the same way. It is only the details of how he lived and died that distinguishes one from another
Kain Spero Escrow Removal and Acquisition Dirt Nap Squad. 3329	Posted - 2014.04.16 04:23:00 - [26] - Quote VALCORE72 wrote: are they attacking them self ? didnt saber say you still could but would't get any isk from it ? if they have the isk guess the could keep it locked down for a while . Problem is they were using this exploit before the fix to clone pack refunds. I wouldn't be surprised if KEQ was actually the richest corp in the game. Owner of Spero Escrow Services Follow @KainSpero for Dust and CPM news
THUNDERGROOVE Fatal Absolution Dirt Nap Squad. 667	Posted - 2014.04.16 04:24:00 - [27] - Quote VALCORE72 wrote: but if keq is delt with ,what about the 4 months of district locking that went on ? nothing was done to anyone . District locking isn't an exploit. It's bad mechanics. Multiple attacks at once is an actual bug and not flawed design. There is a huge difference here. Running at 10.6 m/s ak.0 Projects: TDBS \| SDETool Flaylocks are fine
Fiddlestaxp TeamPlayers Dirt Nap Squad. 779	Posted - 2014.04.16 04:24:00 - [28] - Quote Lets get something straight. They used this exploit for MONTHS when it was possible to create 100 million isk per battle by doing this. This is some high level exploiing here, they used one exploit that refunded clone packs, another that created a second battle to reap bio mass rewards, and a third to duplicate this process. I will not retract my statements, I may furthermore investigate the extent of Eternal Beings knowledge of these actions. EB and KEQ have been trading that district back and forth for weeks now... Surely KEQ is a stronger corp than EB, This is just another form of locking, it is just a locking corp that also happens to be a real corp.
Fiddlestaxp TeamPlayers Dirt Nap Squad. 779	Posted - 2014.04.16 04:26:00 - [29] - Quote Kane, zat wants to talk to you on comms
Timbo101 KILL-EM-QUICK RISE of LEGION 196	Posted - 2014.04.16 04:29:00 - [30] - Quote Fiddlestaxp wrote: Lets get something straight. They used this exploit for MONTHS when it was possible to create 100 million isk per battle by doing this. This is some high level exploiing here, they used one exploit that refunded clone packs, another that created a second battle to reap bio mass rewards, and a third to duplicate this process. I will not retract my statements, I may furthermore investigate the extent of Eternal Beings knowledge of these actions. EB and KEQ have been trading that district back and forth for weeks now... Surely KEQ is a stronger corp than EB, This is just another form of locking, it is just a locking corp that also happens to be a real corp. .

Fiddlestaxp TeamPlayers Dirt Nap Squad. 779	Posted - 2014.04.16 04:29:00 - [31] - Quote A district belonging to your corporation has been attacked: District: Bosena IX - District 1 Time of battle: 2014.03.02 01:10:00 Attacking corporation: jobless bums with neckbeards A district belonging to your corporation has been attacked: District: Bosena IX - District 1 Time of battle: 2014.03.02 01:00:00 Attacking corporation: Hellstorm Inc
Fiddlestaxp TeamPlayers Dirt Nap Squad. 779	Posted - 2014.04.16 04:39:00 - [32] - Quote Tried having a friendly talk. Got told that "Life isn't fair" and that it "sounded like a glitch" No more friendly talks. **** List
Ghost Kaisar Fatal Absolution Dirt Nap Squad. 4238	Posted - 2014.04.16 04:48:00 - [33] - Quote Fiddlestaxp wrote: Kane, zat wants to talk to you on comms That was me...... I do sound a lot like Zatara though! I got my cloak and daggers, I'm a very happy Ghost I hack at Mach V
Fiddlestaxp TeamPlayers Dirt Nap Squad. 781	Posted - 2014.04.16 04:52:00 - [34] - Quote Ghost Kaisar wrote: Fiddlestaxp wrote: Kane, zat wants to talk to you on comms That was me...... I do sound a lot like Zatara though! My mistake. Any more KEQ officers here to deny complicacy or evidence?
Ghost Kaisar Fatal Absolution Dirt Nap Squad. 4238	Posted - 2014.04.16 04:53:00 - [35] - Quote Fiddlestaxp wrote: Ghost Kaisar wrote: Fiddlestaxp wrote: Kane, zat wants to talk to you on comms That was me...... I do sound a lot like Zatara though! My mistake. Any more KEQ officers here to deny complicacy or evidence? No problem. It's actually become a running gag in FA I got my cloak and daggers, I'm a very happy Ghost I hack at Mach V
CUSE TOWN333 KILL-EM-QUICK RISE of LEGION 340	Posted - 2014.04.16 05:01:00 - [36] - Quote 21yrOld Knight wrote: I just did a OB drop against KEQ. How did they glitch there one district. There a little confused and to dumb to figure out what happened The clever combatant imposes his will on the enemy, but does not allow the enemy"s will to be imposed upon him. Sun Tzu
Fiddlestaxp TeamPlayers Dirt Nap Squad. 782	Posted - 2014.04.16 05:04:00 - [37] - Quote CUSE TOWN333 wrote: 21yrOld Knight wrote: I just did a OB drop against KEQ. How did they glitch there one district. There a little confused and to dumb to figure out what happened A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:50:00 Attacking corporation: jobless bums with neckbeards ******* A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:10:00 Attacking corporation: jobless bums with neckbeards ********* A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:50:00 Attacking corporation: jobless bums with neckbeards ********* A district belonging to your corporation has been attacked: District: Altbrard VI - District 14 Time of battle: 2014.02.28 04:40:00 Attacking corporation: jobless bums with neckbeards Using exploits to generate massive amounts of isk. Not confused about what you were doing at all.
Gildart Lightray Eternal Beings Proficiency V. 132	Posted - 2014.04.16 06:10:00 - [38] - Quote Fiddlestaxp wrote: Lets get something straight. They used this exploit for MONTHS when it was possible to create 100 million isk per battle by doing this. This is some high level exploiing here, they used one exploit that refunded clone packs, another that created a second battle to reap bio mass rewards, and a third to duplicate this process. I will not retract my statements, I may furthermore investigate the extent of Eternal Beings knowledge of these actions. EB and KEQ have been trading that district back and forth for weeks now... Surely KEQ is a stronger corp than EB, This is just another form of locking, it is just a locking corp that also happens to be a real corp. Dude we beat them fare and square the first time we took the district back from them. We have pictures of all PC battles we've had with them. Last 3 battles we lost. Actually 4 because once we got the district from them we got two attack mails. Close matches but I'll just make this simple. EB was not part of whatever glitch they used. Need to find me? I'll be in "Gildarts Cave"
Fiddlestaxp TeamPlayers Dirt Nap Squad. 784	Posted - 2014.04.16 06:46:00 - [39] - Quote Gildart Lightray wrote: Fiddlestaxp wrote: Lets get something straight. They used this exploit for MONTHS when it was possible to create 100 million isk per battle by doing this. This is some high level exploiing here, they used one exploit that refunded clone packs, another that created a second battle to reap bio mass rewards, and a third to duplicate this process. I will not retract my statements, I may furthermore investigate the extent of Eternal Beings knowledge of these actions. EB and KEQ have been trading that district back and forth for weeks now... Surely KEQ is a stronger corp than EB, This is just another form of locking, it is just a locking corp that also happens to be a real corp. Dude we beat them fare and square the first time we took the district back from them. We have pictures of all PC battles we've had with them. Last 3 battles we lost. Actually 4 because once we got the district from them we got two attack mails. Close matches but I'll just make this simple. EB was not part of whatever glitch they used. Fair enough, sorry to drag you into this. The evidence stands without your involvement and the evidence doesn't necessitate any accusation towards you.
CRUSADER2134 Ancient Exiles. Dirt Nap Squad. 46	Posted - 2014.04.16 07:03:00 - [40] - Quote 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. EVE Character MP2008

Fire2MyBlunt The Phoenix Federation Caps and Mercs 186	Posted - 2014.04.16 07:12:00 - [41] - Quote Thought self locking was allowed just at the cost of your risk. Do they just keep successfully sniping it from you that your mad & won't get 100%? I'm confused.... you guys are something else ... Proud member and Director of The Phoenix Federation I don't go by chubby.. They call me the Hulk around here.
weccer Kameira Lodge Amarr Empire 78	Posted - 2014.04.16 07:14:00 - [42] - Quote So wait...because of a glitch that was exploited the corp has to pay. Idk, sounds like everybody forgot what happens in this game all to often. Nobody cried like a lil ***** when them other corps were exploiting. Idk, sounds like a boohoo moment on DNS's part. Lol why don't we continue this thread and let ccp know of all the other corps who've been exploiting certain glitches.
CRUSADER2134 Ancient Exiles. Dirt Nap Squad. 46	Posted - 2014.04.16 07:14:00 - [43] - Quote Fire2MyBlunt wrote: Thought self locking was allowed just at the cost of your risk. Do they just keep successfully sniping it from you that your mad & won't get 100%? I'm confused.... you guys are something else ... No, they are quadruple attacking it and using a glitch to prevent the re-attack we rightfully won. The quadruple stack is being used to generate isk in an illegal way. EVE Character MP2008
Fire2MyBlunt The Phoenix Federation Caps and Mercs 186	Posted - 2014.04.16 07:24:00 - [44] - Quote CRUSADER2134 wrote: Fire2MyBlunt wrote: Thought self locking was allowed just at the cost of your risk. Do they just keep successfully sniping it from you that your mad & won't get 100%? I'm confused.... you guys are something else ... No, they are quadruple attacking it and using a glitch to prevent the re-attack we rightfully won. The quadruple stack is being used to generate isk in an illegal way. If that's the case then all you mother ***** be banned for district locking in the past . Not only KEQ. I know a lot of you corps did the same ** so let's pull up the logs from way back to see who else did it . :) that'll be fun.. Proud member and Director of The Phoenix Federation I don't go by chubby.. They call me the Hulk around here.
Smoky Fingers Red Star. EoN. 338	Posted - 2014.04.16 07:45:00 - [45] - Quote True rulers of MH #KEQtrillionaires Flight stick user. Oh well :(
cody-p KILL-EM-QUICK RISE of LEGION 25	Posted - 2014.04.16 07:54:00 - [46] - Quote Kain Spero wrote: VALCORE72 wrote: are they attacking them self ? didnt saber say you still could but would't get any isk from it ? if they have the isk guess the could keep it locked down for a while . Problem is they were using this exploit before the fix to clone pack refunds. I wouldn't be surprised if KEQ was actually the richest corp in the game. lmfao....!!!
superjoe360x D.A.R.K L.E.G.I.O.N D.E.F.I.A.N.C.E 228	Posted - 2014.04.16 08:33:00 - [47] - Quote Kain Spero wrote: Tallen Ellecon wrote: Kain Spero wrote: A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:20:00 ATTACKING CORPORATION: FATAL ABSOLUTION ********************************* A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:50:00 ATTACKING CORPORATION: ETERNAL BEINGS KEQ would like an apology. We do not know how this constitutes glitching by us. Please remove the slander from our recruitment thread. You should remove yourself from Dust and biomass your characters in shame. Same goes for all you highly skilled lets blue up nobody has any respect for you DNS loser. Commander, Director of DL and Leader of The SS Elite Squad** *Putting Dust players out of their misery since Jan 2013
smartlayer What The French Red Whines. 99	Posted - 2014.04.16 09:19:00 - [48] - Quote Kain Spero wrote: Tallen Ellecon wrote: Kain Spero wrote: A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:20:00 ATTACKING CORPORATION: FATAL ABSOLUTION *********************************** A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:50:00 ATTACKING CORPORATION: ETERNAL BEINGS KEQ would like an apology. We do not know how this constitutes glitching by us. Please remove the slander from our recruitment thread. You should remove yourself from Dust and biomass your characters in shame. You are very active suddenly to defend your pets, you dont have enought districts ? I dont support exploit but i dont support insider trading or influence peddling then you should too remove yourself from dust and biomass your character (and his wallet to or it would be cheating (again))
smartlayer What The French Red Whines. 99	Posted - 2014.04.16 09:21:00 - [49] - Quote Kain Spero wrote: VALCORE72 wrote: are they attacking them self ? didnt saber say you still could but would't get any isk from it ? if they have the isk guess the could keep it locked down for a while . Problem is they were using this exploit before the fix to clone pack refunds. I wouldn't be surprised if KEQ was actually the richest corp in the game. You are taking the Dust community for retards ?
Flyingconejo KILL-EM-QUICK RISE of LEGION 759	Posted - 2014.04.16 11:44:00 - [50] - Quote There is no rage like a nerd's rage. Just submit your support ticket, and CCP will probably revert the situation back to us under attack from FA with 70 clones left. @To Fiddlestap, Kane, Free Beers, rest of DNS groupies. This is a bug, no intentional glitching. Claiming that we have been abusing this bug for profit for months is obviously false. If it was intentional glitching, you wouldn't have to go back to February to get another instance of multiple attacks, would you? There should be a really long list, but wait, there isn't! This bug has happened to us just one or two times, both attacking and defending, as I'm sure it has happened to other corps, and we actually have reported the bug before, so CCP knows about it. However, you don't have to worry. If we have been "glitching for months" "amassing billions of isk", I'm sure CCP will ban all of us in a couple of days. But since we have not, I would suggest you all to get a chair if you are waiting for our ban, and stop behaving like spurned girlfriends. EDIT: I think I have seen more activity from Kane in this thread that in a month of him as CPM. Nice attempt at slander.

21yrOld Knight Pradox XVI 736	Posted - 2014.04.16 12:07:00 - [51] - Quote This is hilarious. I am happy that I didn't tell any one what really happened last night. wow. Mike Ruan Said I was Dust Famous DNS first to use game theory. Neo-Realism. Prisoner dilemma look it up b4 you meta
CUSE TOWN333 KILL-EM-QUICK RISE of LEGION 345	Posted - 2014.04.16 12:18:00 - [52] - Quote 21yrOld Knight wrote: This is hilarious. I am happy that I didn't tell any one what really happened last night. wow. i eat 4 bags of popcorn lastnight rolling on the ground laughing at the nerd rage i haven't seen this much QQ in forever. The clever combatant imposes his will on the enemy, but does not allow the enemy"s will to be imposed upon him. Sun Tzu
Timbo101 KILL-EM-QUICK RISE of LEGION 201	Posted - 2014.04.16 12:33:00 - [53] - Quote CUSE TOWN333 wrote: 21yrOld Knight wrote: This is hilarious. I am happy that I didn't tell any one what really happened last night. wow. i eat 4 bags of popcorn lastnight rolling on the ground laughing at the nerd rage i haven't seen this much QQ in forever. I had a majestic orgasm last night, unrelated but I thought you should know cuse
VIRDJINN Rampage Diaper Rash. 86	Posted - 2014.04.16 12:37:00 - [54] - Quote Congrats KEQQ, you're now on my list, right next to AE glitching trash. Mark my words, you will NEVER live this down, and everyone in KEQQ will be forever known as glitching trash. Enjoy. I failed English as a 2nd Language and wear a seatbelt on the shortbus. don't laugh.. I only have 1 eye
kiarbanor S.e.V.e.N. General Tso's Alliance 379	Posted - 2014.04.16 12:39:00 - [55] - Quote THUNDERGROOVE wrote: VALCORE72 wrote: but if keq is delt with ,what about the 4 months of district locking that went on ? nothing was done to anyone . District locking isn't an exploit. It's bad mechanics. Multiple attacks at once is an actual bug and not flawed design. There is a huge difference here. I'm still trying to figure out the difference between bad mechanics and a bug. Aren't they both something that gamers take advantage of in order to gain something? So was equipment spamming in order to lag out the other team bad mechanics or a bug? Melee glitch? District locking? How about the hacking, switching to weapon, then being able to kill while cloaked? What about emulators so that kb/m can get auto aim? There are a million more. To me there is no difference because it doesn't matter. People will abuse whatever possible in this game in order to gain "something." If you want serious repercussions for one, you want serious repercussions for all. Happy Gaming!!!
LionTurtle91 KILL-EM-QUICK RISE of LEGION 138	Posted - 2014.04.16 12:47:00 - [56] - Quote Timbo101 wrote: CUSE TOWN333 wrote: 21yrOld Knight wrote: This is hilarious. I am happy that I didn't tell any one what really happened last night. wow. i eat 4 bags of popcorn lastnight rolling on the ground laughing at the nerd rage i haven't seen this much QQ in forever. I had a majestic orgasm last night, unrelated but I thought you should know cuse Was it too the Super Mario Bros theme song again? =ƒæë=ƒæî
Timbo101 KILL-EM-QUICK RISE of LEGION 203	Posted - 2014.04.16 13:08:00 - [57] - Quote LionTurtle91 wrote: Timbo101 wrote: CUSE TOWN333 wrote: 21yrOld Knight wrote: This is hilarious. I am happy that I didn't tell any one what really happened last night. wow. i eat 4 bags of popcorn lastnight rolling on the ground laughing at the nerd rage i haven't seen this much QQ in forever. I had a majestic orgasm last night, unrelated but I thought you should know cuse Was it too the Super Mario Bros theme song again? You know it, only way I can get aroused anymore
Kain Spero Escrow Removal and Acquisition Dirt Nap Squad. 3339	Posted - 2014.04.16 14:17:00 - [58] - Quote Flyingconejo wrote: There is no rage like a nerd's rage. Just submit your support ticket, and CCP will probably revert the situation back to us under attack from FA with 70 clones left. @To Fiddlestap, Kane, Free Beers, rest of DNS groupies. This is a bug, no intentional glitching. Claiming that we have been abusing this bug for profit for months is obviously false. If it was intentional glitching, you wouldn't have to go back to February to get another instance of multiple defences, would you? There should be a really long list, but wait, there isn't! This bug has happened to us just a couple of times, both attacking and defending, as I'm sure it has happened to other corps. We have actually reported the bug the times it happened, so CCP knows about it. However, you don't have to worry. If we have been "glitching for months" "amassing billions of isk", I'm sure CCP will ban all of us in a couple of days. But since we have not, I would suggest you all to get a chair if you are waiting for our ban, and stop behaving like spurned girlfriends. EDIT: I think I have seen more activity from Spero in this thread that in a month of him as CPM. The problem is knowingly using the bug to nullify attacks from another corp is an exploit is the purest sense. KEQ has been systematically using this exploit for months and it seems their members were in the dark because they seem more than happy to provide us with the Concord mails to show that this is a pattern going back to at least February if not sooner. I mean your recruiting thread says no cheaters or glitchers right? I have concord mails showing you all using the glitch every single month from February until now. I wouldn't be surprised if you pattern of abuse went back even further. It's one thing to mess up once or twice and cause the bug which requires precise timing to execute. I can even see someone running a test to see what happens. It's a whole different situation when you systematically use that bug and exploit it to prevent enemy attacks from going through. Apparently KEQ has tried to use this exploit to their advantage not only to keep their district but against corps such as Eternal Beings when KEQ goes on the offensive. Leither even reported the bug to CCP before he left KEQ and was confident that the bug had been thoroughly tested. Two weeks after Leither left though was when one of the most elaborate examples of the exploit occurred with KEQ self attacking themselves 4 times on one district reinforce. WIth the refund bug this potentially grossed them over 200 million ISK in one instance of the exploit over the course of one reinforcement. CCP can decide on the best course of action and I hope that none of your a dumb enough to continue to try and exploit the bug. If it''s bug though and unintentional then KEQ won't mind CCP reinstating FA's win and then allowing their district attack to go through as should have occurred last night when you were defeated with a clone pack attack. I'm sure you all can prove your mettle on the battlefield rather than exemplifying yourself as exploiting glitchers. Owner of Spero Escrow Services Follow @KainSpero for Dust and CPM news
ER-Bullitt Molon Labe. General Tso's Alliance 1349	Posted - 2014.04.16 14:35:00 - [59] - Quote 99% tho.. sooo close.
Flyingconejo KILL-EM-QUICK RISE of LEGION 779	Posted - 2014.04.16 14:44:00 - [60] - Quote Kain Spero wrote: The problem is knowingly using the bug to nullify attacks from another corp is an exploit is the purest sense. KEQ has been systematically using this exploit for months I'm going to stop right here, and call you out on the sistematically. That's a fine word, but it is patently false, or you would have already posted a list with our hundreds of abuses. Kain Spero wrote: I have concord mails showing you all using the glitch every single month from February until now. I wouldn't be surprised if you pattern of abuse went back even further. Every month from February until now. That's what? 2 times in 80 days? 3 times in 80 days? 2-3 times in 3 months is pretty normal for a bug to pop up. If we were exploiting that bug, I would expect to see 20-30 instances in 80 days. But you won't see that, because we did not exploit it. Kain Spero wrote: Apparently KEQ has tried to use this exploit to their advantage not only to keep their district but against corps such as Eternal Beings when KEQ goes on the offensive. Make up your mind. If multi attacking helps the defending corp because only the last attack counts, why would we, exploiting glitchers, use it to attack other districts? It would make our job twice as hard since we would have to win 2 battles for 1 to count? We would actually be helping Eternal Beings! So why would we do it? The answer is we wouldn't. It was a bug. Then as now. Kain Spero wrote: Leither even reported the bug to CCP before he left KEQ and was confident that the bug had been thoroughly tested............. one of the most elaborate examples of the exploit occurred with KEQ self attacking themselves 4 times on one district reinforce. WIth the refund bug this potentially grossed them over 200 million ISK in one instance of the exploit over the course of one reinforcement. Leither reported it. Our CEO reported it. A couple of our directors reported it. We have reported it multiple times. You are a CPM. Instead of trying to get a button to make selling districts easier, why don't you pest CCP about things like this? Also, about the four battles in the same districts, why did we do it only once, if we are exploiting glitchers ? Because we are not. Some of our districts had been sniped by a couple of corps at the time, so we had to get a group of directors at the same time to lock. Bug happened. It was reported. Kain Spero wrote: CCP can decide on the best course of action and I hope that none of KEQ are dumb enough to continue to try and exploit the bug. If it''s bug though and unintentional then KEQ won't mind CCP reinstating FA's win and then allowing their district attack to go through as should have occurred last night when you were defeated with a clone pack attack. I'm sure you all can prove your mettle on the battlefield rather than exemplifying yourself as exploiting glitchers. Not a problem with that, I'm sure CCP will revert it. If we lose it, so be it. As for proving yourself, you have certainly proved the kind of guy you are both in this and our recruitment thread. Throwing a temper tantrum and crying foul to the winds when the game bugs and doesn't go your way is not the kind of behaviour expected from a CPM.

yep derrith again Shining Flame Amarr Empire 111	Posted - 2014.04.16 14:44:00 - [61] - Quote superjoe360x wrote: Kain Spero wrote: Tallen Ellecon wrote: Kain Spero wrote: A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:20:00 ATTACKING CORPORATION: FATAL ABSOLUTION *********************************** A DISTRICT BELONGING TO YOUR CORPORATION HAS BEEN ATTACKED: DISTRICT: ODDELULF III - DISTRICT 3 TIME OF BATTLE: 2014.04.16 02:50:00 ATTACKING CORPORATION: ETERNAL BEINGS KEQ would like an apology. We do not know how this constitutes glitching by us. Please remove the slander from our recruitment thread. You should remove yourself from Dust and biomass your characters in shame. Same goes for all you highly skilled lets blue up nobody has any respect for you DNS loser. Let me tell you a quick story about what respect gets you in this world. Particularly in the sack. Respect and dignity are what rob you of a good time. You ever bent someone over and, well....... then you turn them around and spit in.......... trying to avoid any dirty movie stuff, but it seems I may be failing at that. OH, then when they ask you to get on all fours and tie a dog collar around you and a horsey saddle on your back and play old country western music......... and........ I've forgotten my point. This post officially brought to you by.
Knight Solitaire 751	Posted - 2014.04.16 14:48:00 - [62] - Quote Here's a little song I wrote, might want to sing it note for note, don't worry, be happy. In every life we have some trouble, when you worry you make it double, don't worry, be happy. Don't worry, be happy now! Take it away War Room! Faigh dea "Knight Soiaire has the best RE Game" - Crimson Moon V
Zatara Rought Fatal Absolution 2563	Posted - 2014.04.16 15:06:00 - [63] - Quote 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..." CEO of FA B3RT>PFBHz>TP>IMP>FA Follow me on twitter Skype Zatara.Rought
KenKaniff69 Fatal Absolution 2344	Posted - 2014.04.16 15:23:00 - [64] - Quote Zatara Rought wrote: 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..." 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. The problem with tanks
ER-Bullitt Molon Labe. General Tso's Alliance 1362	Posted - 2014.04.16 15:39:00 - [65] - Quote KenKaniff69 wrote: Why anyone would want to join a corporation that has thrived off of gltiching everything possible just to hold land is beyond me. If this is true, dont care either way, they are trolling you blue donut faggots hard... and its ******* AWESOME (high five amirite) That's reason enough for me. Sending in application right now.
ER-Bullitt Molon Labe. General Tso's Alliance 1362	Posted - 2014.04.16 15:45:00 - [66] - Quote P.S. 99%... close enough. LOL
21yrOld Knight Pradox XVI 748	Posted - 2014.04.16 15:46:00 - [67] - Quote KenKaniff69 wrote: Zatara Rought wrote: 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..." 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. Feel ashamed of what? That they dodge the power of DNS This isn't the real world trying to use hegemony won't work. Mike Ruan Said I was Dust Famous DNS first to use game theory. Neo-Realism. Prisoner dilemma look it up b4 you meta
Flyingconejo KILL-EM-QUICK RISE of LEGION 793	Posted - 2014.04.16 16:17:00 - [68] - Quote Zatara Rought wrote: ............really long post........ Amazing, I didn't see Spero's mouth move even once! Nice trick! How the mighty have fallen! Just kidding, just kidding. I can tell you that I know I did not send a support ticket. Since CCP stopped their support service in Spanish, I stopped reporting bugs. They don't support me, I don't support them. I also know that KEQ has sent support tickets in every other instance of this bug happening, even when it would have benefitted us not to do so. I also know that in some cases, even with KEQ sending a support ticket before the battle, CCP has been too slow/ has not wanted to remove the extra battles. The last time was when we had 2 battles in the same district against Eternal Beings. I guess that CCP has made some cuts on the Support personnel, but since there is no support in Spanish, I could not care less. I was not around for yesterday battles so I don't know for sure if we send a ticket or not for this one, but it would surprise me that we didn't since we have done before every time. I would ask around and find it for you, but lets be honest, you guys really don't care about what really happened, since you have a pretty nice story already mounted in which you are tragic heroes and all that crap. Far from me to burst that bubble. CCP will surely revert the district to the state it was after the first attack, with you reattacking against 70 clones. I know it must be boring in DNS, but all that drama about "glitchers", "exploiters", and "systematically quad locking and making billions" is just the tinfoil party screaming while mounted on the slander train. And with this, I'm off. I dislike Dust, I dislike its forums, and I particularly dislike the War Room, and you trolls have kept me here too much already. See you in a while. o7
Moorian Flav 165	Posted - 2014.04.16 16:23:00 - [69] - Quote Quote: 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". I don't troll; I tell the truth.
yep derrith again Shining Flame Amarr Empire 112	Posted - 2014.04.16 16:28:00 - [70] - Quote Moorian Flav wrote: Quote: 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". Probably, but I rest easier knowing that my pillow is not made of duck feathers, but instead, cold hard isk. Besides, you can chastise FA all you like, but sometimes to dispense justice, you have to do unjust things.

Moorian Flav 167	Posted - 2014.04.16 16:31:00 - [71] - Quote Quote: 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). I don't troll; I tell the truth.
yep derrith again Shining Flame Amarr Empire 113	Posted - 2014.04.16 16:38:00 - [72] - Quote Moorian Flav wrote: Quote: 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). You mistake me for condemning them. Besides, I've grown to the point to where I just can't care anymore, I've heard every story and opinion in the book, and no matter how much I try to explain my thoughts, you all are too thick skulled to consider my side, and vice versa, TBH. So I've given up, it's clear we won't see eye to eye on this. There are people who will continually dream up "facts" and stories to support their claim, and those who just don't listen. It isn't mine or your fault if we don't see things the way you or I do.
Leither Yiltron Ahrendee Mercenaries 860	Posted - 2014.04.16 17:52:00 - [73] - Quote Zatara Rought wrote: 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. 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? Have a pony
THUNDERGROOVE Fatal Absolution Dirt Nap Squad. 667	Posted - 2014.04.16 17:54:00 - [74] - Quote Moorian Flav wrote: Quote: 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". Locking is a bad game mechanic. Bypassing the 1 hour time a corp has to reattack and multiple attacks are actual bugs in the game. Understand the difference before you speak. Running at 10.6 m/s ak.0 Projects: TDBS \| SDETool ScrubzBScrubz
Timbo101 KILL-EM-QUICK RISE of LEGION 224	Posted - 2014.04.16 17:55:00 - [75] - Quote Leither Yiltron wrote: Zatara Rought wrote: 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. 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? Hi Leither! Do you still play often?
Fiddlestaxp TeamPlayers Dirt Nap Squad. 791	Posted - 2014.04.16 17:56:00 - [76] - Quote Leither Yiltron wrote: Zatara Rought wrote: 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. 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.
Kain Spero Escrow Removal and Acquisition Dirt Nap Squad. 3341	Posted - 2014.04.16 17:57:00 - [77] - Quote 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. Owner of Spero Escrow Services Follow @KainSpero for Dust and CPM news
ER-Bullitt Molon Labe. General Tso's Alliance 1379	Posted - 2014.04.16 17:58:00 - [78] - Quote Sounds a lot like... "my bad"
Timbo101 KILL-EM-QUICK RISE of LEGION 224	Posted - 2014.04.16 17:58:00 - [79] - Quote Fiddlestaxp wrote: Leither Yiltron wrote: Zatara Rought wrote: 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. 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 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.
Timbo101 KILL-EM-QUICK RISE of LEGION 229	Posted - 2014.04.16 17:59:00 - [80] - Quote Kain Spero wrote: 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. Who are you responding to Kain? I'm a little confused here, can you rephrase this maybe? Being serious too

Fiddlestaxp TeamPlayers Dirt Nap Squad. 791	Posted - 2014.04.16 18:04:00 - [81] - Quote Timbo101 wrote: Fiddlestaxp wrote: Leither Yiltron wrote: Zatara Rought wrote: 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. 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 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.
Timbo101 KILL-EM-QUICK RISE of LEGION 229	Posted - 2014.04.16 18:06:00 - [82] - Quote Fiddlestaxp wrote: Timbo101 wrote: Fiddlestaxp wrote: Leither Yiltron wrote: Zatara Rought wrote: 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. 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 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. **** happens I guess? I thought you wanted to talk about it, as soon as I posted in our pub chat you left...
ER-Bullitt Molon Labe. General Tso's Alliance 1382	Posted - 2014.04.16 18:06:00 - [83] - Quote Not their fault you didn't do it right.
Tallen Ellecon KILL-EM-QUICK RISE of LEGION 1699	Posted - 2014.04.16 18:17:00 - [84] - Quote Fiddlestaxp wrote: Timbo101 wrote: Fiddlestaxp wrote: Quad attacks don't happen on accident. 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. So how is it not an accident if you can't replicate it with multiple people yourself? How can we say "okay we're going to get 4 attacks in at no profit by doing ____"? I don't see why this is so confusing. Supporter of tiericide, EVE interaction, and a proper NPE SoonGäó514 "No blue tags make Tallen go crazy.
Erobthedude 0uter.Heaven Academy 73	Posted - 2014.04.16 19:03:00 - [85] - Quote Zatara Rought wrote: 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..." Not trolling here, but they can only take advantage of the glitch when they have won the match right? "Dear Lord, without you we are butt dust."
Scheherazade VII 408	Posted - 2014.04.16 19:11:00 - [86] - Quote Pretty funny how a CPM member who has a close relationship with CCP would come crying on the forums like this instead of you know...saying perhaps... "hey do you know if xxxxxx exploit has been reported and if so, what intends to be done about the situation as I have evidence that..." but the thing is, that would be in an instance where you actually give a damn. instead you want all the districts, anybody who wants to blue up and engulf the entire game and have ZERO battles in a game where the idea is to fight over planets really doesn't give a dam about DUST at all, only when it affects them personally. How much ISK have you made from blueing up the ENTIRE GAME and you worry about people locking ONE district? Didn't EVERYBODY lock districts? Wasn't billions if not trillions made from locking districts? But because this stands in the way of you obtaining 100% you come on the forums and cry like a little ***. I'm not even sure if I'm talking to Kain or the OP right now but you're both babies crying over one minor little thing, why are you so hellbent on taking over 100% of the game just to sell districts then demand protection money, attack the district anyway and keep pumping and dumping back and forth to gain ISK?! Wouldn't that be manipulation of the highest order? he who has the most power wins and it seems like your ass is red raw because now somebody else has the power! that should put a new stirrer in the ** pot :D i don't belong to any corp or really actively play DUST but it is fun, i guess now I'll get some uber serious post from some 17 year old kid in an elite corp about how I will be teamkilled in faction warfare. looooooooooool my facts could be untrue but who really cares :D
Dust User KILL-EM-QUICK RISE of LEGION 217	Posted - 2014.04.16 22:12:00 - [87] - Quote Fiddlestaxp wrote: Timbo101 wrote: Fiddlestaxp wrote: Quad attacks don't happen on accident. 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. If the almighty fiddle has never seen it then it must not be true. Maybe you don't know how the game works as well as you think you do? You are a disgrace to neck-beards around the world. Get over yourself.
Zatara Rought Fatal Absolution 2577	Posted - 2014.04.17 02:39:00 - [88] - Quote Moorian Flav wrote: Quote: 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". FA holds land? I think we just managed to get a few attacks in and actually aren't holding ANY land except for one odd district we just took and have no intention of keeping...tbh. CEO of FA B3RT>PFBHz>TP>IMP>FA Follow me on twitter Skype Zatara.Rought
STYLIE77 KILL-EM-QUICK RISE of LEGION 157	Posted - 2014.04.17 02:46:00 - [89] - Quote Kain Spero wrote: 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.
Stiddlefaxq Vherokior Combat Logistics Minmatar Republic 41	Posted - 2014.04.17 02:57:00 - [90] - Quote STYLIE77 wrote: Kain Spero wrote: 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. 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.

Tallen Ellecon KILL-EM-QUICK RISE of LEGION 1735	Posted - 2014.04.17 03:01:00 - [91] - Quote STYLIE77 wrote: Kain Spero wrote: 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. o7 This is why I love this corp. Supporter of tiericide, EVE interaction, and a proper NPE SoonGäó514 "No blue tags make Tallen go crazy.
Stiddlefaxq Vherokior Combat Logistics Minmatar Republic 41	Posted - 2014.04.17 03:06:00 - [92] - Quote STYLIE77 wrote: 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.
Timbo101 KILL-EM-QUICK RISE of LEGION 248	Posted - 2014.04.17 03:13:00 - [93] - Quote Stiddlefaxq wrote: STYLIE77 wrote: 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. Technically I unleashed the kraken
Zatara Rought Fatal Absolution 2577	Posted - 2014.04.17 03:14:00 - [94] - Quote Leither Yiltron wrote: 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? Less than a 1/3 now? I'll be sure to make sure i'm omniscient before I post what my perception is...and post that I could be wrong and am open to more information. If you have a ticket for the 2nd district we attacked I'd love to see some evidence of it. CEO of FA B3RT>PFBHz>TP>IMP>FA Follow me on twitter Skype Zatara.Rought
STYLIE77 KILL-EM-QUICK RISE of LEGION 162	Posted - 2014.04.17 03:15:00 - [95] - Quote Stiddlefaxq wrote: STYLIE77 wrote: Kain Spero wrote: 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. 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?
Stiddlefaxq Vherokior Combat Logistics Minmatar Republic 41	Posted - 2014.04.17 03:22:00 - [96] - Quote STYLIE77 wrote: Stiddlefaxq wrote: STYLIE77 wrote: Kain Spero wrote: 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. 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? It isn't "random" when you time it. Losing 100 million once to something that can be avoided would be enough for any rational corp. The fact that it happened more than once suggests two options, the more likely of which is that your explanation is bogus.
Emperor1349 Molon Labe. General Tso's Alliance 105	Posted - 2014.04.17 03:36:00 - [97] - Quote 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. If you have a poor gun game no proto suit can help you. If you have a good gun game no proto suit is needed.
Zatara Rought Fatal Absolution 2577	Posted - 2014.04.17 03:36:00 - [98] - Quote STYLIE77 wrote: 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. 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. CEO of FA B3RT>PFBHz>TP>IMP>FA Follow me on twitter Skype Zatara.Rought
Stiddlefaxq Vherokior Combat Logistics Minmatar Republic 41	Posted - 2014.04.17 03:40:00 - [99] - Quote Emperor1349 wrote: 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. We are printing isk legit at least
STYLIE77 KILL-EM-QUICK RISE of LEGION 163	Posted - 2014.04.17 03:43:00 - [100] - Quote Zatara Rought wrote: STYLIE77 wrote: 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. 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. I would be happy to provide a screenshot but Eve does not show the Dust wallet and even then the wallet only goes back so far. Contact Hawkin Pete from Molon Labe... his knowledge of locking mechanics is most likely greater than that of the Game Masters or that of most CEO's in Dust including Cubs. He can verify the losses incurred as I am sure he had some himself. However, the frustration of the situation is understandable. Simply ask the rest of DNS to back off and re-attack, all this KEQQ is quite unnecessary.

CUSE TOWN333 KILL-EM-QUICK RISE of LEGION 368	Posted - 2014.04.17 03:57:00 - [101] - Quote Stiddlefaxq wrote: STYLIE77 wrote: 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 found nothing at all that shows we made isk off a quad lock because its not possible to do that but nice try. all you have is a couple times the bug happened to us cause we have like 4 guys locking at once cause you have 4 guys trying to snipe. then the FA and eternal beings tryed to launch an attack on us at the same time wich bugged there attacks together wich is not are doing. so your wasting everyones time by makeing crap up wich i dont see how this helps you i mean you have all the corps not in DNS stuck trying to launch clone pacs at you now how much more of an advantage do you need to get 100%. just stop with all the QQ and play the game your meta is weak sauce trying to slander people. The clever combatant imposes his will on the enemy, but does not allow the enemy"s will to be imposed upon him. Sun Tzu
Leither Yiltron Ahrendee Mercenaries 869	Posted - 2014.04.17 04:11:00 - [102] - Quote Zatara Rought wrote: Leither Yiltron wrote: 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. I received notification at around 10am, noticed it around 12pm. At that time I was told that exactly ONE of my corp's battles were incorrectly allowed through. Whatever the case, by the time I got to my apartment at 1230 to sacrifice my day sorting it out, the described rescheduling and onlining had already happened. 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. It wasn't my intent to say that you were reporting as well, this is merely my side of the situation. You weren't part of the defending corp, so how can you possibly claim that what the GM's told you about rescheduling proves anything about what actually happened to the districts? I'm really intrigued how you know this. Should discuss this with me sometime what proof you have that lead to this statement. I don't have proof to provide. When I made it home, STB had attacked one of KEQ's districts which was newly onlined. There were two battles on it. KEQ's officers immediately moved to attack the other ones with the locking corp because we had no idea what was going on, but didn't want more attacks from STB or similar hitting the districts. So you relocked a district that had an attack on it when they had rescheduled it once already. :/ 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. I said the battles involved FA- whether or not they "should have" happened I have no idea after all the GM intervention. 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. Which is what I reported in the following paragraph. All I know is that the battle fought there was nullified. Our accounts jibe. Again, we had launched and attack on this district because it was online after GM intervention. So this portion has nothing to do with my post because it was on a separate unrelated district? Awesome sauce. Yes, because it explains the situation in full, especially in regards to how much GM intervention was going on. 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. Have a pony
m twiggz Pradox One Proficiency V. 530	Posted - 2014.04.17 04:25:00 - [103] - Quote The unnecessary amount of DNS QQ this is causing is hilarious. Keep up the good work KEQ.
Stiddlefaxq Vherokior Combat Logistics Minmatar Republic 41	Posted - 2014.04.17 04:26:00 - [104] - Quote Leither Yiltron wrote: Zatara Rought wrote: Leither Yiltron wrote: 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. I received notification at around 10am, noticed it around 12pm. At that time I was told that exactly ONE of my corp's battles were incorrectly allowed through. Whatever the case, by the time I got to my apartment at 1230 to sacrifice my day sorting it out, the described rescheduling and onlining had already happened. 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. It wasn't my intent to say that you were reporting as well, this is merely my side of the situation. You weren't part of the defending corp, so how can you possibly claim that what the GM's told you about rescheduling proves anything about what actually happened to the districts? I'm really intrigued how you know this. Should discuss this with me sometime what proof you have that lead to this statement. I don't have proof to provide. When I made it home, STB had attacked one of KEQ's districts which was newly onlined. There were two battles on it. KEQ's officers immediately moved to attack the other ones with the locking corp because we had no idea what was going on, but didn't want more attacks from STB or similar hitting the districts. So you relocked a district that had an attack on it when they had rescheduled it once already. :/ 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. I said the battles involved FA- whether or not they "should have" happened I have no idea after all the GM intervention. 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. Which is what I reported in the following paragraph. All I know is that the battle fought there was nullified. Our accounts jibe. Again, we had launched and attack on this district because it was online after GM intervention. So this portion has nothing to do with my post because it was on a separate unrelated district? Awesome sauce. Yes, because it explains the situation in full, especially in regards to how much GM intervention was going on. 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.
kayn TARON KILL-EM-QUICK RISE of LEGION 59	Posted - 2014.04.17 04:39:00 - [105] - Quote 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 :) Dust is marketed as an FPS/MMO. Can you name me one MMO that does not have a functional online friends list or PVE? lol
Leither Yiltron Ahrendee Mercenaries 872	Posted - 2014.04.17 04:46:00 - [106] - Quote Stiddlefaxq wrote: 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. I usually don't discuss this kind of thing on public forums, but it's important to note that I was kicked from KEQ after more than a year of service. I have absolutely no motivation for defending them arbitrarily. Like I said in my post, I personally own the corporation KEQ originally used to lock their districts. I set up the procedures they use for locking and sniping districts originally. This allows me to say without reservation that the way they lock districts with clone packs and snipe locked districts is to my knowledge the most efficient strategy under the conventional mechanics. It is also, like I described, prone to causing these multiple battle scenarios by accident. They are not advantageous, and are in fact annoying and stupid. They cost additional ISK and gain nothing. Just like someone posted in another thread, this can happen even when completely unrelated corps attack the same district as well. If they were rude to you in your meeting that's not fun, but it doesn't change the fact that they've been playing the game the only way they know how. When you contacted them whatever your offer was, it almost certainly sounded like it was to the tune of "please let us attack your district for free" to them. Considering that it's one of the last districts in Molden Heath that DNS doesn't own, they're probably zealous over its defense. Kane has been egging this whole thing on without acknowledging the full breadth of the way this mechanic works. If you want to I'll gladly talk to you about how this whole thing works in game. Send me a mail, I'm online right now. Overall though, I'd think as a community it'd be a lot more graceful if we'd all stop and take time to understand the entirety of how these types of mechanics work before trying to play finger pointing games. In the end CCP will resolve the situation to the best of their ability, and there's literally nothing this forum thread or any other is going to change that. Have a pony
CUSE TOWN333 KILL-EM-QUICK RISE of LEGION 368	Posted - 2014.04.17 04:51:00 - [107] - Quote Stiddlefaxq wrote: Leither Yiltron wrote: Zatara Rought wrote: Leither Yiltron wrote: 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. I received notification at around 10am, noticed it around 12pm. At that time I was told that exactly ONE of my corp's battles were incorrectly allowed through. Whatever the case, by the time I got to my apartment at 1230 to sacrifice my day sorting it out, the described rescheduling and onlining had already happened. 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. It wasn't my intent to say that you were reporting as well, this is merely my side of the situation. You weren't part of the defending corp, so how can you possibly claim that what the GM's told you about rescheduling proves anything about what actually happened to the districts? I'm really intrigued how you know this. Should discuss this with me sometime what proof you have that lead to this statement. I don't have proof to provide. When I made it home, STB had attacked one of KEQ's districts which was newly onlined. There were two battles on it. KEQ's officers immediately moved to attack the other ones with the locking corp because we had no idea what was going on, but didn't want more attacks from STB or similar hitting the districts. So you relocked a district that had an attack on it when they had rescheduled it once already. :/ 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. I said the battles involved FA- whether or not they "should have" happened I have no idea after all the GM intervention. 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. Which is what I reported in the following paragraph. All I know is that the battle fought there was nullified. Our accounts jibe. Again, we had launched and attack on this district because it was online after GM intervention. So this portion has nothing to do with my post because it was on a separate unrelated district? Awesome sauce. Yes, because it explains the situation in full, especially in regards to how much GM intervention was going on. 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. So you slander the crap out of a honorable gameing clan that has been around for 10 years because your "pretty sure" that we did something wrong. you guys are letting this 100% thing mess your head up to much. got outside get some air have a BBQ and enjoy life. dust is a video game and people just want to have good battles with each other don't ever forget that. trying to rule a game that is this small is cool and all but if you drive the player base away this game will die but KEQ will not. The clever combatant imposes his will on the enemy, but does not allow the enemy"s will to be imposed upon him. Sun Tzu
m twiggz Pradox One Proficiency V. 533	Posted - 2014.04.17 04:54:00 - [108] - Quote kayn TARON wrote: 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 :) 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.
STYLIE77 KILL-EM-QUICK RISE of LEGION 167	Posted - 2014.04.17 05:59:00 - [109] - Quote Leither Yiltron wrote: 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....
Tallen Ellecon KILL-EM-QUICK RISE of LEGION 1742	Posted - 2014.04.17 06:07:00 - [110] - Quote STYLIE77 wrote: Leither Yiltron wrote: 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.... Damn.... that ****'s good. You should give Cuse some lessons. Supporter of tiericide, EVE interaction, and a proper NPE SoonGäó514 "No blue tags make Tallen go crazy.

Blind Nojoy G I A N T General Tso's Alliance 166	Posted - 2014.04.17 06:19:00 - [111] - Quote CRUSADER2134 wrote: 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 don't think this statement could be any further from accurate. As far as I remember in Dust, CCP has NEVER done ANYTHING to ANYONE when it comes to bugs and glitches. Did they punish anyone for locking districts a few months ago? Did they punish anyone for using the melee glitch? When the CCP refunded people isk that they shouldn't have, and those people took that isk and bought hundreds of tanks and proto suits, and then ended up with a negative isk balance, didn't CCP just put them back to zero isk but let them keep all their stuff? When PC first dropped weren't people able to briefly send money from eve to dust? The only bans I've heard of in dust have been forum bans. And I really don't care about this game enough anymore to look the afformentioned incidents up, but that's what I remember....They haven't enforced anything in the past, why should they start now? Especially after I sold all my verizon stock and put all my money into Orville Redenbacher's....
Stiddlefaxq Vherokior Combat Logistics Minmatar Republic 41	Posted - 2014.04.17 07:46:00 - [112] - Quote m twiggz wrote: kayn TARON wrote: 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 :) 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. Wait, what happened?
whakatane77 KILL-EM-QUICK RISE of LEGION 9	Posted - 2014.04.17 09:42:00 - [113] - Quote We won three battles in a row, only two counted.
Weznof Nalek What The French Red Whines. 44	Posted - 2014.04.17 10:02:00 - [114] - Quote Kain Spero wrote: 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 think your attitude is disproportionate, you have more than 200 districts and you just cry foul for only 1. If CCP should make the right choice, it should already begin by removing your rights CPM.
Z3R0 GR4VITY Red Star. EoN. 349	Posted - 2014.04.17 14:39:00 - [115] - Quote This **** is getting ridiculous. All the QQ over a single district that a corp may have exploited game mechanics to save is stupid, especially because the ones who are QQ'ing have been exploiting game mechanics on a huge scale over the past month. If this is what the Dust community has become, I feel bad for the devs that make the game largely from suggestions of the people from this community. "Oh yeah, well where did you buy your clothes, the toilet store?"
diddy tanks KILL-EM-QUICK RISE of LEGION 0	Posted - 2014.04.17 15:45:00 - [116] - Quote This is hilarious. These boys are hilarious. It's a free game. CCP don't care (if they did player base wouldn't be horrible.). They should have included more players in matches, so d!ck heads like you who have no lives wouldn't have ruined this game. Dirt Nap Squad = bowl of (iiiiiiiiiii)
jerrmy12 kahoalii 1037	Posted - 2014.04.17 16:18:00 - [117] - Quote Free Beers wrote: VALCORE72 wrote: are they attacking them self ? didnt saber say you still could but would't get any isk from it ? if they have the isk guess the could keep it locked down for a while . 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. so what, they sent attacks to directs, how is that cheating Closed beta vet Tears, sweet delicious tears
Jin no kami Valor Coalition Red Whines. 45	Posted - 2014.04.17 22:27:00 - [118] - Quote Since everyone's here lets hold hands =ƒÖê=ƒÖë=ƒÖè
Ridire Greine 221	Posted - 2014.04.17 22:38:00 - [119] - Quote Jin no kami wrote: Since everyone's here lets hold hands =ƒÖê=ƒÖë=ƒÖè (>o_o)><(o_o<) "Jolly cooperation" Knight Solaire
Leadfoot10 Molon Labe. General Tso's Alliance 1064	Posted - 2014.04.18 05:09:00 - [120] - Quote Wow. Just wow. DNS QQing about a reattack bug on one district -- which was reported by KEQ. You have reached a new low.

Nothing Certain Bioshock Rejects 512	Posted - 2014.04.18 06:32:00 - [121] - Quote Wow, it is rare to see such hypocrisy. A bug worked in someone else's favor and the people who exploit every bug and advantage in the game act all indignant and righteous. This game is full of exploits, glitches, bugs and broken mechanics, the and protostomping is the biggest problem in this game but I have yet to see CPM Kain Spero remark on any of them not affecting his alliance. Blatant conflict of interest is fine? Because, that's why.
Sad Heavy Eternal Beings Proficiency V. 75	Posted - 2014.04.22 20:06:00 - [122] - Quote m twiggz wrote: kayn TARON wrote: 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 :) 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 still recovering my isk losses Scrubby Python Pilot, Corp Chat Troll, Elite Scrub, Caldari Loyalist
SoTasLost Property Kameira Lodge Amarr Empire 3	Posted - 2014.04.22 20:16:00 - [123] - Quote Worst thread ever. Come on guys, KEQ aren't 'glitchers' They simply do things differently then everyone else that just so happens locks them up in a way that prevents re-attacks. I mean, come on, it's not like they keep doing this so the happy 'mistake' can keep reoccurring - right? That's just plain foil capping.......................


Pages: 1 2 3 4 5 :: [one page]

COPYRIGHT NOTICE
EVE Online/DUST514, the EVE/DUST514 logo, EVE/DUST514 and all associated logos and designs are the intellectual property of CCP hf. All artwork, screenshots, characters, vehicles, storylines, world facts or other recognizable features of the intellectual property relating to these trademarks are likewise the intellectual property of CCP hf. EVE Online and the EVE logo are the registered trademarks of CCP hf. All rights are reserved worldwide. All other trademarks are the property of their respective owners. CCP hf. has granted permission to OMG Labs to use EVE Online/DUST514 and all associated logos and designs for promotional and information purposes on its website but does not endorse, and is not in any way affiliated with, OMG Labs. CCP is in no way responsible for the content on or functioning of this website, nor can it be liable for any damage arising from the use of this website.

Mike Ruan Said I was Dust Famous

Mike Ruan Said I was Dust Famous

Mike Ruan Said I was Dust Famous

Mike Ruan Said I was Dust Famous

Mike Ruan Said I was Dust Famous