EVE Information Portal

because this change might be the reason for traffic control messages when attempting to make wormhole jumps. fewer nodes = standby mode which causes jump attempts to fail, with a traffic control message similar to the ones you'll experience on the test server. the problem with this condition is the failed jump also counts against the wormhole's mass limit, even though the jump was unsuccessful. This leads to unexpected wormhole collapse due to mass limitations that are reached prematurely. The inaccurate mass accumulation after failed jumps is the issue, beyond the inconvenience of needing to re-attempt wormhole jumps because the node was unprepared.

The traffic control message is a preexisting condition, and is made worse by the reduced number of nodes dedicated to w-space. in the case of jump gates which lack the mass limitations of wormholes, traffic control messages simply mean 'try again'.

This dev blog was referenced because internally, within CCP, it's not guaranteed everyone has up-to-date knowledge of changes such as CCP Prism X's node remapping dev blog. Without knowledge of such a change, employees of CCP and players are likely to assume wormhole mass limitations are handled correctly, without any cause to believe otherwise.

to put the severity of this into perspective, a wormhole with a 3 billion kg mass limit can handle 3 capitals. with a failed jump attempt due to traffic control, the wormhole can only handle 2, after the first capital's mass was inaccurately counted against the wormhole's mass limit.

further implications of this condition include collapsing a 3 billion kg wormhole with 3 capitals that attempt their jumps simultaneously, which would be rejected by traffic control of an unprepared node, and collapse the hole without any jumps made. depending on the goal of the players making the jump with those capitals, this could be good or bad.

a potential "off switch" for wormholes, if a wormhole on an unprepared node is overwhelmed by the initial jump attempt.

this inquiry of mine can be dismissed if it can be confirmed that mass limits are not affected by failed jump attempts due to traffic control. however, i'm farily certain I experienced this bug yesterday when attempting a jump with some ships of considerable mass. it was a sequence of jumps that I have made several times previously.

the basic question is: If a wormhole jump fails because the node is unprepared (and generates a traffic control message), does a ship's mass count against the mass limit of the wormhole, even though the jump was rejected by the node.

sorry about the triple post, this is something I found (all I've found so far).

https://forums.eveonline.com/default.aspx?g=posts&m=777940#post777940

(CCP Greyscale)

if that answer could be updated to include how traffic control fits in, that would be greeeeat

I dislike leaving things hanging.

Wormhole Mass reduction is well outside of the scope of my work. Obviously mass should not be decreased on a denied jump but that should be bug reported through the proper channels so that it receives proper due diligence. Apparently this has been BR'd already so YAY!

Libras are not trustworthy. We're extremely dodgy characters who seem to be willing to adopt any side of everything for the sake of whatever deviant impulses drive us at that given moment.

I do believe everything else has been covered already in previous posts.

Fly safe...
..ish!

So is there going to be any investigation into whether static striping of nodes will give better performance for large fleets moving through systems because of the inter- vs. intra- node thing?

Who cares about some random system in bum **** egypt? When you have adjacent systems all on the same node, that makes the game even more unplayable than it was previously. It makes the issue of moving large fleets even worse than it was before.

Seriously, what the hell were you thinking? You clearly have no idea how people actually play this game.