Player Features and Ideas Discussion

First, let's specify that this is not simply about scanning alone.

It would affect other areas quite plainly.

This is my expectation of a trade off for self-repeating sensors, or d-scan as we often refer to it.

It would introduce a new toggle-based control option for d-scan, in addition to the single use scan button.
In this context, toggle means to change states in a persistent manner, rather than triggering for a one time event.
Specifically, it means having the sensors automatically rescan based on the existing settings for the d-scan.

This is to define how long it takes repeating sensors to automatically rescan, rather than needing to press the scan button each time.

The consideration that this is automated should be included, I believe, as this diminishes player error at the point of forgetting to trigger sensors to stay updated.
For that reason, I would recommend that existing d-scan options for manual triggering be left alone, to reward those willing to make the extra effort rather than have it done for them.
(similar to the logic that auto-pilot was less efficient in moving ships)

Basic Details:
Next, let's presume that it takes X amount of time to scan an area of space, comparable to the grid we see parsed in our overview of local contacts.

Now, we can use D-scan to control the area of space we scan in two ways.
We can use a cone, to limit scanning to one direction.
We can select the range, to set the distance and possibly signal strength.

At one end, we have simple on-grid awareness, which is instantaneous and constantly updated.
For each grid equivalent we add to this, sensor cycle time should increase.
The more grids we try to scan, the longer it should take to cycle.

Now, lets presume that we are scanning a full sphere, omnidirectional.
Add to this, we are setting the maximum possible range.
(I personally think each ship should have different range capabilities, but that may be another topic for another place)

The settings I just described should result in the longest possible cycle time for the sensors, to again repeat the task.

What amounts to a balance question, is what should be the time for this maximum scan?

1 minute? Perhaps 2?

I did not expect the term 'toggle' to be seen as something unclear.

In this context, it means to change states in a persistent manner, rather than triggering for a one time event.
Specifically, it means having the sensors automatically rescan based on the existing settings for the d-scan.

This is to define how long it takes repeating sensors to automatically rescan, rather than needing to press the scan button each time.

The consideration that this is automated should be included, I believe, as this diminishes player error at the point of forgetting to trigger sensors to stay updated.
For that reason, I would recommend that existing d-scan options for manual triggering be left alone, to reward those willing to make the extra effort rather than have it done for them.
(similar to the logic that auto-pilot was less efficient in moving ships)

Your point is well taken.

I apologize for any confusion, I sometimes have trouble explaining ideas because of simple details like that.
Switching gears between engineer and spokesman is a bit rough for me, lol.

Those three words make this a bad idea. Player error is the cause of a vast majority of the content in this game.

I'm sure you've heard of the Battle of Asakai, it's only one of the largest battles in online gaming history. Remember what caused that? Player error, when a Titan pilot clicked jump instead of bridge. I could go on and on, providing examples of how player error is good for the game, if not necessarily for the player who made the error.

True enough its oft repeated but has there ever been a genuinely convincing argument for or against it? People on both sides tend to wildly misrepresent clicking as 'eve is hard' or think they should have magic sensors that make everything warpable and auto-target ships before they land.

In the end you're either paying attention to your D-Scan or not, is there any extra value in having people spam-click it?

This is the most important bit. Automating d-scan might well make people more complacent. In my mind, forcing people to spam click is a bad game mechanic. The player should be able to set the scanning interval, up to the current max. It then scans automatically when the window is active (not closed/minimized, nothing on top of it, etc).

Thank you for being patient

Grabbing just this section, for now, as it offered what I believe to be good questions to clarify:

The arc of the scan, as comparing a full omnidirectional sphere to a limited cone, is not the exclusive factor in this.

If you have a 180 degree angle scan, that is basically everything on one side of the ship, it can scan farther in the same amount of time than a full 360 degree scan could.

I am using the local grid like a unit of measurement here, trying to keep things relatable.
It takes X amount of time to scan 1,000 grids, regardless of how they are arranged.
If you only look in one direction, 1,000 grids extends much farther away than if you had them in every direction.

The cycle time on a maximum scan, maximum range combined with full sphere scanning, should define the longest possible cycle time.
The scanning time should scale based on the amount of space being scanned, down from this number in a linear manner.
(If you scan 3 grids instead of 6, it takes half the time)

As to the sensors reacting to a specific item, I am not pushing for that right now.
I am thinking it is getting ahead of ourselves, and may be too far in automating things.

Btw, grids are not (why the hell do we call them grids anyway) some sort of static cubic area defined by certain distances. Grids are dynamically generated and altered based on the behaviors and locations of objects and players, along with when and where they moved.

Grids can be stretched out to thousands of kilometers, into weird shapes, or manipulated into tiny grids less than 50 km across.

As such they are not a good measurement for defining distances. It would be better to use the normal AU measurement when talking about scanning distance or scanned volume.

For those interested, here's a guide on just how ****** up grids can get and how they are generated/manipulated.

http://go-dl.eve-files.com/media/0912/gridfumanual2.pdf

I'm pretty sure as a sentient human being I can focus on whatever I like. I'm pretty sure CCP is aware that I am sentient. I'd also like to point out you posted this on a forum for discussion. I'm discussing my opinion.

NO because it will be a botting tool.

Also, link where CCP has asked that others not focus on possible botting buffs.