Originally by: Haniblecter Teg

---

My concern is the last paragraph stating tha tyou will now actively check for market anomolies.

Dropping this hint is only going to make it harder to detect duping, because then dupers are only going to shuffle their assets around to make the dent on the market smaller.

---

Originally by: Cadde

---

Edited by: Cadde on 10/02/2009 17:52:00
Page 1 on a long blog!

Good stuff

EDIT:

I would also like to know where all the generated isk went, as stated in the blog:

"Between 6 and 12 TRILLION isk has been gained from this exploit"

Just to put it into perspective, that is between 6,000 and 12,000 BILLION isk, enough to purchase and decently fit about:

---

Originally by: Valeria Crossroads

---

"Users directly involved in the exploit were permanently banned. Direct involvement meant that the character had a director role in the corporation using the exploit or was directly involved in servicing the POSes in exploited state."

This highly upsets me. In my corp we have several people who have the freedom to setup their own posses. Its their responsibility to maintain it. They quoted text means that if one of them turns bad: me and my directors get perma banned without us doing anything wrong ourselves. This is of course completely unacceptable and unfair. Banning guilty people OK, but being a CEO or director does not automatically means you knew what was going on and thus cannot mean that you get banned too.

---

Originally by: Anaesthera

---

Fascinating read, but I may have to read it twice to understand it all.

Question....don't you guys have a way to run a query that, for example, checks the top 20 ISK earning corps and individuals? And then check exactly why they are in the top? A corp making trillions of isk has got to raise a red flag.

---

Originally by: Valeria Crossroads

---

Edited by: Valeria Crossroads on 10/02/2009 20:40:19

Originally by: Raymon James

---

. . . where were you when BoB was disbanded?

this is a TOTAL PvP game, you better bloody well know what the people under you are doing. Especialy when they are embarking on something on this scale.

---

You cannot and should not be punished for crimes someone else did. It ridiculous that if you are a CEO of a company and some employee commits a crime that you also should go to jail. Only the real guilty should be punished. What you are saying would never hold up in a real court case, cause it must be proved that without any doubt a person knew what was going on. And in our setup no isk goes through the corp wallets. That ccp produces faulty code is their problem. Punishing people who did not knew that a certain exploit existed is unacceptable.

---

Originally by: John McCreedy

---

Two questions need to be asked:

1. What action, if any, has been taken against the GMs who did not correctly investigate the petitions filed to see if these where widescale exploits and made erroneous assumptions?



2. Can and will you give us a guarantee that in future, any petition in any catagory of a nature involving "dumping" will be investigated to determine whether it is an isloated incident or, as was the case here, an exploit on an industrial scale?

And for once in yoru lives, don't treat this enquiry as a "capsuleer" but rather as a subscriber to your product because that is why you have ongoing customer service problems. We need somebody from CCP to make a pledge that no more assumptions will be made and investigations will be made to uncover the facts so as to avoid anything like this ever happening again.

J

---

Quote:

---

To date, we have found three petitions regarding the reactor bug in our systems. Two of those are since late October 2005 and one since late October 2007. In all cases, the issue was handled as an isolated bug for the players reporting it and the work done was geared towards fixing that particular issue.

In one of the older cases, the user petitioning was asked to file a bug report but the resulting report was closed after the bug hunters were not able to reproduce the issue. At the time, no procedures were in place on our end to ensure that reproduction steps were included. Nowadays, our bug hunters will contact the player submitting the report and request that the steps be added if they are missing.

Quite frankly, it must be said that at the time, the documentation and logs available for POS-related things left much to be desired and anyone involved in handling such issues would have been facing a very difficult task indeed. Very little information was available to staff and players alike about how things were supposed to work and what little logs existed were in no way sufficient to provide information needed to successfully tackle problems with POS mechanics. The usual stopgap fix was to simply repackage the structures and hope that it would take care of the issue at hand.

The last petition was correctly filed into the exploit category but it was simply handled as an individual problem for the player reporting it. Thus it fell through the cracks and did not raise the flags it should have and no exploit investigation was launched.

---