Assembly Hall

Hi CSM,

What's happening to local chat in k-space?

Is there any effort in that direction?

If, not, what is the is problem? The issue is a non-issue or not important/postponed indefinitely?
There aren't any proposals worth considering? There aren't any good idea to form a basis for a proposal?


PS. I looked up in the Evelopedia in "Open Issues", "Rejected issues", "Issues in progress" and "Resolved issues", but no mention of local chat in any of it.

I like it.

Revising and expanding intel tools is definitely on the to-do list (as was mentioned in the May summit minutes), but we haven't seen any concrete proposals from CCP yet. Hopefully we will get an update at the next summit (Nov 30-Dec 02).

At this point I am used to how WH space works and so tired of the drama and bs involved with this subject that I would sing and dance in jubilation if all of EvE had local chat work just like it does in WH space.

Just fix D-Scan so it is useable and not just a mindless clickfest.

My attitude is just a bit different.

When WH corps are willing to have locatable addresses that anyone can right-click on to get there. When cyno's work in those areas - then let's talk about removal of local.

A lot of WH folks forget the extra protections involved:

- when your front-door moves around all the time and you can collapse it with a bit of effort.
- when cynos are useless k-space toys.
- when only so many ships, of so much mass can squeeze in before that door cycles to the next entrance.
- when locator agents won't tell folks where you are at.

Yes, you have a lot of extra protections in wormholes so the increased risks there from lack of local makes complete sense.

it does not make sense in k-space where anyone in k-space can find you with a locator agent, right-click the system name and have the path there plotted for them. It does not make sense when the only limit on how many can enter in any/every sized ship is how long the node will stay up.

There are a lot of differences between the different portions of space and few seem to take into account the less discussed benefits of w-space over k-space in such terms.

I shared some thoughts about intelligence gathering here:

https://forums.eveonline.com/default.aspx?g=posts&t=8008

The ideas evolved a bit since then like in this post https://forums.eveonline.com/default.aspx?g=posts&m=41192#post41192

When I feel like enduring the trolls I may even put it as a proposal in Assembly Hall.

It's not just about player convenience though, and the argument that "PVPers need it" won't sway people who say they'd be fine without it. Still, it's true that it's a regular occurence to see hundreds of ships move through jumpgates in nullsec. Fleets that would collapse multiple wormholes are the norm in null, and having the same local mechanics for both just wouldn't work.

There is a huge difference between wormhole space and k-space nullsec. K-space is one of connected empires, where people follow set routes and local channel chatter is often an important factor of the game. Killing local by turning it into "don't talk so they don't know you're there" like exists in w-space would fundamentally affect the culture of Eve, nevermind the gameplay.

I am against "fixing local" for just nullsec. If using a chat channel for PvP intel is to be fixed, fit it for ALL space, not just that part.

The problem: There are a multitude of subtle issues involved in "fixing local" that can be categorized.

- UI changes needed.
- Adjusting/adding tools for use.
- Maintaining distinctions between space: K-space vs W-space.

W-Space has certain attributes to it that make no local as much a risk factor as a protection. As such, having tools that allow for the degree of intel you get from local would need to be far more limited or disabled in that type of space. This is a "special case" but there are 2500 wormhole systems involved - that's a lot of "real estate" to tinker with.

As I stated - no, not just nullsec. If the stuff is going to be fixed - make it for *ALL* k-space. Remove the distinctions from "a chat channel" by enabling tools to get the information - highsec, lowsec AND nullsec. 1 other thing about this...

If tools are added or modified (example adjusting ship scanner and/or D-Scan), then enable FILTERING and PRIORITIZATION of what data is returned.

I'm all for tool based intel and getting rid of local but not without maintaining the distinctions between k-space and w-space as well as tying the tools to skills - not just "free gratis" style crap.

The total info local gives is not needed "for free". Number of ships in system? That can be very important for hunters and the hunted but who is flying what? No - not really needed "for free".

On the other hand, tool use and more details can come out -- better with the tools, even more details. How much and what types of details? ... CCP issue with feedback. "test it".