Probably a bit late to spitball, but what the hell.

1) Set all ship jump ranges to exactly 10 light years. Carriers, Titans, Blops, everything. Starbase JBs remain at 5LY.
2) Jump fatigue is measured from 1-100%. Whenever you jump, your fatigue is increased by whatever percentage of 10LY you jump. So a 4LY jump adds 40% fatigue, 8.5LY adds 85%, etc. Simple.
3) Fatigue decays on a curve akin to shields and cap regen, just in reverse. This means that it's much quicker to go from 30% to 20% than from 100% to 90%.
4) Until the fatigue decays completely, this percentage is a limit on subsequent jumps. Someone with a 90% fatigue cannot jump more than 1LY, while someone on 35% fatigue can jump up to 6.5LY
5) Special-cases like blops, freighters and JFs build fatigue at a reduced rate (50% is probably fair).
6) Training Jump Drive Calibration speeds up fatigue decay.

This is far simpler to understand for players, easier to do math on the fly, and means less sitting around waiting on cooldown timers doing nothing in what's meant to be a video game. Inter-region travel is just as slow, but local travel is viable. There's an incentive for players to make shorter jumps or take gates, as recovering from a long jump would take much longer than several shorter ones.
The higher range introduces a trade-off for jump-capable combat ships; the further away they hide the easier it is to make a surprise attack, but the harder it becomes to get away again. In the future, power projection can be tuned by simply adjusting the base rate of fatigue decay.

Examples:

An Archon pilot jumps from Sahkt to Karan, a distance of 6.32LY. After the jump, his fatigue is set at 63.2%. His next jump must be 3.68LY or less, although this will gradually increase as fatigue decays.

A jump freighter pilot jumps from CCP-US to DO6H-Q, a distance of 3.24LY. After the jump, his fatigue is set at a reduced rate of 16.2% (half of 32.4%). His next jump must be 8.38LY or less, although this will gradually increase as fatigue decays.

A Rifter pilot takes a starbase jump bridge between CCP-US and DO6H-Q, a distance of 3.24LY. After the jump, his fatigue is set at 32.4%. His next jump must be 6.76LY or less, meaning he can use at least one more Jump Bridge immediately. This means a return trip is easily possible, but using more than 1-2 bridges means a lengthy delay.

Actually, increasing the range of a JF doesn't change the amount of TIME it takes to move at all. Nor does it the cost. Both fatigue and fuel consumption are measured in light years. I might be able to jump twice as far in one jump in a Jump Freighter, but I have to wait twice as long for jump cooldown, twice as long for jump fatigue to wear off, and pay twice the isotope cost. All increasing the range does is make more of nullsec accessible from lowsec and make all routes take fewer cyno alts.

Doesnt fix the problem of them jumping a gate and instantly leaving - that was the issue at hand. With being unable to bubble - you cant stop that. Unless there's something artificial stopping the gate jump.

Don't you see that by bowing to pressure from the renter serf and lord accounts that this means it is even less likely that Nullsec industry takes off? Remember your goal was to make the universe bigger, and to make it a meaningful decision to live in Omist, instead of it just being yet another convenient region to rent.

I can see that there is a potential problem with the way T2 resources are spread out for nullsec self-sufficiency, and if this is the only reason you are watering down your nerf so much for JF's and titan bridged freighters, then so be it, but please get working on a new moon system so that we can have the original planned changes in all their glory.

By keeping JF's at 10 , and buffing groups that can just bridge freighters around you just destroy any chance of nullsec industry taking off. People will just continue to stock nullsec from Jita and the industry game continues to stagnate, not to mention the already noted potential to deploy HAC / T3 fleets quickly across the universe with a JF + pods in ceptors.

Why the random nerf to the rorqual btw? I know we've been waiting for a Rorqual update for years but since the ship isn't being used how you originally imagined it (in a belt, tractoring jetcans, crushing ore etc) you just decide to nerf it because the players are using it as a hauler? Why not wait until you have the new rorqual redesign ready and nerf it then?

Do the right thing CCP Greyscale, do what is right in terms of game design, not what those who control the CSM are crying out for.

--
Fang

Even with these small changes, more regional fights will kick up, because there will be less fear of getting hotdropped from across the galaxy.

Discussing it.

Please increase the Mexallon in nullsec ores

I guess there won't be any "freighter convoys" after all.

