EVE Information Portal

I'm gonna keep this up...

CCP Greyscale:

First I love these changes. I think they are exactly what Eve needs. Great job for you and the team for putting them together.

Second, I am wondering if you would be open to removing JDC from Eve. As things stand right now the limiting factor for your ability to jump from point A to point B is jump range. JDC is a very valuable skill right now. The issue is that after this goes through the limiting factor will be jump fatigue. This means that JDC, for bring a 53 day train to V, IMO really won't be worth it as it is no longer the limiting factor. A 53 day train to go from 2.2LY to 5 LY (if the 25% bonus stayed) is really underwhelming and not super useful when the limiting factor is jump fatigue.

I would rather you set the base jump range of all ships to 5LY, except BlOps getting 7.5LY, and remove JDC all together. A while back your removed Material Efficiency skill from industry to ensure everyone was competitive from day 1. Please remove JDC, set base jump range to 5LY, and allow everyone to have the same base mobility from day 1.

A better solution than un-nerfing carriers is, I think, a new breed of JF that solely has a (large) SMA.

I like the core fatigue mechanic - it elegantly and consistently nerfs most forms of rapid travel. I believe, however, that you should be more proactive in addressing jump clones. I realize there's a lot more that needs to be considered in addition to the travel implications, but if you're going to nerf suicide cloning, I think you should take a whack at jump clones at the same time. I also think you should take another look at the use of nigh-uncatchable interceptors as a rapid travel option, as they also allow large organizations to get pilots to pre-staged ships rapidly.

Others have mentioned the new-bro joining corp use case for suicide jumping. Please do give us some tool to enable (or replace) that singular usage of the technique.

I believe that you're nerfing jump freighter range too much, or at least too rapidly. Yes, they've not always been in game, but the ecosystem and political geography of Eve have grown around their current capabilities and I ask that you at least give us a bit less of a shock while you nerf them down. An additional, and probably more significant, issue with the 5ly range is that there are pockets of NPC space that will not be reachable without jumps in (probably hostile) sov space. This will interfere with people's ability to conduct harassment and guerilla style operations (the small fights that you intend to encourage). You can tell people to harden up all you like, but it's a bit unfair to allow them to soften over the last few years and not give them a bit of time to adjust to new realities.

Edit: A longer term question I have is how (or if) you intend to support small entities operating independently deep in null sec? That would be one of the goals I'd like to see for a reshaping of null, but I can't see how it would fit with this change. A small organization will have great difficulties in achieving adequate control of that supply chain.

This is my understanding.

Roughly speaking, the fatigue value is put there to keep track of the total distance you have traveled so far. The longer distance you have traveled, the more the fatigue value is accumulated, but it can slowly decay back to zero. The rate of decay is 0.1 per minutes. After the first jump distance of 4.85LY, assume he has no fatigue initially, the fatigue value is 1+4.85 which is 5.85.

The first cooldown timer(in minute) is equal to the fatigue value after first jump, which is 5.85. He is not able to jump until his cooldown timer return to zero. While he is waiting for his next jump, his fatigue value is decaying slowly at the same time. By the time his cooldown timer reach zero, his fatigue value is decayed by 5.85*0.1 which is 0.585. So the remaining fatigue is 5.85-0.585 equals to 5.265. Note that the rate of fatigue decay is much slower than that of cooldown timer. It creates an accumulated effect for subsequent jumps.

The cooldown timer after second jump behaves differently from that of first jump. It is equal to the fatigue value just before that jump, which is 5.265. Note that this cooldown timer does not take into account the fatigue of this jump. As the second jump distance is 3.57LY, the fatigue value is increased by multiplying effect of 5.265*(1+3.57) which is 24.061. Note that after the second jump, the fatigue value is increased exponentially. While he is waiting for his third jump, his fatigue is decreased to 24.601-(5.265*0.1) which is 23.5345.

After the third jump, the cooldown timer(in minute) is equal to the fatigue just before that jump, which is 23.5345. Since the third jump is 4.19LY, the fatigue is increased to 23.5345*(1+4.19) equals to 122.144. As he watch his cooldown timer to tick down to zero, his fatigue is reduced to 122.144-(23.5345*0.1) which is 119.79.

After fouth jump, cooldown timer should be 119.79 minutes(1 hours 59 minutes 47 seconds). Fourth jump range is 4.9LY, so fatigue is 119.79*(1+4.9) which is 706.761. As cooldown time goes to zero, fatigue is reduced to 706.761-(119.79*0.1) which is 694.782. So his next cooldown timer will be 694.78 minutes (11 hours 34 minutes 46 seconds),

As you can see, if he jump right away when cooldown expire, fatique is increased exponentially for each jump from 5.85 > 24.601 > 122.144 > 706.761. Cooldown timers(in minutes) follows closely from 5.265 > 23.5345 > 119.79 > 694.78. Total time needed is 14 hours 3 minutes 57 seconds.

To avoid the exponentially accumulated fatigue effect, he can wait out the fatigue decay before he make the 2nd and 3rd jump, the time he spent for the journey will be significantly shorter.

1st jump has zero waiting time (assume he has no fatigue)
Before making 2nd jump he wait out the fatigue decay (58.5 minutes)
Before making 3rd jump he wait out the fatigue decay (45.7 minutes)
Before making 4th jump he just wait out the cooldown timer (5.19 minutes)
Before making 5th jump he just wait out the cooldown timer (30.102 minutes)
Total time needed is 2 hours 19 minutes 29 seconds. He will accumulate fatigue for the 4th and 5th jump.

To optimize time required for the journey and balance the risk involved, he has to manage when to wait out fatigue decay, when to wait out cooldown timer and when to use stargates.

Spoiler. They don't.

Brilliant idea. Just do not hurt black ops.

All those cries above give us clear evidence how crappy are powerblocks - anything beyond dropping supercaps on T1 cruiser is too demanding for them. Good to know they are just lazy and want everything without effort. Good to know it's beyond their abilities to organize convoys. And good to know things been pushed in right direction - at last.

CCP, good job. And keep that course, don't give up.

You said that there are changes to interdiction bubbles. .. does this mean they will now restrict outgoing stargate jumps?

Yeah, I am really happy about the ramifications for NPC Delve too. Because of the 5LY max range, in order to restock NPC Delve you have to take the Sakht -> 1-SMEB gate or hoof it through Querious (which, without safe stations in the face of jump fatigue, is probably not going to be very effective.) This means, as sovhavers, we can easily starve out NPC Delve by controlling the 1-SMEB gate.

not to mention with all the intel channels in this game, a capital fleet moving away from home to attack or defend one area has greater implications for another area left open.

Wars on 2 fronts will make alliances work for it, forcing diplomacy to the max.