Player Features and Ideas Discussion

That solution provides even more intel. They already stated they don't like local as it sits now. It also makes cloakies basically super powered

read the whole thing +1

I'm not concerned with the back story of workers in station and such.

What I do wish to point out is that the above is intel.

If local chat works like other delayed chats, if I jump in and see Bob in local, I know for a fact he is docked. That tells me something....something potentially of value. And it is something of value I didn't have to do a damn thing to get other than jump into the system and glance at local.

Good OP. I had a similair idea about the Dscan, I like it. I hope CCP takes note to this thread.

i did read it and fully agree with many of the points. At the end of the day the redesign would require the following intel mechanics:
- some form of radar (as you described, limited range proximity sensor, some games call it passive sensors)
- indirect sensors, probes, already done and everybody is happy
- long range radar (our good old dscan, some games call it active sensors)

active sensors usually come with a penalty. You could imagine if you using them others could see you with passive sensors, even though you are out of their passive sensor range.

this doesn't even discuss how you would display those sensors. You can't simply create a radar in eve since you can't expect that most clients can render all brackets twice in large fights. And in large fights you have basically everything on grid what is in system, which is the worst case scenario for the renderer.


this is just an example of a high level concept of the intel tools and could be implemented without even touching local. Now if this ground work is done you could think about how communication could work. Proximity chats (public channel with people on grid, delayed mode) and so on and on. My point simple was CCP has to create a huge foundation before they can even think of modifying how local works. In technical terms there are at a point where they can't refactor the system, they have to redesign it. If they don't have the big picture the task its doomed to fail since incremental patches are not enough to "fix" local/cloaking/dscan/you name it.

- The D-scan requires maximum range to be available as numbers, not just a slider -

This is because I need to enter many figures around 10,000 to 40,000 and I need to be able to distinguish a wreck at 10,000 vs a player at 20,000 when seeking combat over a multi room signature. Its unlikely that a slider will have the required fidelity.

The "radar or passive radar" that you are referring to is the dscan. Remember, the concept of radar, will just be an auto refreshing dscan. No other types of radar. Just make our dscan automated and add ranges to the ships it sees on d scan.

Cloakies could still have their d-scan, but not a ℅ nerf, just have it so all they can detect is that there is a shjip in space, perhaps its range too like you said, but the more refined checks unable to return info until uncloaked.

If a cloakie is 'actively pinging' dscan, have it show up, not range or anything, just that its 'there' maybe have a column specifically to say if a signal is actively running d-scan?

Over all I love the flavour and feel for this suggestion. Makes dscan more useful, and keeps in with the universe. I also like the idea that maybe introducing new skills for it, or existing ones, maybe skill for d-scan range, and also accuracy? Lower skills can decipher hull type; battleship, cruiser etc, higher skill showing the actual ship class?

Another suggestion would be returning scans with a profile image of the ship, the player would then need to cross check with the ISIS to figure out which ship it might be? Would be cool to add at longer ranges, not being able to tell if a hull is T1 or T2?