EVE Information Portal

Were is the game breaking issue ? i clicked here for nothing ?

Read dev's blog's working as intended . Giving the criminal a "chance" jumping xx on 1 with a logi isnt a chance . The explanation so the target HAS a chance even small to fight back .
scenario A : you kill him without logi pilot = gg no need for him to get a S flag
scenario B : you CANT kill him without a logi pilot = criminal has a chance , if logi helps you someone can kill it

pretty fair






Limited Engagements

The personal-flags system tidies up a lot of problems with the old system, but still leaves us with a couple of cases that aren't covered. The main one is that a suspect can be freely attacked, but he has no way to defend himself from attack without committing further crimes. We want to ensure that a player always has a right to self-defense, even if he is A Bad Guy. To solve this, we still require a form of A-B flagging. However this will be heavily limited in application, and won't be propagated via assistance chains like the existing aggression flags are. This is where we introduce the concept of a Limited Engagement. An LE is between a pair of characters. (Always characters, not corps, alliances, factions or anything else). An LE gives each party a legal right to attack the other, without triggering any Legal flag. An LE is ACTIVE as long as offensive actions are on-going. Once offensive acts have stopped, it will begin to count down. Resuming hostilities will reset the timer. If the timer expires (probably 15 minutes but still TBC) then the LE is ended. An LE is created when character A attacks character B, and where B is globally-attackable due to being a Suspect, Criminal or Outlaw. This then allows B to defend himself against A. Like Criminal and Suspect flags, An LE is only effective in empire space. Assisting someone who is engaged in an LE will cause the assistor to receive a Suspect flag. This is to prevent NEUTRAL LOGISTICS interfering in ongoing combat without risk to themselves.

Interesting, could you link the dev blog?

Also your scenario involved xx jumping on 1, what if the situation is xx jumping on xx, then xx's friends come from the HS gate and attack the logi. If you try to engage them the gate guns will shoot you and also if you jump into HS after them you cannot shoot them but everyone can shoot at you.

http://community.eveonline.com/devblog.asp?a=blog&nbid=73443 <---- Blog clickz

Dont use xx for first party and for second ... use different letters xx = xx , but there are 2 parties .
So players A attacks players B , B friends come to help , and kill the logi . Thats the right scenario ?


A can be replaced with xx , but let the B be something else like zz or yy :)

I read through the blog, and the issue with logistics getting a suspect flag for helping during a limited engagements should only apply to high sec, not to low sec or WH space. I am not sure why this is occurring, and unless CCP has made any changes since the release of that dev blog then this is indeed a bug.

From what I understand the logistics will rightfully get all the flags of the person they are assisting. The exception is in high sec where they will also get a suspect flag. This should not though be occuring in WH space and in low sec according to the Dev blog.

Nobody gets a suspect flag in corp-on-corp violence. Except very occationally neutral rr. For reasons unexplained.

Incorrect. This is quoted according to the dev blog. "An LE is only effective in empire space"

The suspect flag is only given when assisting a limtied engagement, as LE's do not happen in low sec or WH space, no suspect flag should be given.

Ok, low sec may have been referred to as empire space in the dev blog. But that doesn't explain the suspect flag still occuring in WHs also. So still strange behaviour which seems to be not working as intended, at least in the case of WHs.

Well, the issue can be worked around in low sec, although it isn't ideal in my opinion as I believe the logical way would be for the logistics to simply get all of the flags which the person he is assisting has. But if this is working as intended then I guess I will work a way to deal with it.

But like we both agree, it does appear the issue in WHs is not meant to be happening. I will replicate it later and submit a bug report.

Thanks for being helpful and clarifying things.

For info, after resolving issue i had.

I updated eve on my other comp. Ran out of space, update got aborted. I cleared some space, and tried again.

End of story is that i couldn't start eve. If i tried safe mode, i got an error log that ended on:

"ImportError: No module named email.utils"

Repairs, reinstalls, changing locations, nothing helped.
After much googling and asking around, i was still stumped.

My solution is not 100% narrowed down, but i can tell ya for me it was either lack of .NET framework update, or DirectX. I updated both before i reinstalled, so i couldn't tell you which one of them it was.

Anywho, just wanted to put it in writing for the few that have the same problem.

NPCs will now only target drones in their size category.

Elite frigates and cruisers NPCs will go for small drones and above.
Frigates and Cruisers NPCs will go for medium drones and above.
Battleship NPCs will go for large drones.

What does this mean for sentry drones?