CUSE TOWN333
KILL-EM-QUICK RISE of LEGION
340
|
Posted - 2014.04.16 05:01:00 -
[1] - 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
|
CUSE TOWN333
KILL-EM-QUICK RISE of LEGION
345
|
Posted - 2014.04.16 12:18:00 -
[2] - 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
|
CUSE TOWN333
KILL-EM-QUICK RISE of LEGION
368
|
Posted - 2014.04.17 03:57:00 -
[3] - 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
|
CUSE TOWN333
KILL-EM-QUICK RISE of LEGION
368
|
Posted - 2014.04.17 04:51:00 -
[4] - 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
|