EVE General Discussion

Not to mention the fact that if I jump through a crit hole ahead of a guy and then ends up being spit out into the system I jumped from just because that other guy sat on a fast lane to the server and I did not... Now, I don't anger easily... but that would surely **** the living hell out of me.

Not sure I know what you're talking about. Polarity timer was always 4 minutes or there abouts.

Mister, Mr Kidd is correct. It's 4 minutes.

Finally! WH-Space has gone erratic. No really, I am not sure if this is bad or good, since it makes hole-life a bit more interesting. I'd really appreciate some randomness for holes. Maybe a module which can give you more precise data on the status of a wh?

This is exactly what I thought as well after reading about the module idea. First, yet another semi-mandatory module for wh shenanigans--how about no, unless it occupies no slots no? okay then. Also, there's the meta element of experience and the various tricks people have devised for dealing with wormholes and mass limits. Experience comes into play, as well as certain degrees of risk when you find that you need to put some ships through the wh to see how it acts in order to tell its mass status.Some degree of variation from what's expected is good, keeps things fun. Random behavior is just bad and obnoxious.

What needs to happen is for wormhole state updates to be correct and each wormhole needs to go through the mass cycle of "not yet significantly disrupted" -> "disrupted but not critically" -> "critically disrupted" based on its total mass allowance attribute. Yesterday I had a 1KKK kg wormhole go from "not been significantly disrupted" to -poof- nonexistent after a single jump through in a Prowler. This is bullshit because, although the nature of wormholes is unpredictable blah blah blah and I expect there to be deviations and some randomness, the deviation in this case would have had to be of about 98% assuming a 10KK kg Prowler (yay for two high slots?). Instead of a 1 billion kg total mass, the wormhole acted like anything between 0.00..001 kg total mass limit, and, say, at most about 22 million kg wormhole assuming also a ~20% deviation between the status of the hole as displayed in show info + its size, and the actual mass it has left over. OR the information about the wormhole in the "show info" was seriously incorrect, not updated properly. Either way, boo. Something is broken when you have occurrences like this pretty frequently, and their incidence "happened" to coincide with a patch.

The players already have the tools they need to make very good guesses regarding wh mass states, and their EOL states as well, and it takes more than two brain cells to use them properly. Experience should have an advantage, and if stuff starts behaving randomly enough that experience stops mattering as much as it did, it points to a broken game mechanic.

As several other people have suggested... it seems that the mass limits are the same.. but the variance is not... whatever you did messed with it so that median mass wh are almost never happening

we chain closed a couple statics just a couple hours ago.. we only used 2 ships, we pinned them, we know EVERYTHING that went through. (inc the scout to see if it was worth keeping open)

for us on a 2bil mass wh we are getting masses up around 2.23-2.38 EVERY time

Ofc we can't see the exact mass, and don't know if the last ship in tripped it at 100t or 5t but this is definitely changed from a random 10% variance to a 20% variance that seems always maxed (in our recent experience)

As one post earlier stated... someone needs to check your dependencies in the code.. something got changed and forgot to put it in the notes or more likely doesn't know they changed it.

its a hard thing to see in progress... will it close at 2.0, 2.1 or higher or lower? we are pushing ships through meant to collapse with a minimum of time and headaches... knowing it is really odd only happens after its closed

** I would suggest, other posters can feel free to disagree, that nearly any toon in this thread would welcome a random CCP visit in their WH, a short convo to get a hole closed, then kill the next static from scratch... then the GM or dev can SEE what is happening 1st hand... **

we won't mind if it means getting this nailed down and explained

If you do bring a cockroach and an enigma please!

For those insisting that the variance has changed, doesn't this paragraph explain that the wormhole mass status you are seeing may not be up-to-date? If the show info is showing old info, then you might be tricked into thinking it's still safe to jump when in fact the server has shrunk the wormhole to critical.

So I would suggest that the mass limits and the variances haven't changed. What has perhaps changed is that when wormholes shrink, clients won't find out until a bit later. The way to test this is to take a few minutes break between ship jumps during a collapse operation and see if the show info eventually updates with accurate info. For CCP Greyscale, is the visual feedback that the wormhole has shrunk also delayed, like the show info is?

When I was closing the other day visual feedback also was delayed.

Hey everyone,

Just to keep you all up to date, I've asked the new Live Team to read through this thread and have a look at the various issues being raised, as they're better placed to do thorough testing of this sort of live code :)

Thanks for bringing these glitches to our attention!
-Greyscale