Oh yes, there is. You repeated a lie about me three times in that post. If you are in non mod persona you have no place to tell me to not reply. If you are telling me not to reply in mod persona, you have no basis to falsely accuse me. To wit:
Nobody posted it was an attempt to introduce the cap, so you are making things up (1).
How can they take something down that wasn't there? Nobody posted there was a cap.
You are making things up (2) to support your theory.
the more you make up (3).
Well, somebody is making stuff up.
Why would I make stuff up when INNO is the one who wrote it and you provided the link? From the Mar 5 Clarification:
This week, we moved forward with an update that sets a limit on Quest Aborts to prevent this exploit, and the impact it has on our servers.
Argue with that.
Not going to discuss this with you any further.
That's one way to avoid giving me the apology I'm due from you for repeating a lie three times.
Anyway, I'd appreciate instead of you erasing your false accusations, you edit in an apology after each of the false accusations stating you were wrong to accuse me of making up that INNO said the 2 second delay was a result of trying to introduce the Abort cap.
Damn straight I'm up in arms about this. When I make a mistake, I own it.
Let's see you do the same.
Now the real fact. Nobody "skipped right over" CMT. That account was used to post the message, cause CMT wasn't in the position to post it at the moment, so CMT asked to do it for them.
I don't understand this. Possibly the last line in that is missing a phrase and should read "so CMT asked
the account holder to do it for them."
None of four CMT could get to the forum. I'm sure it's me comploticizing, but somehow I find that a bit disturbing.
Yeah, I am finding fault with everything CMT has done over the last 6 weeks regarding the Abort cap, maybe it's because I'm paranoid.
Or it could be that to this point nothing CMT has done regarding communicating about the Abort cap has been right.
Not the first time that happened and most likely not the last time. I am sure you do not believe me and want to stick to your own theory, cause that suits you much more, but just have a look on other forums. You will see a mix of that account and CMT posts.
Sure. As always, I reject your contention posters on this forum should be expected to know, understand, or follow what happens on another forum.
From the forum rules:
- It is permitted to discuss other FoE servers, but please bear in mind that they are separate entities, and what goes for one may not necessarily go for another. There are some exceptions to this rule:
'Cause it's only happened twice here in the past 7 years, both times regarding the Abort cap.
As stated, a lot, it's not my job to communicate the state of the game, it's CMT's.
Do not want to give you a platform for your complot theories. The more facts I give you...
...the worse CMT looks.
If I point to three mistakes or unsupported opinions you posted in this thread will you retract the word 'facts'?
I'm looking forward to that apology.
----------
There was no cap when the delay was in place. It only slowed me down, and made it more mundane but I still had more than 2,000 aborts. That would only have been looping on about 20 large GB's which I usually do around 40 or 50 a day.
Thanks for the information.
As noted uppost INNO posted this two days after the delay started:
This week, we moved forward with an update that sets a limit on Quest Aborts to prevent this exploit, and the impact it has on our servers.
Thanks for pointing out my mistake, I appreciate it.
Mea culpa, I was wrong. Pretty stupid of me to believe it when INNO said they had deployed the Abort cap. I should have remembered the current cycle of crappy QA of course they would screw the Cap limit rollout, too.
