Wormholes

--

I would prefer that the k 162 open after some period of time even if nobody falls through it. Sometimes when we open our static we find an empty hole filled with sites and only one wormhole signature. When that happens currently we have to choose between putting a scout on grid to watch it (which opens it if it is not already open) and not putting a scout there and wondering if it is closed. That sort of choice is one of the things which makes eve interesting. The ability to sit and watch it directly without opening it seems too generous to the defender.

With this change the correct action is to always have a scout on each hole while before it was a choice that mattered.

From a group-interaction perspective, this change would have a net effect of reducing the number of such interactions.

1. This change would reduce the number of connections in wormhole space, as people will not jump into an outgoing wormhole if it looks dangerous or undesirable. In particular, the number of K-Space to W-Space connections would be adversely affected.

2. Groups that have closed all incoming and outgoing wormholes and are trying to PVE in isolation are able to do so in greater safety. Consider a hostile scout in a PVE group's home system. Under the current system, the group needs to actively watch d-scan for probes to see if the scout is trying to scan his way out and bring in a hostile fleet. Under the new system the group could easily leave someone by the hole and simply listen for wormhole fire.

3. The risk to an isolated (ie all wormholes closed and static watched) PVE group from rage-rollers is only marginally increased by a reduction of 10 seconds in reaction time. Under the current system, the PVE group's reaction window is the time it takes for the hostile scout to warp to his static, the time it takes for him to pinpoint the fleet's location, and the time it takes for the hostile fleet to land. Because rage-rolling fleets are usually at the ready, their fleet is always at the static by the time the scout has pinpointed their target's location. Therefore, the new system would reduce the PVE group's reaction window by the time it takes for the hostile scout to land on his static (about 10 seconds). Everything else would essentially remain the same.

Thus this change would reduce the number of wormhole connections (a source of player interaction), reduce the risk from in-system hostile scouts (another source of player interaction), and only marginally increase the risk from rolling fleets. The number of potential player interactions would decrease overall.

I would suggest having non-static wormholes spawn their outgoing and K162 signatures concurrently while having static wormholes keep their current behavior. This system, combined with an increase in non-static wormholes would lead to an increased number of connections. And because not all new wormholes guarantee someone was on the other side (ie K162 from a nonstatic wormhole), w-space groups would be tempted to become complacent and thus more vulnerable to attack. Spawning the sister K162 for static wormholes concurrently is not advised, as that would encourage people to leave them critical instead of closing them altogether.

In fact, spawning K162 signatures WITHOUT guaranteeing that someone was there makes for very interesting gameplay, as our current and proposed system gives defenders instant intelligence that someone is nearby. If K162 wormholes appeared by themselves, groups intent on isolation would have to determine whether hostiles are actually around. The fact that the hole could have spawned by themselves encourages risk-adverse groups to try to collapse the wormholes, thus rewarding potential attackers for being stealthy. At the same time, those same groups benefit from increased logistical routes.

As others have said too not having the k162 end spawn will basicly result in nullsec/bears never entering their wormholes thereby eliminating those connections.

How about making the k162 end spawn after 12-24 hours regardless.

First of all - Thank you CCP Fozzie for publishing that Devblog.

Now to the point :)

I think this is nice change and it will help with PvP and will raise some blood pleasure of PvE pilots ^^

Good change - specially if you also add, that connections appear on both side after 10-15mins regardless for you warping to it or scanning it.

This would mean that you can make sneak attacks - super
This means you can block of your WH (minus random INBOUND connections) - even better
This means more connections in general, which in turn means more interactions - also super

Caveat, I am not currently living or working in Wormhole Space, nor have I.

I can understand the ability of an array that scans for and detects Worm Holes, being placed in a solar system to alert those in it that a Worm Hole has opened up.
I can understand that array broadcasting that information to those in that system.
That should be the end of CCP's involvement. A Worm Hole forms, has two ends, if one of those ends is in a system that has a detection array, it is detected and people can be notified.
The detection array should be programed to be selective to whom it sends that information to.
If Corp A installs a detection array, then they should be able to select only their corp and/or alliance to receive that information.
If Corp B wants that information, they would need to install an array in that system as well.

Also, if the capsuleers entered the system via a Wormhole, there is no record of that entry, hence no notification in local as the Gate did not record and or transmit that information ( I believe this is current functionality, it should never be modified). Once that capsuleer makes a transmission, that transmission is detected in system (current functionality I believe). However, if not transmitted in local, local should just get a blank "unknown" added to it.
This should also be true if entering a system via a cyno. Sure, your systems detected the cyno, but not who, if anyone, entered via that cyno.

For a particular type of Wormhole not being detected by the an array, OK, I get that. But for that array to suddenly detect it when someone transits it... I say BS. Either that type of Wormhole is detectable, or it is not. If the Wormhole is not detectable, how was it found in the first place?
I do not buy the argument about fairness. Something either is, or it is not. Let those in system figure out how to deal with the situation, not CCP.

You want a Wormhole to handle any amount of mass, but it collapses after an approximate timeframe, no problem.
You want a Wormhole to collapse after an approximate amount of mass has transited it, no problem.
You want a Wormhole to have a combination of those, sure, but either it is detectable or it is not.

Space is NOT safe. Wormhole space, even less so. Live with it.

Galmalmin

Will decrease k-space wh's opening in wh's.
K-people will just not jump wh's that are not direct null>hs etc.
They have to warp to see where WH leads and therefor the WH spawn. If that is removed and only jump will spawn the wh on other side there will be waaaaay less of em.

I like the idea that the attacker gets just as much time as the defender now when opening up a new wh. I just hope that the new random wormholes will make up for the fact that people won't open wh's by jumping through them all the time. If not you may concider adding a timer after the wh spawned to go ahead and open up the k162.

So in essence... this is reducing the number of null/low/high connections spawning from the k-space side, reducing targets.

This is reducing the Wh systems in a chain and the branches of a chain, so again.. reducing targets.

why not just stop wormhole signatures appearing instantly in the scanner and bring back the days of having to mash the scan button? people who put in effort are still safish, others who dont will find they are dead when ships start landing on grid.. i see this update as making wormholes too safe, and the mass>spawn distance change is broken and not a compromise.

Checking calendar to make sure its not april 1st.