Math.random (or w/e your chosen programing language uses) more or less makes that argument moot. It would be easy enough for someone who knew what they were doing to scrape their own dscan usage, and then program those “patterns” into their script. I’m sure bots already are using it, because it’s really not that hard to code. Building the actual bot would be far more difficult.
And that’s the thing, denying auto dscan to the normal player base does nothing against bots. As I said before, a basic auto hotkey script is a single line of code, and if you want to get fancy with it, you’re talking like less than 5.
You’re assuming that information isn’t already being sent to the client. Destiny alleged that it might be.
But even if it isn’t, how many people are actually using dscan? Would that change that much even with auto dscan mechanic, especially considering EVE’s session change mechanics would by default reset auto dscan every time the player jumped a system or docked / undocked? I find that doubtful.
The proposed auto dscan would still require the player to activate it (because not being able to freeze dscan so you can actually read fleet numbers / ships is a non-starter.) So you’re talking about a fraction of the total.
People in highsec, by in large, don’t use dscan.
The op literally talks about it.
If players aren’t focused on constantly hitting the dscan hotkey, gameplay elements can be designed around other facets of the game to make the experience more engaging. There’s less room for the developers to move around in that space when players feel the need to keep kitting the same key every few seconds.
Agreed, an audible chime would be a welcome addition, even if ccp bows to the “no auto dscan” crowd. Bonus points for making use of that radar ping sfx from the 80’s - 90’s movies.