I originally thought as many do that the hour jump and hour cool down times are too much, but cutting those a lot may cause other potential problems and exploits.
I have another proposal which might help while not causing any problems.
What if FDev were to implement a faster multiple jump algorithm?
Simplest Algorithm Example:
What if there was the normal two hours of wait time on the first jump, then subsequent jumps executed within the cool down period could be much less. These sequential jumps would be cut down to as little as 10 minutes on either side with good timing by the captain. This would cut sequential layovers to as little as 20 minutes on each jump.
This algorithm, if done correctly, could become a Fleet Carrier jump optimization mini-game and we all know how Frontier like their mini-games.
Lore could easily be constructed to support this:
* And even though it's unrelated, while you're at it Frontier, give explorers a way to sell cartographic data out in the black.
What do you think?
I have another proposal which might help while not causing any problems.
What if FDev were to implement a faster multiple jump algorithm?
Simplest Algorithm Example:
What if there was the normal two hours of wait time on the first jump, then subsequent jumps executed within the cool down period could be much less. These sequential jumps would be cut down to as little as 10 minutes on either side with good timing by the captain. This would cut sequential layovers to as little as 20 minutes on each jump.
This algorithm, if done correctly, could become a Fleet Carrier jump optimization mini-game and we all know how Frontier like their mini-games.
Lore could easily be constructed to support this:
- It could be said that Tritium drives not only need a cool down, but they need a warm up, so on multi jump routes it's more efficient to keep them purring.
- The crew is already at stations. If you keep them there everything moves faster.
* And even though it's unrelated, while you're at it Frontier, give explorers a way to sell cartographic data out in the black.
What do you think?
Last edited: