EVE General Discussion

1) delayed local
2) make directional scanner alert when a ship is in range. filters per d-scan range and ship allegiance; friendly ships bypass alert by derived standings if you set so in filters.

Basic filter examples:
High - shows only hostiles and negative standings by d-scan red alert
Null - shows all non-blues as red alert.
Null incoming - shows all non-blues by red alert, but you have set range to 50000 km so you can expect someone on grid soon.

Dscan doesn't include cloaked ships, so this is a no.

Remove Killmails, delay local by 45 to 120 seconds depending on sec stats.

There has been so many threads about local it is no longer funny.

It all comes down to people don't want local cause it allows someone to hide.
That is both prey and hunter.

People want local to stay because without the information, game play will slow down to much as people have to scan every system.

Neither option is except-able which means the game mechanics have to be changed and nobody can agree on what they should be.

So at the end of the day nothing is done and a thread will pop up every now and again about it.

Just like cloaking and the all of threads about it.

Crazy thought, and I don't know if this has been explicitly mentioned before.

But what if instead of local, the lowest level of chat you could get to was constellation?

that channel already exists, although most people close it down.

1. It shouldn't affect chat too much, as most people are either on comms, or chatting in private channels (corp etc).
2. It still gives intel. it just isn't "perfect" anymore. You would know if a neutral is in the general area, but not necessarily which system.

Seems honestly like it would be an interesting comprimise.

It's not a compromise at all. Instead of a character in a cloaked ship causing all PVE in a system to halt, you'll have that same single character in a cloaked ship causing all PVE in an entire constellation to halt.

No. no active alerts.

The great thing about the current system is that for the most part you have to be WATCHING local. The "blinking local" thing CCP just added (while VERY helpful for a guy like me) was a mistake, an anti-pvp mistake in a pvp game.

As much as I would love to see local removed, there is nothing "wrong" with it in relation to people freaking out over covert ops ships in the system. People are calling for locals removal in this particular situation, because:

Despite the fact that cannot prove if someone is AFK...
Despite the fact that cloaked ships cannot do anything...
Despite the fact if someone WAS AFK they cannot see anything...

They still wet their pants when then cannot find a ship on scan.

SO - since they insist on trying to "fix" something that is not broken beyond their own lack of will and risk taking, why not remove local so they don't get scared.


That - and local should be removed because i does nothing but make you feel safe.

I'm just going to call bs on this one. I, for one, will keep right on ratting, instead of watching local I'll watch a d-scan, be in a fleet with friends, if not ratting right with them in pvp capable ships that have a point and cloak fitted. Alliances will adapt by having sentries on strategic gates to watch activities, and life will go on, and to everyone who chooses to stay the profits will go up because we have less competition.

Local is a problem, but it's a problem with a perfectly viable solution already. I can understand why it exists and it is even justified in immersion by the fact the gates know who and what ships they just delivered from another star system. Now people have a problem with a solution to the problem of instant intel, because it's not 100% accurate. People don't know how to deal with a single unknown thrown into the mix and they want to fix the solution and keep the problem.

Well, this is a bit more like it. A discussion about local and intel gathering as opposed to AFK cloaking.

Personally, I don't think Local should be an intel tool at all. Not even in high sec. Make it show only through participation, ala wormhole. Then, work on replacement intel tools.

Our real question should be "if local is removed, how would we replace it?"

I think we need a better sort of system scanner. Maybe something that displays where every active grid is and gives you a rough idea of the population within that grid. Something that picks up "warp signatures" maybe. Too much dependance on local and DScan. Both of those things should be removed, I feel, and merged into one system. Possibly something that overlaps with probe usage, even.

The core is that if local/intel is "fixed", then AFK cloaking just goes away by itself.

Doubt it'll get looked at any time soon, though.