Wormholes

Wow....I didnt even think of how much of a pain in the arse it is going to be finding high sec and low sec connections.

Absolutely the worst idea.

I personally think this is not the positive change you think it's going to be.
What you need to understand with the current system is that, once warp is a initiated the warper and Corp/bros are forced to deal with the consequences of that connection and what is on the other side of it.
This actually gives you the emergent game play you keep touting as being needed.

So if an equally or better force with an on the ball scanner is over there the content gets hairy (do we collapse, fight, what do we do?) but no matter what else that connect is now up and somebody is going to have to make the call which will usually end up with exploding ships.
Now look at your proposal. I can scan a new random down, tell what it is, look at my fleet, see who is answering pings, make tea and then decide "Nah, I don't fancy a C5 connect ramification today". Bookmark it, mark the bookmark not to jump to and not have to deal with it at all.
Take this to it's extreme and a farmer can use/abuse it to the nTH level. They warp to all new randoms, mark them not to be jumped at all until that number = 7 minus number of statics (maximum number of possible WH connects in any one system) and voila, a fully 100% guaranteed safe environment controlled 100% by the holding corp with no chance whatsoever of anyone ever being able to connect without them wanting them to.

It's just an opinion and sorry for the WOT but it needed careful explaining and I tried to keep it respectful which I find difficult at the best of times. Shoot down away!

The timer does need to be in the order of four hours, unless the intention is to deprive residents of any opportunity for keeping their static closed for any useable time.

This change seemed to carefully avoid removing that choice, while balancing things, I do not believe that things like a ten minute timer would achieve that goal in any way.

So should we not suggest resolutions for the possible absence of K162's after this change, rather than try to get the whole choice argument reopened and the improvements lost?

So recommendation:- if not jumped a static hole after four hours becomes a k999 and spawns visible on both sides.
After jumping it returns to it's original designation on the static side and a K162 on the other.

Would it be possible for it to be made scannable when a ship lands on grid with the wormhole rather than on first jump. The time difference would be very small, but the difference that the people in the parent hole can't just warp to the wormhole and start it's life cycle without ever making it scannable on the other side. I feel that makes things a little bit too safe for wormhole residents in general, even though I am on myself.

+1 for a timer, might be a lot more work to code. Something between 30 minutes to 2 hours sounds good.
Will also add to the paranoiafactor. "K162 just spawned but I saw noone on our d-scan nor on the other side."

Better than the original idea by far, but as others have said, this will result in a lot of K162s just never showing up at all, especially nullsec connections.

So, +1 to the idea of having the K162 spawn after a delay is met, or at first jump (whichever comes first). I think 4 hours is too long. 30 minutes seems more reasonable. That's enough time for someone who finds a new wormhole to reship if needed and jump through to go take a look without having a fleet waiting for them on the other sie, but not so much that it means w-space residents will take a big hit on finding connections.

Warping to one should start a timer upon which the k162 side is spawned anyway - but automatically spawning the k162 side does not change the farming aspect as people will just mass down their static and leave it critical and bubbled to farm.

In my optinion this strikes a fair balance between the instant-sig-showing overlay and a hunter's ability to catch prey unsuspecting. Good compromise.

Although I can foresee some shenanigans involving hole timers that start before the K162 is in place.

The reason for suggesting a four hour timer, if un-jumped, is it gives a small window of opportunity to run sites, mine, gas, do Pi and all the other reasons, why a small corp might wish to leave their static closed.
With a very short timer, all their choice to conduct these activities would be removed.

Some may believe that is a desirable goal and some do not. That is an entirely different issue and CCP were avoiding this issue at this time when setting their design for this.

The suggestion of a four hour timer does not challenge this decision, but instead, eliminates an unfortunate side effect.
That is its only goal.
All the K162s will with this eventually spawn, so no loss of K162s and no removal of reasonable choice from the occupants of the statics.

When I first started playing I joined a corp that moved to a wormhole. I enjoyed it and even though it was supposed to be risky, it wasn't too much considering that all you had to do was know where the wormholes were and spam dscan. You didn't even need to worry about where they went. With enough people in the hole you could spam dscan and usually see the hunter or even put alts on the WH entrances.

What people seem to forget is that in normal space all systems are connected and stay that way. So why should WH space be any different? I can't currently close down a star gate and keep people from coming into my pocket. So WH shouldn't have that.

When a WH connect is spawned it should be visible on both sides immediately. You still need to scan it down to find out where it is and what system it connect to... but that connection should be visible on both sides.

Just like stargates... both systems clearly have the connection. With WH space being the same then the connections are always there and the RISK is increased... just like anyone living in HS, LS, Null now...

I am all for finding some protection for people in WH since there is no local, but I think that should be done outside of "not fully connecting the systems" as they should be.