# Ship-mounted Cynosural Disruptor — Active Counterplay to Cynos **URL:** \ **Category:** Player Features & Ideas\ **Created:** [September 23, 2026, 4:58pm UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815 "2026-09-23T16:58:57Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Askanher\_Krividus](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/askanher_krividus/32/512030_2.png) [@Askanher\_Krividus](https://forums.eveonline.com/u/Askanher_Krividus)\ **Post date:** [September 23, 2026, 4:58pm UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/1 "2026-09-23T16:58:57Z")
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: 1. Locks the Arazu. 2. Gets within approximately 5 km. 3. Activates the Cynosural Disruptor. 4. Keeps the module active for the full cycle. 5. 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. ![anty cyno](https://global.discourse-cdn.com/eveonline/original/4X/c/1/7/c17a43f97818d97c7a3e8fb13fb603c0b3e3ffa7.png) ---
**Author:** ![Starcrusher\_Almighty](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/starcrusher_almighty/32/416413_2.png) [@Starcrusher\_Almighty](https://forums.eveonline.com/u/Starcrusher_Almighty)\ **Post date:** [September 23, 2026, 5:16pm UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/2 "2026-09-23T17:16:57Z")
Amazing idea. Please implement!!! ---
**Author:** ![Gerard\_Amatin](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/gerard_amatin/32/481361_2.png) [@Gerard\_Amatin](https://forums.eveonline.com/u/Gerard_Amatin)\ **Post date:** [September 23, 2026, 6:53pm UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/3 "2026-09-23T18:53:45Z")
I like the idea. One issue I however see is that targeting a ship takes time while many of the cyno-capable ships are covops. This means that a covops ship can drop cloak and instantly light a cyno on you before you have the opportunity to target them and block their cyno. This brings me to another cyno adjustment I wouldn’t mind seeing: a small spool-up delay on cynos after activation and before it becomes a jumpable beacon. It doesn’t have to be long, only a few seconds at most to allow players to start preparing a reaction to the incoming force. People could start aligning out if not tackled, or they could put pressure on the cyno-capable ship and possibly take it out before the beacon goes up. While a spool-up timer has been a balance improvement to cynos that I’ve had in mind for a while, I think it’s also an essential change in order for your suggestion to be effective. Without it people could simply ignore your module and drop a fleet on you anyway, despite your cyno disruptor. ---
**Author:** ![Askanher\_Krividus](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/askanher_krividus/32/512030_2.png) [@Askanher\_Krividus](https://forums.eveonline.com/u/Askanher_Krividus)\ **Post date:** [September 24, 2026, 6:27pm UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/4 "2026-09-24T18:27:58Z")
That is a very good point, and I agree. A cloaky Recon such as an Arazu or Falcon can decloak and light the cyno almost immediately, so by the time someone finishes locking the ship, the cyno may already be active and ships may already be jumping through. I think a short activation delay would work very well together with the Cynosural Disruptor. I would not want it to be long, because covert cynos and surprise escalation should still be powerful, but something like 2–5 seconds could give players enough time to react. That could create two stages of counterplay: 1. Stop the cyno during its short activation period. 2. If that fails, keep the Cynosural Disruptor on the cyno ship and, after a full cycle, shut down the already active cyno. I think your suggestion actually makes the whole concept work much better. Thanks for bringing it up. ---
**Author:** ![Lucy\_Alfrir](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/lucy_alfrir/32/382506_2.png) [@Lucy\_Alfrir](https://forums.eveonline.com/u/Lucy_Alfrir)\ **Post date:** [September 24, 2026, 10:39pm UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/5 "2026-09-24T22:39:00Z")
Surely any dps module, gun, missile launcher, drone is a Cyno Disruptor. Blow up the cyno ship, no more cyno. I’m not entirely against the concept of slower conduits, or a cyno delay as said elsewhere. But the OPs suggestion is just a shortcut of already existing mechanics. ---
**Author:** ![Arthur\_Aihaken](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/arthur_aihaken/32/504104_2.png) [@Arthur\_Aihaken](https://forums.eveonline.com/u/Arthur_Aihaken)\ **Post date:** [September 25, 2026, 12:42am UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/6 "2026-09-25T00:42:37Z")
What about removing all cynos from low-sec except industrial ones? ---
**Author:** ![The\_Tapioca\_Terrorist](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/the_tapioca_terrorist/32/493091_2.png) [@The\_Tapioca\_Terrorist](https://forums.eveonline.com/u/The_Tapioca_Terrorist)\ **Post date:** [September 25, 2026, 8:39am UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/7 "2026-09-25T08:39:14Z")
how do you move carriers and dreads etc? ---
**Author:** ![Lucy\_Alfrir](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/lucy_alfrir/32/382506_2.png) [@Lucy\_Alfrir](https://forums.eveonline.com/u/Lucy_Alfrir)\ **Post date:** [September 25, 2026, 9:03am UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/8 "2026-09-25T09:03:29Z")
With a Rorqual ---
**Author:** ![Mephiztopheleze](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/mephiztopheleze/32/381036_2.png) [@Mephiztopheleze](https://forums.eveonline.com/u/Mephiztopheleze)\ **Post date:** [September 27, 2026, 5:24am UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/9 "2026-09-27T05:24:32Z")
i think this would lead to a lot of people targeting their own cyno ships with this thing on move-ops rather than sit through the whole cycle of a cyno… light cyno jump in disrupt cyno. cyno ship is now free to move to the next jump point. ---
**Author:** ![Gerard\_Amatin](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/gerard_amatin/32/481361_2.png) [@Gerard\_Amatin](https://forums.eveonline.com/u/Gerard_Amatin)\ **Post date:** [September 27, 2026, 6:54am UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/10 "2026-09-27T06:54:37Z")
That’s a good point. If it suppresses a cyno it shouldn’t let the cyno ship go free early. ---
**Author:** ![Askanher\_Krividus](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/askanher_krividus/32/512030_2.png) [@Askanher\_Krividus](https://forums.eveonline.com/u/Askanher_Krividus)\ **Post date:** [September 28, 2026, 8:49am UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/11 "2026-09-28T08:49:49Z")
That is a good point, but I think there is a simpler way to prevent that abuse. If a Cynosural Disruptor shuts down an active cyno early, the cyno ship should still keep the original cyno commitment timer. For example, if the cyno would normally remain active for 10 minutes and it is disrupted after 2 minutes, the field disappears, but that ship cannot activate another cyno for the remaining 8 minutes. Alternatively, CCP could simply apply a fixed reactivation cooldown after a cyno is forcibly disrupted. That way the module can still shut down an enemy cyno, but it cannot be used as a shortcut to move cyno ships faster between jump points. The cyno disappears, but the ship does not immediately become free to light another one. ---
**Author:** ![Syzygium](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/syzygium/32/510263_2.png) [@Syzygium](https://forums.eveonline.com/u/Syzygium)\ **Post date:** [September 28, 2026, 9:29am UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/12 "2026-09-28T09:29:48Z")
A BlackOps gang is already on grid and firing on you before you reacted, locked the cynoship, got into 5km range and activated the module. ---
**Author:** ![Jayden\_Thomas](https://sea1.discourse-cdn.com/eveonline/user_avatar/forums.eveonline.com/jayden_thomas/32/407936_2.png) [@Jayden\_Thomas](https://forums.eveonline.com/u/Jayden_Thomas)\ **Post date:** [October 4, 2026, 1:26am UTC](https://forums.eveonline.com/t/ship-mounted-cynosural-disruptor-active-counterplay-to-cynos/518815/13 "2026-10-04T01:26:57Z")
Extra slots on ships are already hard to spare for a specific “cyno jamming” module like this. An easier solution would be to just put an activation cost on a cyno module with a spool up timer, and give the opposing team time to neut it out before the timer is up.