On the bridge in-jump

Logically, yes, it must be based on mass if the problem is space-time shape related - too sheer a gradient or something?

However, as noted, if you can come up with a good factor of safety value then that's a pretty good shorthand. If it's good enough for a rock/iron world then it's probably good enough for anything they're likely to deal with.

Equally, if the gravity field is the problem, then logically, the same tech which produces an M-Drive's acceleration should be able to produce an 'interdictor field' - although pulling someone out of jump is less likely, it shouldn't be beyond the wit of man to prevent someone jumping. After all, a 6G acceleration represents a (localised) gravity well equivalent to a planet six times the mass of the earth....
 
rust said:
This way an object's jump shadow is based upon its volume, while logically it should be based upon its mass, because it is the object's gravity field which influences the jump bubble, not its diameter.

In MTU it is 10D jump limit for GG's.
 
I've always seen the drop tanks interfering as the drop tanks either throwing out the mass element of the calculations due to not clearing the bubble before it hits the critical mass...

The other aspect might be that they might cause leaks in the bubble as they exit, so you have less fuel being converted into useable exotics than you would otherwise - which since the fuel is being carefully measured, is why you may end up with a shorter jump than you might otherwise do... from the description of the jump bubble, the jump drive is constantly replacing the bubble's lost exotics as the jump progresses (which is why you use more fuel) so if it has to replace lost exotics due to the puncture, leaves less for the jump endurance...
 
BFalcon said:
... so if it has to replace lost exotics due to the puncture, leaves less for the jump endurance...
Hmm ... this could explain a short misjump, but according to the Mongoose
Traveller rules a misjump can take a ship up to 36 parsec in a random di-
rection, which means there can be no direct relation between the amount
of available fuel and the distance covered by the jump.
 
I think a 36 parsec misjump can best be described by the old legend: Disk Read Error (A)bort, (R)etry, (I)gnore... :)
 
Back
Top