"Bounty" and "legal status" are the same thing. There is no difference between them. It's merely two words for saying exactly the same.
There are, however, two different ways of displayingbounty or legal status. One is as a positive integer number (including 0), and the other is as a string. In the old plist-based scripting system (sometimes referred to as "legacy scripting") the first one was called legalStatus_number (which is the same as JS's ship.bounty) and the second one was called commander_legal_status. So even the word "bounty" wasn't used in the old system, except in shipdata.plist.
Ah, I see what you mean now! We were defining the terms in different contexts. I interpreted "bounty" as a number, and "legal status" as, well, a status, such as "Offender" or "Fugitive", as I was thinking of it in terms of the meaning of the word in language, rather than code. (Wow, that's a badly phrased sentence...)
I was not aware of the way the code worked, although in hindsight it makes sense! Thanks for the info!
If you intentionally mis-jump make sure you do it between two systems that are as close as you can get, to make sure you have enough fuel to jump after your drive is repaired. It just makes it easier that way. You don't want to get stranded after all your hard work.
If you intentionally mis-jump make sure you do it between two systems that are as close as you can get, to make sure you have enough fuel to jump after your drive is repaired.
After a forced misjump there is nothing to repair. You can jump out any time. Only if the misjump was caused by a drive malfunction, this malfunction has to be repaired first.
Still, the advice concerning fuel is important. A misjump, although leaving you stranded halfway, consumes all the fuel needed to reach your original destination. If that destination was 6.8 LY away, you're left in the middle between the two systems with only 0.2 LY worth of fuel. Therefore it is advisable not to force a misjump between two systems more than 4.4 LY apart from each other. (This does not take into account that there could be a "sideways" system closer to you than your original destination. It also does not take into account the various existing ways (all through OXPs) of taking a fuel reserve with you, or refueling in interstellar space.)
Pull up in the last couple of seconds before the jump!
Am I doing something wrong? I hit "h" to start the hyperspace jump, then 1 second before the jump I hit up. I still make it to the other system. Is there something I am missing to do an intentional misjump?
Pull up in the last couple of seconds before the jump!
Am I doing something wrong? I hit "h" to start the hyperspace jump, then 1 second before the jump I hit up. I still make it to the other system. Is there something I am missing to do an intentional misjump?
Are you using a stick? If so, sometimes the dead spot prevents the mis-jump.
Hold down the up/down key, just as the '1' starts to fade.
I would advise stilts for the quagmires, and camels for the snowy hills
And any survivors, their debts I will certainly pay. There's always a way!
Like in all good flight simulations, if you press the 'up' key you're actually nosediving, so you might have to try the other up!
Does it actually make a difference? I have to admit that I've done it without really consciously thinking about it, and I typically "climb", but I was always under the impression that diving or climbing would equally work.
byronarn wrote:
Am I doing something wrong? I hit "h" to start the hyperspace jump, then 1 second before the jump I hit up. I still make it to the other system. Is there something I am missing to do an intentional misjump?
If the timing is proving tricky then you can just fly "up" as soon as you start the countdown, and continue to fly round in circles, that should do the trick.
Like in all good flight simulations, if you press the 'up' key you're actually nosediving, so you might have to try the other up!
Does it actually make a difference? I have to admit that I've done it without really consciously thinking about it, and I typically "climb", but I was always under the impression that diving or climbing would equally work.
No, it is only climbing that does it. The forced misjump is defined either as being scripted or as having maximum climb rate at the moment the countdown reaches zero. From the source:
BOOL misjump = [self scriptedMisjump] || ((flightPitch == max_flight_pitch) || (malfunc && (randf() > 0.75)));
The control method should not matter. If you cannot execute the misjump, it probably means that you are not in full climb at zero. Is the climb indicator all the way up?
Edit: Checked it with the mouse. Indeed, with mouse (and probably joystick too), we do not achieve the full climb rate. Maybe that's a little bug there.
Last edited by another_commander on Fri Nov 19, 2010 9:18 pm, edited 1 time in total.
