first
So this will be turned on with the next patch?
Or just on SiSi?

Soooo the only thing that matters for me is: does it use any additional Windows OS components and therefor does it still work on Linux through WINE?

... and Mac?

Thanks for the reply. Standard libraries sounds good, it's probably just working ootb. Guess we have to wait for tomorrow. (Setting long skill to be trained.)

What is defined as a 'crash' ?

Does that include when clients stop responding, but never close?

Does that include when internet connection drops causing the client to stop receiving packets?

What events will cause the crash report to actually be filed?

I'm a bit curious as to whether this will only catch EVE-specific crashes or whether it will be able to report cider-related ones as well (or, worse, I'd imagine, ones where EVE and cider collude to make my life miserable)?

That refers to the standard Windows thing, and is unclear on the CCP error reporting.

I appreciate that, thanks.

Solo Drakban makes a good point - is mandatory reporting being patched out before release, or in winter expansion 1.1

and... there is always the possibility that a flaw in the tool or a hacking event might turn it into something malicious that grabs personal info. If you willy nilly allow data to be sucked off your computer then be prepared for serious RL consequences.


+1 to the Dev's!

First, I believe you need to look up the definition of "bragging". I was not bragging, I was merely stating an example. Also, I'm not sure what game you're playing, but EVE is generally not a 'busy' game. Except during instances of combat, a lot of EVE can be played with it in a window with only one eye paying attention to things happening while you actually do useful things in another window.

Also, I am aware that it's my responsibility, which is why I was asking for the ability to opt into the data collection with the ability to review the data being sent so that I can verify what CCP is collecting and make the determination on if the data can be sent. The alternatives are to not load EVE while doing other things (which may be a blessing in some respects) or take actions to block their crash reporting system (which wouldn't be of benefit to anybody as they would then never receive a crash report as I would just set it and forget it).

I honestly don't get why people are still on about this. CCP said "Hey, awesome crash collection stuff coming up!" to which the question was asked "Is it optional?" CCP quite reasonably said "Oops, not now but we'll make it so!" and everything was fine. I would have preferred it be optional on launch but, again, a Dev gave a reasonable alternative if there were any reservations about the system until they could add the opt in, and again, everything was fine.

Then people came out of the woodwork with "if you have nothing to hide..." crap which is why some of us were giving examples of why we would indeed care. Regardless of how relevant you think they are, I do appreciate that CCP has addressed the concerns.

Actually, no, that's not what has us 'all jittery'. I'm fine with CCP getting a list of all my running applications (as I have said before), injected into EVE or not, so long as they are up-front about it (hell, Sreegs is welcome to show up at my place unannounced, crash on my couch and go through my computer himself looking for bots) so I can make the decision as to what applications to run at the same time as EVE. I also want the chance to review what they are sending as they currently have some ground to cover to regain my full trust in their statements.

It's all about informed consent balancing against the need for privacy.

this indeed can be a good base for a new tool to check for RMT. Regular autoupload of memory dump to eve servers, no optout, autoban if bot is found. simple :)

I would love to see a graph of the crash data that you have collected thus far.