TLDR: Expand CONCORD into low-sec.
Caveats: Players enrolled in FW and/or piloting combat ships are ineligible for CONCORD protection; protection is only available for mining ships, haulers, freighters and industrial ships. Availability: 0.3-0.4 systems only.
Asbestos suit on.
3 Likes
If it had been anybody else I might have considered this a serious suggestion
1 Like
Ha no.
Imagine how incredibly annoying it is to get into a fight in low sec, and some dudes in Squall join the hostile fleet and start firing light missiles at your fleet. You fight back, and suddenly your fleet gets CONCORDed. 
Just because some ships are used for hauling or mining doesn’t mean they cannot also be very effective combat ships. I remember a guy in my alliance who always was immediately on top of hostile fleets providing warp-ins in his combat probing Venture. He was a legend for it.
Let’s keep CONCORD nicely contained in HS space.
1 Like
The combat timer would preclude CONCORD intervention (in your example).
It would be absolutely hilarious watching CONCORD obliterate gate camps on low-sec entry points.
Sorry, I added some more text while you posted that.
The combat probing Venture in my example wouldn’t get a combat timer, but would be a massive combat help. And you would be unable to attack him without getting CONCORDed.
1 Like
Timer for combat probes? We get one for Bastion…
So anyone who wishes to find their own MTU in HS now can be freely engaged by anyone who accidentally got caught in their probe scan?
I think that causes more problems than it solves.
60-second combat timer… (no docking or gate jumping)
So mining in lowsec would be safer than highsec? How do you plan on ganking a rorqual when it has CONCORD protection?
1 Like
We need things to generate more combat not less.
BUT…
They would show, but it would be extremely random
When they arrive, it is of a random size, 1 to 10?
Those ships are composed of a faction type Navy ship, not the real CONCORD.
They can be killed or fought with? Affects your NPC concord standings?