I have full confidence in the customer support department to look at the cases very carefully :)

Question, do you, or to the GM's..

Assuming kills from this bug are reimbursed [ as they should be, this was a game bug ] will our modules be returned, along with the ship ? I know *normally* it's just modules that didn't drop. But in this case, they wouldn't have dropped if we were not victims of Concord, and with the Activity, and the GCC, we obviously could not go back to loot our own wrecks and recover any drops..

I ask because my alt dropped everything.. So getting just the Hull back, while a step in the right direction of course, is still only half way there :/

I have full confidence in the customer support department to look at the cases very carefully :)

even CONCORD wants to burn Jita

So maybe you can tell us all something mr dev

Eve is 9-10 years old yes?

FULL of bugs out the ass...


World of tanks just hit 1 year.

The biggest "bug" people complain about is in fact how things should work (not detecting camo netted tanks)

Can ya tell us why eve is just so full of fail when another game is so full of idk WIN?


Can you tell us why when WoT had server lag it took them 2 weeks to fix the issue yet took CCP years to call lag a feature, and still did not get it right?

Bug testing taking time my ass.... this just shows how little you people know...

No one ever thought "O hey since we are slowing down X let's make sure Y Z all tick at the same time"

Idk where I live... that is what gets you places... not sitting around being a brain dead code monkey.

we have already fixed it :) File a petition for any reimbursement.

-- :( Goliath types too fast!

The long and short of it is that the interaction between Crimewatch and Time Dilation prompted a little "disagreement" on criminal status.

Could you forsee this exact situation ? No..

The long and short of it is that the interaction between Crimewatch and Time Dilation prompted a little "disagreement" on criminal status.

I'm just going to say what everyone is thinking. As long as I'm reimbursed for my ships and sec. status I don't really care about this bug. Why? Because it's such a specific bug that we will likely not see it again for months, years, or potentially ever.

Think about it, how often do you have every last person in Jita shooting each other?

Just give me my stuff back, do what you can to fix this, and I'll be a happy consumer.

we have already fixed it :) File a petition for any reimbursement.

