For information and discussion about Oolite.
https://bb.oolite.space/
Change the condition "galaxy_number lessthan 4" into "galaxy_number lessthan 5". But you have to do it also in the shipData.plist I think. (depending on the testversion you ae using.) I was in galaxy 5 and had to change the last version at several places to test the program in an unintended system.I'm in Galaxy 4 and even
Thanks Eric for answering this question.I'm in Galaxy 4 and even when I'm at a TL 10 Democratic system there is a distinct lack of local heros.
The mission were offered in Confederacy systems! Not in Democracies. Sorry I have to read it carefully.I'm in Galaxy 4 and even when I'm at a TL 10 Democratic system there is a distinct lack of local heros.
It was a lot of work, but I got a lot of help from Eric Walch. His hints about problems in the script and shipdata (and often a solution for that) are a source of wisdom. And his work in updating the WIKI is also a great one.Pretty spectacular for a first OXP.
Sorry. I really don't know. I think it will, because the OXP doesn't use any untested or totally new commands. Maybe one of the good guys can clear this? Or test it on your own and give me a call.Does it work in 1.65?
Code: Select all
"setDesiredRangeTo: 12000.0", performFlee does not work*
performFlee, "setDesiredRangeTo: 12000.0" works*
but
"setDesiredRangeTo: 12000.0", performIntercept works*
performIntercept, "setDesiredRangeTo: 12000.0" does not work*
* as intended in the harkovraidAIsCode: Select all
- (void) setDesiredRangeTo:(NSString *)rangeString
{
desired_range = [rangeString doubleValue];
}
Code: Select all
- (void) behaviour_intercept_target:(double) delta_t
{
double range = [self rangeToPrimaryTarget];
desired_speed = maxFlightSpeed;
if (range < desired_range)
[shipAI reactToMessage:@"DESIRED_RANGE_ACHIEVED"];
else .......
Code: Select all
- (void) behaviour_flee_target:(double) delta_t
{
double range = [self rangeToPrimaryTarget];
if (range > desired_range)
[shipAI message:@"REACHED_SAFETY"];
else ......
Thanks Eric,So this means that you even can change the desired_range during the intercept or flee. When it didn't work for you, you probably redefined the range in an other part of the state. But to prevent starting with a range of zero, better define the range first.
I've installed V1.65 and played some missions. The Oxp seems to work under V1.65.In the first post you wrote that this OXP is for 1.69. I'm still on 1.65 but would like to play this one. Does it work in 1.65?
Yes, totally right. And always with a smile. Thanks a lot.That's what I really like about this community, unselfish colaboration and helping each other.
I think it is a feature, but I never saw these problems. But after performAttack, the ship can have about 5 different behaviors. With the 1.69.1 debugging key you can see the current behavior of the ship. Maybe this gives a clue to the problem. Maybe it could come from the physics of the ship itself. Has an other ship the same problem?I've posted it before: NPC attacking slow moving vessel. If a NPC (already got a target) should execute performAttack he often got some trouble with facing the target. Is performAttack broken or is it a feature?
No but on the wiki it usually tells you when it is a post 1.65 command. And there are very few new commands with normal scripting so most 1.69 things will work under 1.65I've installed V1.65 and played some missions. The Oxp seems to work under V1.65.
Is there a list out there under which version methods/messages are introduced or deprecated?
Thanks Eric. But that's why I'm wondering. It doesn't matter what kind of ship it is. But it only happens if there are more than one of them on the run (pirate ambush for example). I tried it without installed OXPs, with some of them and with my own one. With Version 1.65 and 1.69.1-test. Always the same. Some of them didn't get the right direction.I think it is a feature, but I never saw these problems. But after performAttack, the ship can have about 5 different behaviors. With the 1.69.1 debugging key you can see the current behavior of the ship. Maybe this gives a clue to the problem. Maybe it could come from the physics of the ship itself. Has an other ship the same problem?