One of the situations that inspired this idea is small-gang PvP.
A small group can take a fight, commit to a target, and suddenly a cyno is lit and a much larger force appears — for example a capital fleet, a large Black Ops drop, or another form of rapid escalation.
The problem is not that cynos exist or that escalation exists. Both are important parts of EVE.
The problem is that, once the cyno ship is on grid and the cyno goes up, the smaller group often has very little meaningful counterplay other than killing the cyno ship immediately or trying to disengage before the reinforcements arrive.
I would like to suggest a new tactical tool:
Cynosural Disruptor
A ship-mounted module that targets the ship generating the cyno.
The goal would not be to remove hotdrops, capitals or Black Ops gameplay.
The goal would be to give small and medium gangs a risky, close-range way to fight over whether the cyno succeeds.
How it would work
The Cynosural Disruptor would always target the ship responsible for generating the cyno.
For example:
-
Arazu
-
Falcon
-
Rapier
-
other Recon ships
-
other ships capable of fitting the relevant cyno
The module would not target the cynosural field itself.
Case 1 — Cyno has not been activated yet
If the Cynosural Disruptor is active on the target ship, that ship cannot activate its cynosural field.
The disrupting ship must maintain:
-
target lock
-
module activation
-
short range
-
sufficient capacitor
If any of these are lost, the target can attempt to light the cyno again.
Case 2 — Cyno is already active
If the target ship has already activated its cyno, the Cynosural Disruptor can still be used on that same ship.
The module begins a disruption cycle.
For example:
10 seconds
If the disrupting ship maintains lock, range and module activation for the entire cycle, the active cynosural field generated by the target ship is forcibly shut down.
If the disruptor loses lock, is jammed, neuted, forced out of range or destroyed before the cycle finishes, the cyno remains active.
This gives the side using the cyno time to react.
Example situation
A small PvP gang engages another group.
An Arazu decloaks and activates a cyno.
A large Black Ops fleet or capital force begins preparing to jump.
Instead of having no option other than immediately leaving or killing the Arazu through raw DPS, one pilot in the small gang can commit a specialized ship to stopping the cyno.
The pilot:
-
Locks the Arazu.
-
Gets within approximately 5 km.
-
Activates the Cynosural Disruptor.
-
Keeps the module active for the full cycle.
-
If the cycle completes, the cyno shuts down.
The cyno fleet now has a tactical objective too.
They can:
-
kill the disrupting ship
-
jam it
-
neut it
-
web it away
-
force it outside module range
-
break its lock
-
protect the cyno ship long enough for reinforcements to arrive
This creates interaction for both sides.
Why very short range?
The module should not become a safe long-range anti-cyno weapon.
Using it should require commitment.
A range of approximately:
5 km
would mean the disrupting ship has to physically approach the cyno platform.
That ship is therefore putting itself in significant danger.
This is especially important in Black Ops situations.
A Recon ship could still decloak and immediately light a cyno.
The enemy would then have to react quickly, approach the cyno ship and survive long enough to complete the disruption cycle.
Possible module characteristics
These values are only examples for discussion.
Cynosural Disruptor I
-
Targeted module
-
Optimal range: around 5 km
-
Cycle time: around 10 seconds
-
High capacitor consumption
-
Significant CPU / powergrid requirements
-
Cannot be used while cloaked
-
Only one target at a time
-
Requires continuous target lock
-
Active cyno only shuts down after a full uninterrupted cycle
Possible ship restrictions:
-
Heavy Interdictors
-
Recon Ships
-
or a new specialized hull
I think Heavy Interdictors could make sense because they are already designed around controlling movement and force projection.
Recon Ships could also make sense thematically, although balance would obviously be important.
Mobile Cynosural Inhibitors would still have a role
This would not replace the Mobile Cynosural Inhibitor.
The Mobile Cynosural Inhibitor is an area-denial deployable.
The proposed Cynosural Disruptor would instead be:
-
reactive
-
targeted
-
short-range
-
ship-mounted
-
vulnerable to electronic warfare
-
vulnerable to capacitor warfare
-
dependent on keeping the disrupting ship alive
They would serve different purposes.
Main goal
The idea is not:
“Cynos are too strong, remove them.”
The idea is:
“If someone commits a ship to opening a cyno in the middle of a fight, the enemy should have a difficult but possible way to fight over that cyno.”
A small gang should not automatically defeat a capital fleet or a Black Ops drop simply because one member fitted this module.
But it could create a few seconds of meaningful gameplay where both sides have objectives.
The cyno side wants to protect the cyno long enough for the escalation to arrive.
The defending side wants to get a specialized ship onto the cyno platform and maintain disruption long enough to shut it down.
That could turn:
Cyno appears → 30 ships arrive
into:
Cyno appears → disruptor commits → both sides fight over whether the escalation succeeds.
I think that could create interesting small-gang, lowsec and nullsec engagements without removing the strategic importance of cynos.
All numerical values above are only examples and could obviously be adjusted for balance.
The images below are AI-generated concept illustrations and are only included to visually explain the idea. They are not official EVE Online or CCP assets.
