Miners are pretty bad, too. Stealing all the ore for themselves that is supposed to be used for the common good; stripping asteroid belts to nothing, two hours after downtime. The insatiable maws of greed.
I think there could be an argument for having the player owned station have a suspect timer for allowing criminals to tether. If a player gives logi support to a criminal they join them in being suspect, right? Why not player owned structures. How long should such a timer last? Long enough for the structure to become a pinata?
Not anymore since quite some time by now…
April Changes - Removal Of Neutral Assitance
Following the round of high priority loophole closures and bugfixes in March, we are also prepping a set of changes to the mechanics around highsec “neutral assistance” for the April release.
Removal of neutral assistance
Under current mechanics, if a neutral character applies a remote assistance module (such as a remote repairer) to another character they can receive a suspect flag if their target meets all of the following conditions:
- is involved in a war (including normal wars or FW)
- does not share a corp/alliance (or FW side if the war in question is the FW war) with the assistor
- is engaged in PVP (has a capsuleer logoff timer)
As well, area of effect command bursts currently apply to every member of a pilot’s fleet that is within range, without distinction for whether those fleet members are at war.
In both of these cases, the resulting gameplay can be frustrating and unfun as combatants cannot effectively engage neutral repair ships until they activate their modules and cannot engage neutral command bursting ships at all without incurring CONCORD’s wrath.
Recently the bulk of the community feedback we’ve been seeing on these particular issues has been in favor of making direct changes to remove these tactics.
After the April release, the penalty for direct targeted neutral assistance meeting the conditions above AND occurring within highsec will become a criminal flag and CONCORD response. The safety system will prevent the activation of the targeted assistance modules under these conditions, so we suggest that support pilots in highsec engage their safety at either green or yellow levels to prevent unintentional CONCORDOKKEN.
For area of effect command bursts we are approaching the problem a little differently as you may want to continue boosting the members of your fleet that are not involved in a war. Therefore, after the April release neutral command bursts will simply not affect a pilot that meets the conditions listed above when activated in highsec space.
The increased penalty for neutral targeted assistance will also apply to limited engagements (such as those caused by duels) but for performance reasons we won’t be preventing command bursts from applying to pilots in limited engagements.
Neither of these changes impact assisting your corpmates or alliancemates in a war (since you’re in the same war as them), and neither of these changes apply to lowsec (the penalty for targeted neutral assistance in lowsec will continue to be a suspect flag just like today).
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.