These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Player Features and Ideas Discussion

 
  • Topic is locked indefinitely.
 

Change Local based on System Sec Status
Author
Previous Topic Next Topic
Tidurious
Blatant Alt Corp
#1 - 2012-02-06 19:56:27 UTC
There's a lot of complaining about local in null/low sec being too powerful, and I agree. However, there are also a lot of threads about removing local completely, and I think that gives a little too much advantage to the hunter/killer gang out there and puts the nullsec ratters/miners at a disadvantage if they're not part of a large fleet/corporation/alliance.

The change I propose is this:
In hisec, local should stay the same as it is now. No changes are needed to local in hisec.

In lowsec, the transmission quality from the incoming pilot scanners is reduced. Therefore, local is delayed. In 0.4, it is delayed 1 minute (you don't show up until 1 minute after you enter the system) and in 0.1it is delayed 4 minutes, with each 0.1 of sec status causing another minute of delay. However - even if you cannot see the pilot information yet (timer has not expired), you can still see the NUMBER of pilots in system in real-time.

In nullsec, you should be able to see how many pilots are in system, in real-time. However, you cannot see any information about these pilots unless they speak in local. So, you know that a pilot has entered the system, but you know NOTHING about them. It could be a 2 week old idiot in a reaper, it could be someone in a pod, it could be a jump freighter pilot. All you know is how many pilots are in system.


I think this would allow the roaming gangs to remain more anonymous, because it's a dead give-away when 7 guys from the same corp jump into system all at once. However, it also lets the PvE players in nullsec have a tiny bit of warning that SOMEONE is in system, but they don't know who, if they are related, how old the pilots are, etc.

What do y'all think?
Nikk Narrel
Moonlit Bonsai
#2 - 2012-02-06 23:03:14 UTC
Tidurious wrote:
There's a lot of complaining about local in null/low sec being too powerful, and I agree. However, there are also a lot of threads about removing local completely, and I think that gives a little too much advantage to the hunter/killer gang out there and puts the nullsec ratters/miners at a disadvantage if they're not part of a large fleet/corporation/alliance.

The change I propose is this:
In hisec, local should stay the same as it is now. No changes are needed to local in hisec.

In lowsec, the transmission quality from the incoming pilot scanners is reduced. Therefore, local is delayed. In 0.4, it is delayed 1 minute (you don't show up until 1 minute after you enter the system) and in 0.1it is delayed 4 minutes, with each 0.1 of sec status causing another minute of delay. However - even if you cannot see the pilot information yet (timer has not expired), you can still see the NUMBER of pilots in system in real-time.

In nullsec, you should be able to see how many pilots are in system, in real-time. However, you cannot see any information about these pilots unless they speak in local. So, you know that a pilot has entered the system, but you know NOTHING about them. It could be a 2 week old idiot in a reaper, it could be someone in a pod, it could be a jump freighter pilot. All you know is how many pilots are in system.


I think this would allow the roaming gangs to remain more anonymous, because it's a dead give-away when 7 guys from the same corp jump into system all at once. However, it also lets the PvE players in nullsec have a tiny bit of warning that SOMEONE is in system, but they don't know who, if they are related, how old the pilots are, etc.

What do y'all think?

I think you have people in lowsec spamming the D-scan, worried about being attacked with no warning.

Automate D-Scan so that it self repeats often enough for people to not be too paranoid about mining or ratting, or risk losing these in low sec. If they can't see who is coming for them, they might as well go do wormholes with their better ores and rat salvage.

I also happen to think with the sonar analogy in naval warfare, someone d-scanning often enough should be detectable because they are sending out energy that can be traced back to them, like a direction indicator.

Upgrading Local to Eliminate All AFK Influence What if Local Chat changed, Hunting the Cloaked...
Gevlin
Pator Tech School
Minmatar Republic
#3 - 2012-02-06 23:11:42 UTC
this also needs to be for the roamer. that he does not see who is in system for 1 minute when he jump in otherwise you have just made it a roamers dream and all you resource gatherers will stay in high sec in NPC corps.


Okay scout you jump in you see a number of people start scanning them down...


I would though no eve put the number of people showing.

Someday I will have the time to play. For now it is mining afk in High sec. In Cheap ships
Tidurious
Blatant Alt Corp
#4 - 2012-02-06 23:15:46 UTC
Gevlin wrote:
this also needs to be for the roamer. that he does not see who is in system for 1 minute when he jump in otherwise you have just made it a roamers dream and all you resource gatherers will stay in high sec in NPC corps.


Okay scout you jump in you see a number of people start scanning them down...


I would though no eve put the number of people showing.


Sir, I would request that, prior to posting in threads, you train English to at least level III, if not IV or V (best option). Your post makes no sense, especially your sentence "I would though no eve put the number of people's showing".

While I understand that English may not be your first language, please remember that these are English forums and that no matter what it says, google translator does not actually translate into understandable English.

I believe English 5 takes about 38 days with the right attributes, please begin training immediately.
Axium Cog
Grand Solar Trinity
Grand Inquisitors Federation
#5 - 2012-02-06 23:47:59 UTC
While i see where your coming form and agree on alot of points, i have a different approach for solving it.

Ive lived in W-space for a very long time. D-Scanning for probes is a necessity. Dont and thats when theyll drop probes. Local here is speak only. You only show up when you talk. Nullsec shouldnt be to that level, after all they have gates.
I dont think lowsec needs a delay. There is faction/DED presence there so it makes sense lore-wise for there to be reliable communications.

Nullsec however.
If a miner isnt a part of a corp or alliance that owns the space hes ratting in, then he should have to be paranoid and spamming dscan.

Id like to see local require a communications array sovereignty structure that provides local numbers and communications for anyone blue to that alliance.

Id like to see ewar ships with a codebreaker module be able to tap into these communications arrays. Perhaps first cycle gets the number in local, second cycle reveals who is in local, and a third and subsequent cycles reveals the last 10 communications to go through local.

As a counter to this, provide a smartbomb-like signal jammer that has a chance, kinda like lockbreaker bombs with targeting, to remove someone from local from local for 5 seconds.

either way, CCP has said local was never intended to be an intel tool, most people agree. something has to give eventually.
Soldarius
Dreddit
Test Alliance Please Ignore
#6 - 2012-02-07 02:01:36 UTC
Last time I checked, local already instantly tells you the person is there. So I don't see the difference. Their ship type is only shown when you either see them on grid or catch them on d-scan.

For the sake of argument, I'm assumking what you want is different levels of "intel" available from local channel based on security class of the system, with an option in sovereign nulsec for an intel improvement.

I'm all for it. This would make npc nulsec just like w-space. Perhaps you could have access to npc sov instant local with sufficient standinds with the npcs. Otherwise, delayed just like w-space.

http://youtu.be/YVkUvmDQ3HY
Tidurious
Blatant Alt Corp
#7 - 2012-02-07 04:06:02 UTC
Soldarius - with the current local, you know that someone is there, you also know WHO they are, and what corp they belong to, etc. If you have dual screens, it's easy to quickly look them up on BC and the like, etc.

With my proposal, you would know SOMEONE is there (unlike WH space, when you have no idea) but not even who they are, unless they chat in local. I think this would reduce the "free intel" a bit while maintaining SOME element of general knowledge about the population of the system. I don't care about local improvement in soverign systems at all; I'm just talking about null in general.