90% reduction means that transport fleets will move a lot faster than capital fleets. Pretty easy to turn unarmed jfs into offensive gambits with that.

Were you seriously planning to invest tens of billions into local production for just 10-100 guys in your far-away region?
That seems irrational from a business perspective.
You'd need hundreds of BPOs and huge stockpiles of lots and lots of different materials to be self-sustaining.

Tbh maybe I just don't understand the vision of self-sustaining 0.0 industry but seems like the ROI would be so bad that it would still be better to do logistics no matter how difficult it is, at least for some stuff. And then you'd just bring everything you need anyway.

Or, you could use an interceptor, and use the JFs closer to the operating base to move stuff. Much faster than your option.

I love how logistics continues to get deep anal fisted by not giving similar benefits to rorqs as you would JF's.

This is much better than the original changes. I still think the fatigue values are a tad high and they need to be capped at like 7 days maximum fatigue possible though. If pilots are allowed to accumulate too much fatigue it will wind up resulting in people inadvertantly giving themselves huge fatigue timers and, rather than waiting them out, they'll just de-sub in frustration.

A supercap in lowsec jumps a gate: implies gates were the intended travel plan. An escape cyno may not be on standby, or in jump range, in every case. A HIC with focused disrupt script loaded has a fair chance to stop a super who was gate travelling, without an escape cyno ready.

This isn't a U-Turn. The changes are intended to nerf the ability of nullsec groups to project their firepower across the universe in a matter of minutes. These changes still fully nerf capital combat ships (?rorqual?) and prevent groups from tagging along every fight that happens in the galaxy.

Even with these small changes, more regional fights will kick up, because there will be less fear of getting hotdropped from across the galaxy.

We didn't think it was sensible to let it keep its drone bonus and have a 10LY range, and at the end of the day the bonus won out. The ship needs a large rework anyway, and we'll revisit all this when that happens :)

"All ships designated as having a GÇ£haulingGÇ¥ role in ISIS (ie the following ship groups: Industrial, Blockade Runner, Deep Space Transport, Industrial Command Ship, Freighter) will similarly get a 90% reduction to distance counted for the purpose of fatigue generation. Obviously they canGÇÖt jump themselves, but this also applies on use of bridges or portals. "

Whats to stop N3//CFC from now traveling in T1 industrial hauler blobs and avoiding massive fatigue generation???

"All ships designated as having a GÇ£haulingGÇ¥ role in ISIS (ie the following ship groups: Industrial, Blockade Runner, Deep Space Transport, Industrial Command Ship, Freighter) will similarly get a 90% reduction to distance counted for the purpose of fatigue generation. Obviously they canGÇÖt jump themselves, but this also applies on use of bridges or portals. "

Whats to stop N3//CFC from now traveling in T1 industrial hauler blobs and avoiding massive fatigue generation???

Yes but it has zero chance to stop a super who does have an escape cyno ready, and the super can tank on the out gate until one is in place.

The way I figure it will work, is you get an dictor on both sides of the gate, and then it will be a matter of the dictor locking and using the infinite point on the super cap before the pilot can initiate jump drive. I imagine due to lag, and slow reactions, you would actually catch quite a few with this method.

Although if you want something more substantial, then perhaps a spool up on jumping out could be implemented.

This is what we 'others' complain about - the changes where opening up for more diverse gameplay again- with the current way only one way to play is feasible. ROI is not always measured in isk you know - there are actually players who do things just because they can be done - not necessarily because they are best isk per "insert favourite time length here".

If i would just speak for myself - and i know i am not the only one anyways - then i rather manufacture my ass of for no isk at all but for a real purpose that might support some actual group effort. Same goes for anything you might imagine - its not only shooting at things - even if many people still seem to believe that. ROI can also be measured in 'i can deliver everything the locals need' - it just depends on what your investment was meant for. With current logistics the gameplay of 'being self-sufficient' has been basically deleted.

"All ships designated as having a GÇ£haulingGÇ¥ role in ISIS (ie the following ship groups: Industrial, Blockade Runner, Deep Space Transport, Industrial Command Ship, Freighter) will similarly get a 90% reduction to distance counted for the purpose of fatigue generation. Obviously they canGÇÖt jump themselves, but this also applies on use of bridges or portals. "

Whats to stop N3//CFC from now traveling in T1 industrial hauler blobs and avoiding massive fatigue generation???