EVE General Discussion

Local is the perfect intel tool for bots. There are systems where half the people log when I jump in. On the other hand CCP could probably use our alliance as a Bot detector by now. So don't forget Highsec and remove it there as well

And?

At the least, access to Local intel in sov null should come at a cost.
However that would come with loud yells of Malcanis' Law, stating larger entities can better afford it.

Explain to me, what rationale is there that Player Sov, as player owneď and operated, should have free Local?

(inb4 it protects the weak from the strong)

The reality of why local does exist is for the facilitation of finding and escaping in a PvP centric gaming world. Without the facilitation of aggressor/aggressed it will be a very bland game and much more cat and moue much akin to a Silent Hunter submarine simulator in its entirety looking for kills.

The Lore guys are right it is an IFF issue that we must log ourselves and our ships masses and types, akin to an Aircraft carriers catapults needing to dial in the ship type to fling it across the required space with the right energy levels.

That being said delaying local in some areas and giving an advantage to different areas and players would be interesting. Id even suggest using a variance like the 1.08 sig/sensor strength formula to give shorter or longer delays. Making the arrays basically be one tick system scanners. Then tbh Id have them be forced to be anchored on grid to the gates, likely within 100-150kms, to work effectively.

Sov null gets the arrays, NPC null gets a short delayed local for everyone as does low sec. And High is left as it is.

Honestly my only concern is that Sov null needs to not get much safer through this and there must be effective counterplay there.

I also like the WH delay idea both ways tbh. Lore could be something like subspace signals and recalibrations take time to be redone after being ripped through a WH. Limiting dscan range on a WH to K-space jump would be interesting too especially if K-space local takes a while to update after a jump. Again I would use the 1.08 + mass for the update. The more mass passing through on a jump the faster it would update. So a single ship is the slowest, a large fleet is the shortest.

I try to tell people that, I'm IN on of those largets alliances that can drop Capital Ships on anyhting that decides to roam though our space. but you can't tell people that, because they automatically assume that anyone who supports something that exists is somehow selfishly supporting a status quo they benefit from. Because they think that, they can't see the WARNINGS people are trying to give them.

In short, it's DOMINION SOV all over again. I love telling this story because it's a cuationary tale not just for players of EVE Online, but for people in general.

When CCP announced and described the Dominion Sov system and stated it's goal as "oppening up null to smaller groups and making space more dynamic", there was instant opposition to it. Much of that opposition came from people who were members of Goonswarm (but they weren't the only ones).

People who hate goons saw Goons telling people that Dominion Sov would be a mistake because those high hit point structures would not cause smaller groups to come, but rather it would entice people to join ever larger groups to make the 'sov grind' more bearable (in much the same way the old POS based sov system Dominion was supposed to replace did). But the anti-goon folks just weren't listening, they didn't trust Goons so anyhting a Goon said must be a lie.

So CCP implemented Dominion Sov, A game that already had Coalitions developed MEGA-COALITIONS, lots and lots of people blued each other (because being blue and easily grinding down millions of hit points is less annoying than not being blue), and the Goons that no one trusted spent half a Decade punishing people for not listening to them when they were telling the turth.



Well, it's like that with local in null. When we try to tell people that getting rid of local in null will make null LESS hospitible to small groups than it is now (in the way that C5/C6 woromholes are, only worse), they don't listen. They think it will be great.

I actually want CCP to get rid of local in null for a month, because it's like parents and children. Anyone who has ever been a parent knows that you can tell your kid all day about something, but at some point the only way to break through their know-it-all stubbornness and ignorance is to SHOW them their folly.

I think removing local would certainly make the argument low and null sec space is far more dangerous. Currently High Sec is more dangerous with the ganking, alt support etc.

Local in low and null just means people are "intelled" making this BS argument about risk vs reward mute.

So your answer to my question is:
-"Its there cos its always been there".

Now that, is a stupid piece of crap argument.

So your answer is now:
-"Its there cos of Lore"

Thats an even more stupid and crap argument than the previous one.

What part of Lore specifically makes it immutable that Player Sov has free Local intel?

*delete* Misread original post.

The greatest lie is that player null isn't "owned" by concord... who do you pay your sov bills too? What happens if you don't pay your 'rent' to concord?

They are the ones who maintain local through the gates.

All riiiight! Surely if you just keep insulting us hi-sec types you will convince us to come down to lo-sec and join you in the never-ending soap opera of PVP combat.