-- :( Goliath types too fast!

I'm just going to say what everyone is thinking. As long as I'm reimbursed for my ships and sec. status I don't really care about this bug. Why? Because it's such a specific bug that we will likely not see it again for months, years, or potentially ever.

Think about it, how often do you have every last person in Jita shooting each other?

Just give me my stuff back, do what you can to fix this, and I'll be a happy consumer.

Concorded and sec status lost, why?

That does not sound like a resounding yes. If not then thats just BS.

That does not sound like a resounding yes. If not then thats just BS.

That does not sound like a resounding yes. If not then thats just BS.

This sounds like you encountered the issue described in this thread. While the issue is now fixed, some people regrettably lost ships and security status. Please submit a petition if you feel you have unjustly lost your assets and this will be reviewed by our diligent Customer Support team.

This doesn't require a bug report as we have now fixed the issue. Your petition will be dealt with in due course and I cannot comment on possible outcomes.

Hi, I received a GCC for shooting Outlaws, and was Concorded, without warning, at Jita 4-4.

I waited out the timers and re-shipped and was Concorded for opening fire on hostile outlaws once more, without warnings.

I know Concord are busy and have much to do, would it be possible to give them one of them re-inforced nodes to keep up with stuff, rather than just shooting anyone that aggressives?

I understand this is probably an unforeseen edge case log, and I wish you good luck with that, sounds quite painful.

I would also like to use this opportunity to thank CCP for all their efforts to bring the Eve-Online community together and expand the user base, nice one, keep up the good work.

I submitted a petition, and I guess I will put in a bug report as well - but i was concorded when I legally shot a flashy. Is my sec status going to be fixed for this?

The long and short of it is that the interaction between Crimewatch and Time Dilation prompted a little "disagreement" on criminal status.

The long and short of it is that the interaction between Crimewatch and Time Dilation prompted a little "disagreement" on criminal status.

Notwithstanding that the issue you are describing and this issue are separate, as this issue has never arisen in the game before now (nor could it have, really, without a crazy chain of coincidence happening). The Crimewatch system has never been stressed with this many edge cases and mitigating factors before and we will endeavour to react quickly in identifying and resolving issues as they arise.

i m curious, why is the issue caused exactly? any technical details?

How much of a waste of time is it going to be when all the petitions for reimbursement of ships because you failed to see the inevitable come rolling in?

Better to fix a problem before it happens. Less manpower wasted.

Mr Epeen

How much of a waste of time is it going to be when all the petitions for reimbursement of ships because you failed to see the inevitable come rolling in?

Better to fix a problem before it happens. Less manpower wasted.

Mr Epeen

Yes we can automate that kind of scale, but it wouldn't be representative or controllable enough to find this issue.

How would a tiny scale "2000 character lag-fest in jita" even work? Can you artificially stress the server to that kind of extent?

You're using "edge case" in the wrong context twice there, also we don't test based around specific player driven events, we test based on professionally built, planned test cases. It's not like someone goes "hey Goons are going to be in Jita next week, let's try recreating it on a tiny scale on Sisi to see if we hit anything". That would be, as I have said, a massive waste of time.

Pretty sure you've had plenty of notice that this particular edge case was coming. I'm also pretty sure that you should have realized this particular edge case would have a major impact on the game.

I have to ask myself then, why was this particular edge case not thoroughly tested before it was too late?

I have my suspicions as to why, but I don't need any more of my posts deleted today so I'll just keep them to myself.

Mr Epeen

The chance of finding this bug would be the loose equivalent of finding a needle in a haystack which only appears when you are with three friends all performing an unrehearsed dance routine in a particular order.

When you say stress testing, I believe you are referring to mass testing, which only accounts for a tiny portion of our QA efforts and needs to cover a wide variety of topics each time - usually newer ones. For proper stress testing we use different techniques but none would have the individual manpower capable of finding a defect like this with any degree of confidence to make it worthwhile.

There has been plenty of testing, but replicating this particular scenario (which would be best described as an edge case) and then finding the defect (also an edge case) while also replicating all other possible edge cases would be a massive waste of time and resources and frankly almost impossible to do.

There has been plenty of testing, but replicating this particular scenario (which would be best described as an edge case) and then finding the defect (also an edge case) while also replicating all other possible edge cases would be a massive waste of time and resources and frankly almost impossible to do. No-one tests like that because of the wasteful nature of the testing, so you must account for the fact that edge cases arise, and if they are severe enough they get fixed at a high priority. The chance of finding this bug would be the loose equivalent of finding a needle in a haystack which only appears when you are with three friends all performing an unrehearsed dance routine in a particular order.

When you say stress testing, I believe you are referring to mass testing, which only accounts for a tiny portion of our QA efforts and needs to cover a wide variety of topics each time - usually newer ones. For proper stress testing we use different techniques but none would have the individual manpower capable of finding a defect like this with any degree of confidence to make it worthwhile.

I'm very happy to hear this is a bug, and not a case of "The Logs, they show nothing." :)

Annoying as it may be, I fully understand how these issues could have arisin.. Stress Tests on SiSi take place in null, So I doubt there has been nearly as much testing on TiDI and it's interactions with Crimewatch/Concord/etc.

Might be worth, in the future, moving stress tests alternating between Null, Low, and Highsec, to help detect any future issues.

Good thing they are putting out all these new dumb expansions when you have bugs that can cause sec + ship lose... LOL.

Failing for 2 years so far CCP

Still aint fixed the lag... calling lag a feature is not fixing it and now lul....

EVERYONE SHOULD PETITION FOR REPLACEMENT HAHAHAHAHAHAHAAAAAAAAAAA Load up that petition system really well.

Quite correct that a bug report would be the way to get this info to development. Petitions go to GMs.

Notwithstanding that the issue you are describing and this issue are separate, as this issue has never arisen in the game before now (nor could it have, really, without a crazy chain of coincidence happening). The Crimewatch system has never been stressed with this many edge cases and mitigating factors before and we will endeavour to react quickly in identifying and resolving issues as they arise.

Also, he didn't get the "You're about to commit a crime" dialogue even though he had the option for it active. So that is a bug.

So there I was, thinking of undocking for the first time in months to shoot some flashies, then I saw this and the pod thread, set another long train and alt-shift-q'd.

Keep up the good work CCP.

Pretty much typical CCP.

I'd love CCP to explain why some additional combat in a system that has it's own node, still requires huge Tidi.

Can you give us any details on this bug, for avoiding any appearance of us exploiting it? We wish to make the players in Jita suffer for their sins, but wish to do so honorably and within the EULA and TOS.

Notwithstanding that the issue you are describing and this issue are separate, as this issue has never arisen in the game before now (nor could it have, really, without a crazy chain of coincidence happening). The Crimewatch system has never been stressed with this many edge cases and mitigating factors before and we will endeavour to react quickly in identifying and resolving issues as they arise.

even CONCORD wants to burn Jita

Quite correct that a bug report would be the way to get this info to development. Petitions go to GMs.

Notwithstanding that the issue you are describing and this issue are separate, as this issue has never arisen in the game before now (nor could it have, really, without a crazy chain of coincidence happening). The Crimewatch system has never been stressed with this many edge cases and mitigating factors before and we will endeavour to react quickly in identifying and resolving issues as they arise.

A bug report wont get your sec status back up, its already been confirmed a bug, CCP should reimburse the status drop.

Posting to confirm that this is indeed a bug and we are looking into the cause of it now. More information to follow.

I think I see where everyone just got pwned who is shooting goons in Jita. And I think that was the plan all along.

Mr Epeen

That part is working as intended. What's not working as intended is pods still being flashy red after the ship kill, implying to everyone that they can be shot at without incurring a GCC.

Also, he didn't get the "You're about to commit a crime" dialogue even though he had the option for it active. So that is a bug.

No, it's not. The Goon he attacked was not an outlaw and he was not wardeced. He attacked a random player unprovoked and got Concorded for his trouble, just like he should have.

Posting to confirm that this is indeed a bug and we are looking into the cause of it now. More information to follow.

Concord is implementing a scorched earth policy!!! Too many gankers, too many ships... kill them all!!

sorry for you're lots

Why, I haven't had such negative emotions towards a catalyst since the ending of mass effect 3 (huhuhu)

Perhaps a bug report would have been more effective than a petition.

I posted a petition over a week ago now about concord warnings not showing up when you were about to unknowingly commit a crime. Still didn't recieve a message or anything on it, maybe you guys need to check your logs a little faster.

Posting to confirm that this is indeed a bug and we are looking into the cause of it now. More information to follow.

even CONCORD wants to burn Jita

It would be funny if this was due to CrimeWatch not compensating for Time Dilation. So on grid, the simulation knows that this guy is blink red for 15 minutes x 9 min/min time dilation factor (i.e.: about 135min), and these guys shot him at 20-odd minutes into the fight: target is blinky red on grid, so no CONCORDOKKEN warning. But Crime Watch (being external to time dilation) decides that the 15 minutes is well and truly up, and POW, RIGHT IN THE SMACKER!

Yeh had a similar issue. Shot a flashy red criminal and didnt get a concord warning (have it on atm to avoid issues) and concord proceeded to put me in my place _.

How convenient you get concorded for shooting flashies right at the weekend when goons do their burn jita campaign.

Devswarm strikes again.

You do realize they are going to get refunded right?

Please don't fix it too quickly. Tears are delicious.

Gyrostabs and blasters, I think CONCORD knew what they were doing, putting your lolfit out of its misery.

Gyrostabs and blasters, I think CONCORD knew what they were doing, putting your lolfit out of its misery.

thier logs show nuthin... move along nuthin to see here
any1 got kill rights on you?

EVE news24

many many others have had the same problem.


It is a Bug in the game. However, CCP will tell you its working as intended.

There may be an item on EVE news24 in the next day or so on this very problem.