Fix Null/Low Risk–Reward Inversion

EVE Technology and Research Center Player Features & Ideas
1

[Suggestion] Fix Null/Low Risk–Reward Inversion: Cyno Counterplay + Fog-of-War Intel + Op-Window Defensive Arrays

  1. Problems we’re trying to solve

Right now, lowsec and nullsec often feel less like “dangerous space” and more like “space with CCTV + instant police response.” Two mechanics reinforce each other:

A) Near-perfect, free, real-time intel

Instant Local rosters (plus other system-level intel) mean intrusions are detected immediately.

Defenders can avoid risk with passive attention rather than active presence.

B) Near-instant force projection

Cynos allow defenders to convert “spotted” into “overwhelmed” too quickly.

Small-gang and independent activity collapses because many engagements become structurally unwinnable or non-interactive.

Combined outcome

Roaming declines (not fear of fights — fear of inevitability).

Lowsec trends from “wild west” to “police state.”

Nullsec becomes “safe-ish and profitable” for incumbents, encouraging stagnation and space hoarding.

This encourages rent-seeking behavior: groups can monetize control over far more space than they actively use.

This isn’t about “nerf null” or “buff hunters.” It’s about restoring the sandbox loop: risk scales with reward, and fights are contestable rather than instant doom.

  1. Design goals

Restore counterplay time

Escalation should be contestable: windows to react, reposition, and kill the enabling mechanism.

Restore geography

Distance and fixed terrain (gates/chokepoints) should matter again.

Scale intel with security status

Highsec = most free intel → Lowsec = less → Nullsec = even less → Wormholes = none.

Make overreach expensive

Big groups can still build safe-ish cores, but holding vast unused space should require attention and presence.

Preserve big fights

Large battles remain possible, but require visible commitment and multiple vulnerable points (not “one cyno, instant delete”).

  1. Proposal (high level)

3.1 Cyno / force projection changes

Add cyno spool-up time (example baseline: 60s). Cynos become a commitment window.

Per-cyno jump throughput throttle (example: 15–30s delay between jumpers per cyno).

Large escalations still happen by using multiple cynos on grid (more commitment, more failure points).

Capitals can use normal gates to restore geography and interdiction.

3.2 Intel changes (security-tier “fog of war”)

Highsec: Local unchanged (full roster).

Lowsec: Local shows count only (no identities).

Nullsec: Local shows count only + delayed/pulsed (example end-state: 10-minute ticks).

Wormholes: unchanged (no free roster unless you speak).

Important reality check: wormholes are harsher than null because they also have unstable connectivity, yet people live there fine. Null has fixed, defendable gate terrain — so “reduced Local makes null impossible” doesn’t really hold up.

  1. Avoiding “Blackout PTSD”: incremental rollout (~12 months)

This scale of change must be incremental to avoid shock and to allow tuning with real telemetry.

Phase 0: publish end-state + gather baseline metrics.

Phase 1–2: start in lowsec (modest cyno friction → lowsec count-only Local).

Phase 3–4: transition null (count-only → pulsed → final tick cadence; cyno friction ramps to target).

  1. Defensive “op-window” tools (null-only, sov-owner only)

If intel becomes less perfect, defenders need temporary, fightable tools to buy safety during specific operations (mining/ratting/move ops) without restoring permanent free wallhack intel.

Op-Window Defensive Arrays (shared rules):

Nullsec only; only deployable in sovereignty systems your alliance owns

10-minute online timer, 60-minute duration, unrecoverable

~200k EHP, no damage cap (shootable objective)

Warpable beacon visible in-system

Visible on the star map for everyone, including while anchoring, with remaining time

(using them should “light a flare”: you buy security but advertise activity and create content)

Gate Tripwire Beacon

Anchors near a stargate; alerts on jumps into system: gate + time + count (+ optional hull class bands).

Filament Redirect Beacon

Filaments can’t target specific systems, so this doesn’t block planned ops.

Any incoming filament result that would land in-system gets redirected (rerolled) elsewhere.

Cyno Interference Array

Makes cynos contestable rather than impossible.

While active: 2× cyno spool-up time, and a warning ping when any cyno begins spooling (including covert).

Cooldowns and limits prevent 24/7 “safety services.”

  1. What success looks like

Lowsec gets its “wild west” back: more roaming, fewer instant police-state hotdrops.

Null becomes a gradient: safer cores possible, but borders porous and unused space contestable.

Less rent-seeking pressure: fewer “permission/rent empires,” more footholds and friction.

More regular PvP: fewer instant deletions, more contested escalation and on-grid objectives.

Big fights still happen, but require visible commitment across multiple points.

  1. The big concern: “this will hurt incumbents”

Yes. It will cost groups optimized around the current low/null ecosystem. That’s unavoidable if the goal is to fix the underlying physics. That’s why the rollout is incremental, and why defensive arrays exist as a temporary, contestable replacement for some lost passive certainty.

2

Fix your text and i might read it. Can’t promise though. But maybe someone else will read it then.

3

Risk is defined by the challenge provided by the system, not the challenge provided by the players.

Why are so many failbears coming to forums recently, whining about how the game needs to be changed because they’re bad at it? As soon as one cryfest gets closed, another is opened to replace it with the same complaints.

Serisouly, bro thinks the current system is near-instant force projection? :rofl: LOL, force projection’s been nerfed into oblivion except for short range. Either they have a fleet on standby within a short distance, they’re willing to take a big hit on jump fatigue to protect what you’re shooting, or you fail at taking targets down so badly that they’re able to coordinate one on the fly. Those are the only scenarios to your complaint of instant force projection.

4

Guy wants “active presence” and complains about “active presence” that makes low sec and null sec “safe”. Guy wants less “rent empires” but suggests things that make “rent empires” instead of small groups claiming space even more likely. You can’t make this up.

5

Null/low, it’s the ghetto, you either love it, or don’t.

6

You’re right that force projection has been nerfed over the years — it went from super broken to still very broken in the specific way that matters for small-gang interaction.

  1. Acknowledge the nerfs (agree on history).

Yes: projection used to be insane. The problem is that the remaining “short-range inevitability” is still enough to suppress roaming and independent play.

  1. Jump fatigue doesn’t address the first-drop problem.

Jump fatigue mainly limits repeated long-distance chaining by the same ships. It doesn’t change the fact that the first response to a roaming gang / PvE target can still be fast enough to be functionally inevitable. So it reduced cross-map projection, but it doesn’t fix “spotted → overwhelmed” inside a region/local cluster.

  1. “Failbear” is not an argument.

Calling people failbears is just ad hominem. If the mechanics create low marginal risk for incumbents and hard counters for smaller groups, that’s a design problem whether or not someone likes it.

  1. This is about relative risk–reward in sov null.

My point isn’t “null should be safe” or “delete escalation.” It’s that sov null currently lets large groups remove their own marginal risk too efficiently (intel certainty + rapid response), while also giving them near-hard counters versus smaller groups. That’s why the proposal focuses on reaction windows (cyno spool-up + per-cyno throughput limits) and less perfect passive intel (delayed/anonymous signals), so small groups get time-to-play while large groups can still keep the space they actually use relatively safe.