Player Features and Ideas Discussion

I agree that there should be some way to stop cynos from being lit on grid, and I have supported this as a role for the tech 2, tier 2 BC. They are the only pre crucible hull that does NOT have a tech 2 variant, witht he exception of capitals and rookie ships. They would be a little like dictors I imagine, with a healthy amount of tank, with weapons coming as an afterthought. This gives the gang fielding it a little bit more notice when they are going to get another gang dropped on them, or if they need to start getting their own capitals out of the fight so they can withdraw.

Lit your own cyno in another grid.

It would not stop hotdropping, but at last it would delay it.

I like the idea. A T2 BC is ~200m and it looks fair enough.

sounds like an intresting idea.

yes and no.

while i like the concept, it would be easy to perma run said module provided you field what is necessary.
you take said cruiser, provided one cap is on field, said cap could feed the cruiser in fuel via hangar and rep him up, thus preventing on grid cyno potentially for a very long time, maybe enought to prevent ennemy cyno to light is own if pointed (cannot go offgrid to bring reinforcement) or destroyed.

and by the time another cyno up, fleet is dead, while actually they had means to counter.

the current issue with bridges is that many ppl misuse it only playing the "hotdrop 20 BS to kill a cruiser" thing, and nothing more, wich is boring and lame.

plus this will be a "all or nothing result" jump are pretty fast, so the odd you manage to activate the jammer before cyno light and fleet on field are really low.

so either you still end up with overwhelming fleet or you just kill the bait with nothing more

Sorry to rain on the general parade here, but I feel the OP is skipping past a few crucial details, in what is really a larger more complex issue.

Hot Dropping: Bridging is intended to bypass reinforced blockades and travel time. Here, it has been fine tuned to avoid advertising the presence of a fleet to the free intel tool as well by delaying the easily recognizable population spike till the last possible moment. The intention is to deny the warning local provides, although it still reports the presence of the cyno boat enough to be associated with AFK Cloaking instead.
Quite simply, while PvE pilots would never resume regular activities with a hostile fleet present, they are sometimes willing to gamble over whether a cloaked vessel represents that level of threat at a given time.

---

The OP presents an idea that would effectively remove the counter that was player created.
Noone seriously is worried over cloaked vessels, as they are balanced with low combat abilities in exchange for this would-be stealth.
No, people are more worried about is that the vessel may be allowing a fleet to bypass local chat's intel.

That population spike is a dead giveaway that a large number of ships is coming, and local warns everyone the moment they enter the system. Short of hot dropping, it is simple to stay aligned and insta warp to a safe the moment you see such a pop spike. This allows anyone wanting to avoid a fleet the ability to do so.

I do not suggest that fleets should be fed free kill mails, do not assume that. I AM suggesting that it should take more effort than casually glancing at local chat to be warned of this.

If you don't want to need teamwork and effort to succeed, go where it is not needed. Everywhere local warns people like this, however, I notice it is also not needed.

Noone is missing a point.

You are complaining about something that was player created as a counter measure to the intel provided by Local Chat.

If you ignore this source and cause for it, you won't get a realistic solution either. You will just create something that gets exploited, by either making the original problem worse, or snowballing into something entirely unforeseen.

Only by removing the cause of a problem is it eliminated.

This would be a nice addition

I think Mary Annabelle caught on to it.

This is not to create fights, or even balance fights. It is a means to avoid them.

A cyno pilot who knows he cannot light up won't bother. The whole point of a hot drop is to catch someone who would otherwise not stick around to fight.
Having established they don't want a fight, and this keeping it firmly up to them, it won't happen.

I think the exact opposite . . . how many roams dont take place because everyone fears the hot drop? how many fleets arent engaged because "it feels like bait cyno"

I suggest this module have a 1 minute cycle timer with no early deactivation. This module would also disallow warp and would carry with it the same propulsion mod penalties as the warp disruption field generator.

Basically it would be saying "I dont want to be hot dropped, but I'm committing to this fight"

How many well intentioned ideas end up being misused?

I appreciate you would want this to promote more PvP, but the fact remains that it could be used very effectively to avoid it.
And let there be no doubt strong motivation exists for some pilots to do exactly that.

It is not enough that it might do some good occasionally.

How would you balance out those who would seek to avoid risk, above and beyond what is intended by the game's design?
For this undoubtedly creates such opportunities.