• Welcome to the new COTI server. We've moved the Citizens to a new server. Please let us know in the COTI Website issue forum if you find any problems.
  • We, the systems administration staff, apologize for this unexpected outage of the boards. We have resolved the root cause of the problem and there should be no further disruptions.

Travel time for in system jumps?

They really only are useful for a few reasons:
1) You're going more than a few AU
2) you don't want the low-energy alpha that is 1PSL+ impact with the interplanetary medium.
3) you want to avoid pirates
4) you're using TNE, T4, or T5
4.1) TNE - fuel restrictions make even 1LM slower than jump.
4.2) T4/T5 1000D limit makes all deep system worlds outside the short-term reach of T-Plates.
 
Even if the distance travelled is zero, the time in jump is always 168 ± 10% hours (151 to 185 hours).
Unless, of course, you Misjump; then the duration might be significantly longer (assuming the vessel survives in the first place).

According to CT02 "Starships", page 6:

A misjump results in a jump in a random direction (1 of 6), for a random distance (1 to 36 parsecs), with a random amount of time (1 to 6 weeks) spent in jump space before arrival.

Thus, according to canon, a stationary misjump can not occur -- the ship is thrown a minimum of 1 parsec away in a random direction.
 
Last edited:
Thus, according to canon, a stationary misjump can not occur -- the ship is thrown a minimum of 1 parsec away in a random direction.

Actually, not really. A J-1 is UP to 3.26 parsecs. (anywhere within one hex) A J-1 can send you to a star 1 LY away. So, J1 is 0-3.26 parsecs. J2 - 3.27 - 6.52 Parsecs, etc.

At least that is how Jump space works... :)
 
Actually, not really. A J-1 is UP to 3.26 parsecs. (anywhere within one hex) A J-1 can send you to a star 1 LY away. So, J1 is 0-3.26 parsecs. J2 - 3.27 - 6.52 Parsecs, etc.

At least that is how Jump space works... :)
Yes, but the way the game mechanic works is that it places you a minimum of 1 parsec away. The question is how closely the game mechanic matches "reality". Note that the distance distribution follows some weirdly twisted bell curve. Perhaps misjumping ships do, in "reality", sometimes wind up less that a parsec away, but the likelihood is too low for the resolution of the game.


Hans
 
Yes, but the way the game mechanic works is that it places you a minimum of 1 parsec away.

Actually, there is no minimum. A jump hex is anywhere within one hex.

"Throw one die to determine the number of dice thrown (1 to 6); throw that number of dice to determine the number of hexes in length the misjump is."
 
No, a "Jump 1" is not the same sematically as "a 1 hex jump". The latter is anywhere from 0.5 to 1.5 Pc distance... while the former is anything under 1.5Pc.

It's a side effect of the quanitization effect of the hexgrid...

And the misjump is a minimum 1 hex jump, not a jump 1. Really, it's possible in very odd circumstances to quantize out to even less than a parsec... but in general, it means at least a parsec, especially if one treats the hex measures as centered upon the ship at departure.
 
No, a "Jump 1" is not the same sematically as "a 1 hex jump". The latter is anywhere from 0.5 to 1.5 Pc distance... while the former is anything under 1.5Pc.

It's a side effect of the quanitization effect of the hexgrid...

And the misjump is a minimum 1 hex jump, not a jump 1. Really, it's possible in very odd circumstances to quantize out to even less than a parsec... but in general, it means at least a parsec, especially if one treats the hex measures as centered upon the ship at departure.


I see what you're saying, semantically. So, a mis jump could be as little as .5 hex.
 
Actually, there is no minimum. A jump hex is anywhere within one hex.

"Throw one die to determine the number of dice thrown (1 to 6); throw that number of dice to determine the number of hexes in length the misjump is."
Not the way I interpret the text. 36 hexes is 36 hexes away, not 35. 1 hex is 1 hex away, not 0. If you roll a 1 on the first throw and a 1 on the second throw, you end up in the adjacent hex, not the same one.


Hans
 
That particular rule doesn't need to. It's already written elsewhere in the rules.
Could you elucidate, please? The rule doesn't refer to any other rule and AFAIK no other rule refer to this one, so what relevance could they have?


Hans
 
Could you elucidate, please? The rule doesn't refer to any other rule and AFAIK no other rule refer to this one, so what relevance could they have?


Hans

It's an unintended consequence of using 1Pc hexes and quantizing systems to the centers of those hexes.

If I have a system at 1204 it could be in col 12 anywhere from 11.5 to 12.5, and in row 4 from 3.5 to 4.5, but it all renders to 12 by 4.
 
It's an unintended consequence of using 1Pc hexes and quantizing systems to the centers of those hexes.
It's a consequence of that, yes, and for all I know it could be an unintended one. But the salient point is that it is. For gaming purposes a system in one hex is considered to be one parsec from a system in an adjacent hex.

If I have a system at 1204 it could be in col 12 anywhere from 11.5 to 12.5, and in row 4 from 3.5 to 4.5, but it all renders to 12 by 4.
That's sounds reasonable enough, but AFAIK there is no rule anywhere that actually says so. HG_B says that this half-parsec variation is mentioned elsewhere in the rules. Where?

EDIT: Incidentally, if a system is able to be anywhere in hex 1204, then it can be anywhere from 11.000[...]001 to 12.0 and from 3.000[...]001 to 4.0. Look at a hex map.


Hans
 
Last edited:
Back
Top