Pages: [1] :: one page |
Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Bronson Hughes
The Knights of the Blessed Mother of Acceleration
308
|
Posted - 2014.08.26 15:45:00 -
[1] - Quote
Having (almost) everyone show up in Local in non-WH space is not only fine (to some extent), it fits with the lore. Each system has stargates, and these stargates control who can enter and leave a system, and they keep a record of who's in system. This is the "Traffic Control" we notice when we first try to go into a system after downtime.
But here's the thing. Traffic Control has (or should have) no way of knowing if a pilot has left system via means other than a stargate (Wormhole, Jump Drive, or Jump Bridge.)
So here's an idea. Keep Local largely as-is but pilots will not become visible in Local until they:
1. Enter a system via stargate. 2. Dock at a station. 3. Say something in Local Chat.
And here's the kicker: Pilots won't disappear from their previous Local channel until they show up in a new one.
Given the lack of stargates and stations in WH-space, this would leave Local in WH-space exactly as it is now.
Local in hisec would remain largely as it is now because the vast majority of traffic into or out of hisec is via stargate, but the presence of hisec wormholes and the ability to jump out of hisec would change it's dynamic slightly.
But Local in losec and nullsec would become more...dynamic. BlOps bridging would become more covert (only the covert cyno pilot would show up in local, assuming they weren't left there by another BlOps bridge). Non-hotdropped capitals would gain a certain element of surprise, assuming they didn't dock after jumping in. Wormholes would become far more useful for transit between points in K-space. And (I feel unfortunately), it would remove supercap pilots from Local entirely unless they talked in Local.
Having said all of that, I'm not a strong supporter of changing how Local works. I think it's largely fine just how it is. This is just an idea I'm pitching in to see what folks think.
Thoughts? Reading Comprehension: a skill so important it deserves it's own skillbook.
I want to create content, not become content. |

w3ak3stl1nk
Hedion University
85
|
Posted - 2014.08.26 15:49:00 -
[2] - Quote
Hot dropping friendly? Is that my two cents or yours? |

Velicitia
Arma Artificer
2519
|
Posted - 2014.08.26 15:51:00 -
[3] - Quote
looks more solid than the other "fix local" plans.
Not sure having supers have "nope, you're never gonna see me!" is a good thing though.
One of the bitter points of a good bittervet is the realisation that all those SP don't really do much, and that the newbie is having much more fun with what little he has. - Tippia |

shimiku
Black VooDoo Asassins The Kadeshi
16
|
Posted - 2014.08.26 15:52:00 -
[4] - Quote
so when i jump in to a system and cloak and log out then in again i will not apear in local so now i can hot drop ppl with out them know it might happen / be prepared ? |

Fer'isam K'ahn
None Of One
352
|
Posted - 2014.08.26 16:06:00 -
[5] - Quote
+1 for innovation and logic. Reserve my judgement about implementation for now. Nice trail of thoughts.  Are you sure your issues aren't elsewhere ?! |

Discomanco
We pooped on your lawn We pooped on your lawn.
41
|
Posted - 2014.08.26 16:36:00 -
[6] - Quote
shimiku wrote:so when i jump in to a system and cloak and log out then in again i will not apear in local so now i can hot drop ppl with out them know it might happen / be prepared ? Depends on how the local is going to work out with the "Pilots won't disappear from their previous Local channel until they show up in a new one.". Logging off might remove you from local (or may not), but once you log in, your previous Local was still the same, so you were never showed up in a new one? I don't know, just a thought |

Bronson Hughes
The Knights of the Blessed Mother of Acceleration
308
|
Posted - 2014.08.26 16:58:00 -
[7] - Quote
Discomanco wrote:shimiku wrote:so when i jump in to a system and cloak and log out then in again i will not apear in local so now i can hot drop ppl with out them know it might happen / be prepared ? Depends on how the local is going to work out with the "Pilots won't disappear from their previous Local channel until they show up in a new one.". Logging off might remove you from local (or may not), but once you log in, your previous Local was still the same, so you were never showed up in a new one? I don't know, just a thought I had thought about how Local handles pilots logging off. Initially, I was thinking that pilots would continue showing up in Local (whichever Local they happened to be in) when they logged out. This would make for some interesting gameplay options because you'd never know if, for example, that AFK cloaker was even really logged in or not, let alone at the keyboard.
But, I took it out of my proposal because of the density of logged out pilots in certain systems. Can you imagine the server strain and bandwidth issues if Jita Local tried to display the names and portraits of every single pilot logged off in Jita? As interesting as I think this would be, I doubt the hardware could handle it effectively. So, for now, my idea has you disappearing from Local, whichever Local you may be in, when you log out, and reappearing when you log in. It's just like it is now, except for the whole "I may not be where Local thinks I am" part.
So, to answer the original question, if you show up in Local, you'll show up in Local until you show up in another Local. Logging out won't drop you from whichever Local you're in when you log back in.
Now, you could still get a "ghost" CovOps into any system without the logoff mechanic. Have another CovOps pilot enter the system via stargate (they'd be visible in Local), have them light a covert cyno, and then have a BlOps bridge you into system. You'd be cloaked, and not show up in Local, but it would take three pilots to accomplish and you'd be vulnerable to being probed out for at least a few moments while the covert cyno is up. Reading Comprehension: a skill so important it deserves it's own skillbook.
I want to create content, not become content. |

Mike Voidstar
Voidstar Free Flight Foundation
718
|
Posted - 2014.08.26 17:42:00 -
[8] - Quote
I can go along with this so long as it holds until the pilot does *anything* detectable---shoot a rat, warp, dock, launch probes, use Dscan.... anything at all but move at subwarp without a MWD out of sight of anything else. As soon as you are on grid with something that is monitored... you are now monitored.
|

Bronson Hughes
The Knights of the Blessed Mother of Acceleration
308
|
Posted - 2014.08.26 17:46:00 -
[9] - Quote
Mike Voidstar wrote:I can go along with this so long as it holds until the pilot does *anything* detectable---shoot a rat, warp, dock, launch probes, use Dscan.... anything at all but move at subwarp without a MWD out of sight of anything else. As soon as you are on grid with something that is monitored... you are now monitored.
I originally wanted to do something like that as well. You do something in local, you show up in Local. However, I have a feeling that implementing that would be quite a technical challenge. For the sake of simplicity, I kept the current WH-space mechanic of you say something in local, you show up in Local. Reading Comprehension: a skill so important it deserves it's own skillbook.
I want to create content, not become content. |

Bronson Hughes
The Knights of the Blessed Mother of Acceleration
310
|
Posted - 2014.08.27 14:47:00 -
[10] - Quote
Bumping an idea that, at least so far, people haven't thought is horrible. Reading Comprehension: a skill so important it deserves it's own skillbook.
I want to create content, not become content. |

Aivlis Eldelbar
Ubuntu Inc. The Fourth District
17
|
Posted - 2014.08.28 13:01:00 -
[11] - Quote
+1 for the innovative side of it, I can't say I've read this before.
It does sound hard to implement, though, and would lead to massive headaches if you're trying to hunt someone. The downside of your proposal is of course the fact it buffs hotdroppers in null, as it allows them to seed undetectable cynoships into system via bridges, with no counterplay possible.
What makes WH local work so well is the nature of wormholes and the inability of unseen predators to summon their whole coalition on top of Random Mackinaw #1287981 with impunity. People are fine with not seing reds in local since if they got into system it's because the entrances were not being monitored, and even if something decloaks, it will have to kill you by it's own merits, not via an "I Win Button"
While your system is a decent, if complex, proposal, it needs mechanics more advanced than the ones present in w-space to decide if someone shows up in local. Dscan pings could be a way, as they are needed for active hunting, and it matches RL nicely (active radars can be detected at double their own range due to them radiating energy out, so if someone is pinging dscan they should be noticeable in some way). You could argue for this to only happen if the hunter used dscan close enough to a gate, station, etc... thus adding another element to make systems more diverse.
In all honesty, I don't see this happening in EVE with it's current developement direction, but best of luck with the idea, as it's quite nice. |

Alvatore DiMarco
Capricious Endeavours Ltd
2497
|
Posted - 2014.08.28 13:41:00 -
[12] - Quote
Since we're talking about lore, stargates will indeed know if you've left the system. The FTL communications we keep seeing referred to in the lore manifest themselves for us as the chat system. FTL communications are handled by fluid routers; these routers are embedded in each stargate just as a matter of simplicity. Every ship that is built has its own transmitter that matches with an identical one in the FTL communications backbone.
https://community.eveonline.com/backstory/scientific-articles/faster-than-light-communication/ <-- Here's the proper explanation.
So when you leave system, yes indeed the fluid router network will take notice. Even if you leave by a WH or cyno. |

Zylona Femtov
Center for Advanced Studies Gallente Federation
11
|
Posted - 2014.08.28 14:04:00 -
[13] - Quote
Bronson Hughes wrote:
So here's an idea. Keep Local largely as-is but pilots will not become visible in Local until they:
1. Enter a system via stargate. 2. Dock at a station. 3. Say something in Local Chat.
For once we have a reasonnable idea, that might work.
I would point out that only crossing a gate or log/unlog in station should be registered. That for being logical with the Concord control.
If you arrived throught a wormhole or you log in space after downtime, you shouldn't be visible in local until you speak out.
That might freakout people at war in hight sec and low sec might be more interesting to investigate if the usual pirate cannot see you directly at first, travelling in null might become tricky as most of the time it's allright.
I like this idea |

Bristol Snogg
Velocity Industries Ltd
0
|
Posted - 2014.09.29 18:31:00 -
[14] - Quote
I have also been thinking about this and would like to add to the OP.
So lets consider the following. To appear in the local chat channel as already mentioned a pilot has to:
Enter a system via a stargate and...
A communication hub needs to be present in system.
So for High Sec, Low Sec and NPC 0.0 due to the presence of a NPC station this communication hub will already be built as is part of the station and so local members are displayed as per normal now.
However any NPC space that does not have a station there are two trains of thought; a. Local does not get displayed unless members communicate in it, just like WH space b. or CCP design a communication hub and anchor it around the sun so that the communication hub generates its power from the system sun. Imagine having this structure orbiting the sun, just visible in the glow. This will allow local to be displayed as per normal.
This brings us the non NPC space or 0.0 space owned by alliances etc
If an alliance want local members to be displayed then they will need to build in each system they own a communication hub which again can be anchored only around the sun.
If this structure is in system then local members are displayed as per normal. If the communication hub is not present then guess what, then local acts just like it does WH space. So this will be separate structure from the station.
Of course this is EVE and so this communication hub can be destroyed, but unfortunately is just another structure grinding scenario.
So in 0.0 space by not having a communication hub means that people entering the system can enter without being detected unless the people living in system use their D-Scan. Those that live in system can also be hidden unless those entering use their D-Scan.
In WH space the communication hub cannot be anchored due to the effects of WH space. So WH space does not change, it remains as is.
|

Daenika
MMO-Mechanics.com
143
|
Posted - 2014.09.29 19:35:00 -
[15] - Quote
I'm....actually a huge fan of this idea, and it fits perfectly with lore. It would definitely make wormhole travel a LOT more powerful, but still leave limits (ie you can surprise jump someone in the system the wormhole is in, but not in the next system over, since you'd have to take a stargate to get there).
That said, I would amend it such that jumping to a cyno beacon places you in local, since they are anchored structures that are likely in Concord's database uplink. Ship-based cynos would work as you suggest. This is to further emphasize that you either need to have a cyno ship to jump to, or an escort fleet at the cyno beacon.
Also, since kills are logged in Concord's DB in k-space, it might make sense to add pilots to local once they've been logged on a killmail. This would allow single-instance ganks without allowing hordes to float in a system cloaked on a gate for every traveler through.
That said, I tend to agree with the above. I think Supers should have an innate exclusion to this, in that they always show up in local (large enough that the stargates automatically detect them, or a Concord-required transponder, or something). |

Alundil
Isogen 5
679
|
Posted - 2014.09.29 19:58:00 -
[16] - Quote
Echoing other nods of approval. Of all of the ideas that have sought to "iterate" on local, this one seems a decent middle ground between ensuring that local is still present and functioning but doesn't offer free, limitless and instantaneous intel gathering.
Given that my personal preference is the wspace model of delayed until you say something, I DO realize that such a model would likely never be adopted by CCP for the kspace systems (as known is implied).
[LORE] With that said, stargates and stations (and even jump bridges perhaps) are the only structures that one could reasonably assume would have transit records made available to CONCORD or whichever New Eden group is responsible for maintaining the "public" interstellar comm relays. All other methods of ingress/egress avoid, explicitly, any involvement with or reliance on CONCORD maintained structures. [/LORE]
As for the actions that "get you reported in local" here's my breakdown:
**in 0.0** Talking in local (duh) Jumping a gate Un/Docking in a station Jumping in via Jump Bridge interacting with an agent in space
**In high/low security** the above (excluding things not possible in high/low) gaining suspect/criminal flag
The reason I don't think that 0.0 local should report pilots with aggression is the same reasons they don't go flashy now. 0.0 = lawless space.
I'm right behind you |

Angelique Duchemin
GoonWaffe Goonswarm Federation
883
|
Posted - 2014.09.29 20:08:00 -
[17] - Quote
Local is fine.
With interceptor gangs jumping in and warping to all the sites within seconds, local keeps people paying attention or they get killed.
The good thing about local is that it makes people feel safe enough to rat in Carriers and bring out other expensive ships.
Ships that can then fall victim to smart gangs or to the pilot not paying attention.
People beg for a local nerf because they want free kills for little or no effort but once the risk-reward scales so far in the risk direction then they will just find other methods of income and you won't have anything to hunt.
The very sun of heaven seemed distorted when viewed through the polarising miasma welling out from this sea-soaked perversion, and twisted menace and suspense lurked leeringly in those crazily elusive angles of carven rock where a second glance shewed concavity after the first shewed convexity. |

Daenika
MMO-Mechanics.com
143
|
Posted - 2014.09.29 20:28:00 -
[18] - Quote
Quote:The reason I don't think that 0.0 local should report pilots with aggression is the same reasons they don't go flashy now. 0.0 = lawless space.
I tend to agree, but it's well established that kills, at least, get reported. That's why I suggested that pilots that post on a killmail show up in local. That's not aggression, just if you're actually on a killmail.
I would also add cyno beacons to the list. They use the same system as jump bridges.
Angelique Duchemin wrote:People beg for a local nerf because they want free kills for little or no effort but once the risk-reward scales so far in the risk direction then they will just find other methods of income and you won't have anything to hunt.
No they don't. They want the possibility of a kill, period. As it stands now, even with an interceptor, you have a minimum of about 12-15 seconds from an interceptor pilot jumping into system until they land on grid with you, and that's if they pick the right anoms and it's relatively close to the gate. Even with hyperspatial accelerators and implants, inties still can't drop below about 10-12 seconds from initiating warp to landing on grid unless it's a very short warp.
Now, any stationary ship short of a capital can guarantee getting into warp in 8-10 seconds with the use of an AB or MWD. These ships are even largely immune to bubbles. It takes a warp-speed rigged dictor with implants a minimum of 10-20 seconds to get on grid with a station, even if the station is on the same celestial as the jump gate. The dictor can instantly deploy a bubble after leaving warp, but then must burn around (another 20-30 seconds, or more for large stations) to get other approach vectors. As long as the ratting ship initiates warp before the bubble on their approach vector is deployed (even if they are still aligning and have not yet entered warp at the time), they will land at zero on the station and instantly dock up. Even if they are coming from the same direction as the dictor, from hundreds of AU away, they'll sail clean through the bubble and land at zero.
Local is too powerful in its current state, and ratters have too much of an advantage in the balance.
Also note that this wouldn't do much for interceptor gangs, since those mostly roam through stargates. This would mostly be a thing for covert gangs moving around via wormholes or blops bridges. |

Angelique Duchemin
GoonWaffe Goonswarm Federation
885
|
Posted - 2014.09.29 20:43:00 -
[19] - Quote
Daenika wrote:Quote:The reason I don't think that 0.0 local should report pilots with aggression is the same reasons they don't go flashy now. 0.0 = lawless space. I tend to agree, but it's well established that kills, at least, get reported. That's why I suggested that pilots that post on a killmail show up in local. That's not aggression, just if you're actually on a killmail. I would also add cyno beacons to the list. They use the same system as jump bridges. Angelique Duchemin wrote:People beg for a local nerf because they want free kills for little or no effort but once the risk-reward scales so far in the risk direction then they will just find other methods of income and you won't have anything to hunt. No they don't. They want the possibility of a kill, period. As it stands now, even with an interceptor, you have a minimum of about 12-15 seconds from an interceptor pilot jumping into system until they land on grid with you, and that's if they pick the right anoms and it's relatively close to the gate. Even with hyperspatial accelerators and implants, inties still can't drop below about 10-12 seconds from initiating warp to landing on grid unless it's a very short warp. Now, any stationary ship short of a capital can guarantee getting into warp in 8-10 seconds with the use of an AB or MWD. These ships are even largely immune to bubbles. It takes a warp-speed rigged dictor with implants a minimum of 10-20 seconds to get on grid with a station, even if the station is on the same celestial as the jump gate. The dictor can instantly deploy a bubble after leaving warp, but then must burn around (another 20-30 seconds, or more for large stations) to get other approach vectors. As long as the ratting ship initiates warp before the bubble on their approach vector is deployed (even if they are still aligning and have not yet entered warp at the time), they will land at zero on the station and instantly dock up. Even if they are coming from the same direction as the dictor, from hundreds of AU away, they'll sail clean through the bubble and land at zero. Local is too powerful in its current state, and ratters have too much of an advantage in the balance. Also note that this wouldn't do much for interceptor gangs, since those mostly roam through stargates. This would mostly be a thing for covert gangs moving around via wormholes or blops bridges.
People are killing ratters in null all day every day. What are they doing right that you don't?
The very sun of heaven seemed distorted when viewed through the polarising miasma welling out from this sea-soaked perversion, and twisted menace and suspense lurked leeringly in those crazily elusive angles of carven rock where a second glance shewed concavity after the first shewed convexity. |

Daenika
MMO-Mechanics.com
143
|
Posted - 2014.09.29 20:59:00 -
[20] - Quote
Quote:People are killing ratters in null all day every day. What are they doing right that you don't?
They are finding people that are afk or stupid. I myself lost a Rattlesnake to a hotdrop back in my FA days of yore when I went AFK for a bio with a neut in system. Careless people will lose their stuff regardless.
The problem is, if people are paying attention, they are 100% immune to ganks most of the time. Ratting carriers a bit less so, but battleships and below can completely negate any gank attempt purely through vigilance. It doesn't matter how skillful or prepared the ganking party, if the ratter hits "warp to station" as soon as a local enters system, they cannot be ganked with current mechanics. That's why afk cloaking is a thing, because it's the only way to catch otherwise watchful people, by making the presence of the neut so persistent that the only options are to give up on ratting in that system entirely, or rat with the neut in system and give up your local intel source.
This method would give gankers an option in certain circumstances. I recall a few weeks back when we had a system with literally 30 multiboxed characters mining in barges in a system. If a neut entered system, they initiated warp nearly instantly. Whether it was a bot or simply a vigilant person, there wasn't a single thing that could have been done about those miners. They were functionally mining in high sec, in that they had essentially zero risk of being ganked. I'm not sure even a log-in warp at belt in an interceptors would have been fast enough to catch them. |

Alundil
Isogen 5
679
|
Posted - 2014.09.29 22:17:00 -
[21] - Quote
Daenika wrote:Quote:People are killing ratters in null all day every day. What are they doing right that you don't? They are finding people that are afk or stupid. I myself lost a Rattlesnake to a hotdrop back in my FA days of yore when I went AFK for a bio with a neut in system. Careless people will lose their stuff regardless. The problem is, if people are paying attention, they are 100% immune to ganks most of the time. Ratting carriers a bit less so, but battleships and below can completely negate any gank attempt purely through vigilance. It doesn't matter how skillful or prepared the ganking party, if the ratter hits "warp to station" as soon as a local enters system, they cannot be ganked with current mechanics. That's why afk cloaking is a thing, because it's the only way to catch otherwise watchful people, by making the presence of the neut so persistent that the only options are to give up on ratting in that system entirely, or rat with the neut in system and give up your local intel source. This method would give gankers an option in certain circumstances. I recall a few weeks back when we had a system with literally 30 multiboxed characters mining in barges in a system. If a neut entered system, they initiated warp nearly instantly. Whether it was a bot or simply a vigilant person, there wasn't a single thing that could have been done about those miners. They were functionally mining in high sec, in that they had essentially zero risk of being ganked. I'm not sure even a log-in warp at belt in an interceptors would have been fast enough to catch them. This.
Used to rat in null with a blingy Hub-Vindi....never even got close to losing it. Not once. But then I was paying attention. Local intel too stronk.
I'm right behind you |

WILLY TROPICAL
Republic Military School Minmatar Republic
13
|
Posted - 2014.09.29 23:20:00 -
[22] - Quote
I rat in null a lot and of course i'm inmune to ganks becuase i'm always watching local and never afk, so what. Keep hunting and looking for unaware people or come to the forums to beg for easy kills. Oh yes, you already did the latter. Get lost. |

Leonard Nimoy II
Dark Force Protectorate Special Operators Federation Alliance
8
|
Posted - 2014.09.29 23:27:00 -
[23] - Quote
WILLY TROPICAL wrote:I rat in null a lot and of course i'm inmune to ganks becuase i'm always watching local and never afk, so what. Keep hunting and looking for unaware people or come to the forums to beg for easy kills. Oh yes, you already did the latter. Get lost.
This. |

Wolf Incaelum
State Protectorate Caldari State
14
|
Posted - 2014.09.30 01:11:00 -
[24] - Quote
+1
I really like this idea. There isn't much of a point to being stealthy if everyone knows that you're there. That's like having a story on the nightly world news about a top secret satellite. It isn't very "top secret" if they have David frikkin Muir doing a report on it.
|

Laura Agathon
Black Thorne Corporation Black Thorne Alliance
6
|
Posted - 2014.10.02 09:03:00 -
[25] - Quote
So much win in this thread, as long as it gets implemented without Fozzie touching it, all will be well with the world. |

Tabyll Altol
Breaking.Bad Circle-Of-Two
20
|
Posted - 2014.10.02 11:41:00 -
[26] - Quote
So if i undock, relogg i will not apear in the local ??
Why do we need this ?
If you want no local go into the Wormholes, the local is a help for me when i-Śm playing active not to loose my ship.
-1 |

Bayta Charante
Zero Atmosphere
8
|
Posted - 2014.10.02 14:06:00 -
[27] - Quote
You could add some kind of penalization for the clone if it gets killed while not in the current local, as if the cloning facility couldn't contact the last records of the running clone and keep the new one up to date.
Just an idea... |
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |