These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

EVE New Citizens Q&A

 
  • Topic is locked indefinitely.
 

Cross-Corporation Fleets, Wardec, and being CONCORD'ed
Author
Previous Topic Next Topic
Dorvius
Imperial Academy
Amarr Empire
#1 - 2017-07-02 05:06:57 UTC
Assume Players A and B are members of Corporation 1. Corporation 1 is under wardec from their long-time enemy, the brutal Corporation 2.

Players A and B form a fleet with Player C, who is a member of Corporation 3. Their corporations are not in an alliance together. If a player from Corporation 2 encounters this fleet, may he shoot Player C in highsec without CONCORD involvement? If a player from Corporation 2 engages Player A or B can C participate in the fight without CONCORD involvement?
ShahFluffers
Ice Fire Warriors
#2 - 2017-07-02 06:43:50 UTC  |  Edited by: ShahFluffers
The answer is no to all of the above.


The only way any member of Corporation 3 can engage Corporation 2 is if they have joined as official allies of Corporation 1 (in other words, Corp 3 has to join the war dec).

Exception: If a member of Corporation 3 provides remote assistance to a member of Corporation 1, they will be flagged as "suspect status" and can be engaged by anyone in the game.

If anyone shoots a person with "suspect status" then said person can engage back (but no one else).

How did you Veterans start?
Dark Lord Trump
Infinite Point
Pandemic Horde
#3 - 2017-07-02 18:53:15 UTC
Joining a fleet does not modify rules of engagement.

I'm going to build a big wall that will keep the Gallente out, and they're going to pay for it!
Memphis Baas
#4 - 2017-07-03 04:04:57 UTC
A and B will see C as purple (member of fleet), D as red blinky war enemy.
C will see A and B as purple (in fleet), D as neutral.
D will see A and B as red blinky war enemy, C as neutral.

When D vs. A + B start shooting, CONCORD isn't called because there's a war going on between the players. No one gains suspect status because the shooting is warranted by the war.

From player D's point of view, C will remain a neutral even after the shooting with A and B starts.
From player C's point of view, D is a neutral.

If C takes action against D, Concord will intervene. If D takes action against C, Concord will intervene. However, if all players involved have green safety settings in their HUDs, the guns won't activate in the case of C vs D, thus avoiding the Concord reaction.

As explained above, C can get involved by remote-repairing A or B, thus becoming suspect. At that point D can shoot C, and C can shoot back.

Basically, the combat rules and flags are not affected by fleet status. The Overview makes it clear who's enemy and who isn't, but it helps to make sure you have the Overview configured properly, with the red conditions where you can shoot being above (higher priority than) peaceful conditions like "he's in my corp, alliance, or fleet". And keep your safety settings to green.
Sabriz Adoudel
Move along there is nothing here
#5 - 2017-07-03 08:49:29 UTC
The easiest way to check this is to set your safety to green or yellow, and watch what happens when you try to shoot.

The rules of highsec combat do not care one iota about your fleets. Only corporations matter.

I support the New Order and CODE. alliance. www.minerbumping.com
Dorvius
Imperial Academy
Amarr Empire
#6 - 2017-07-04 05:14:44 UTC
Memphis Baas wrote:
A and B will see C as purple (member of fleet), D as red blinky war enemy.
C will see A and B as purple (in fleet), D as neutral.
D will see A and B as red blinky war enemy, C as neutral.

When D vs. A + B start shooting, CONCORD isn't called because there's a war going on between the players. No one gains suspect status because the shooting is warranted by the war.

From player D's point of view, C will remain a neutral even after the shooting with A and B starts.
From player C's point of view, D is a neutral.

If C takes action against D, Concord will intervene. If D takes action against C, Concord will intervene. However, if all players involved have green safety settings in their HUDs, the guns won't activate in the case of C vs D, thus avoiding the Concord reaction.

As explained above, C can get involved by remote-repairing A or B, thus becoming suspect. At that point D can shoot C, and C can shoot back.

Basically, the combat rules and flags are not affected by fleet status. The Overview makes it clear who's enemy and who isn't, but it helps to make sure you have the Overview configured properly, with the red conditions where you can shoot being above (higher priority than) peaceful conditions like "he's in my corp, alliance, or fleet". And keep your safety settings to green.





Thanks for the detailed writeup! That lays things out a lot more plainly for me. I suppose I was under the incorrect assumption that being in a fleet treated aggression against one fleetmate as an aggression against all. I know better now!

Much appreciation for everyone who replied.
Memphis Baas
#7 - 2017-07-04 17:54:16 UTC
There's no outward indication that anyone is in a fleet. If you're not in the fleet, you don't see any indication of a fleet, you just see a bunch of ships sticking together, or acting coordinated, for no particular reason. There's no purple color, nothing.

So, "aggression against 1 = aggression against the fleet" would really suck from an outsider's point of view. You're trying to shoot what appears to be a random neutral, and all of a sudden your whole screen becomes red.

As players, we would exploit the hell out of this "surprise, mofo" game mechanic, if it existed.