Player Features and Ideas Discussion

I posted this to the discussion thread, but it was somewhere up in the 4000 range, so I'm re-posting here so maybe it gets seen.

The idea of Jump Fatigue is fine, but I don't like the exponential timer and binary choice of this implementation. It seems arbitrary and inelegant. With this system you will end up with people being left out or left behind when using jump portals or bridges. "Hey guys I would love to join the fleet but my timer won't cool down for a week, see you later :-(".

Why not make fatigue affect how far you can jump safely. As your fatigue increases the range you can jump without consequences decreases.

The consequences of jumping outside of your safe jump range could be tuned to how far outside the range you jump. If it's just outside, then you have a small chance of taking HP damage, or a debuff to Cap/Shield regen, etc. If you jump way out side of your safe range then you could have dire issues, Major HP damage, no cap/shield regen for some time, or you could burn out your jump drive stranding you for some cooldown period the duration of which could vary according to the severity of the damage.

You could tune this to have the same general principles of the timer based approach, but with the added tactical and strategic decision of jumping into the danger zone.

If you make small jumps to nearby places doing logistics within a small area, this type of system would allow you to do that with out dealing with an exponentially growing timer after each jump.

The increase to your fatigue level could scale as well, if you jump well inside your safe range the fatigue grows slowly, If you are pushing the boundaries of your safe range then it grows more quickly, and if you jump into the danger zone it could grow even faster.

From the player standpoint this could be displayed very easily in the map view showing your jump range.

From the given example provided in the dev blog, the player would come to the same decision since jumping continuously to their max safe range without letting the fatigue decrease would reduce their safe range rather quickly. You'd reach a point where your next jump could burn out your ability to jump, so might as well take the gates. But instead of making that choice for them, they still have the option of jumping.

All of the other mechanics of allowing some ships to have reduced fatigue work here as well.

Using fatigue in this way would achieve the same stated goals, but instead of taking away the players ability to jump you're giving them more choices, with tactical consequences.

Don't get the week long timer would be the answer here.

Goofy Randomness

Hmmm.

How about your fatigue timer is instead used as the percentage chance of an Elite style Misjump.

No damage or anything like that, but you could turn up anywhere within a (Fatigue value x distance of attempted jump) radius of your starting system, and then have to wait out your fatigue timer before you can jump again.

Used to make you Very Careful in Elite to keep your drives well maintained.



More people willing to wait out short fatigue timer's, more nerve-wracking if you have to push it for several jumps. The multiplying factor of the fatigue might need to be scaled down somewhat to make it fair

Ooh, Imagine arranging a hotdrop on an enemy fleet, and one of your caps misjumps, and ends up 20 ly inside enemy territory ...

Do you leave him to his fate ... Do you send in a small support fleet to try to defend it if the enemy notice ... Do you try to distract the enemy command with a feint on their borders ...

Either way it's brown trousers time for that cap pilot

how about we wait to see if the current is bad b4 we go trying to fix it? or at the very least post in one of the threads already about this topic

i do think that a max CD of 30 days as it is now (as far as i know) is a bit long. i also find the jump range of normal carriers a tad low as they only have 5LY while they had a lot more jump range then dreads, supers and titans.

so the fixing idea is good, of course it has major impact but that's the intention

Please refrain from cross-posting.

Thread locked.