No death_actions with missiles

For test results, bug reports, announcements of new builds etc.

Moderators: winston, another_commander, Getafix

User avatar
Eric Walch
Slightly Grand Rear Admiral
Slightly Grand Rear Admiral
Posts: 5536
Joined: Sat Jun 16, 2007 3:48 pm
Location: Netherlands

Post by Eric Walch »

Nemoricus wrote:
Okay, what exactly worked? The AI? Or the change to the ship data?
It needs both!

I now downloaded version 4.0 and tested it. It uses the same like_ship references. That means none of the present behemoths works as intended. Only it is more visible with the mission behemoth. I wrote a small patch file that contains a altered shipdata.plist. Replace the original one with this one

But when looking in an AI trace I see:

Code: Select all

  Oolite [ai.message.receive] AI.m:353: AI hofd-nellieAI.plist for Behemoth - Nellie 237 in state 'ATTACK_SHIP' receives message 'EXIT'
  Oolite [ai.message.receive] AI.m:353: AI hofd-nellieAI.plist for Behemoth - Nellie 237 in state 'ABANDON_SHIP' receives message 'ENTER'
  Oolite [ai.takeAction] AI.m:411: Behemoth - Nellie 237 to take action launchShipWithRole: hofd-shuttle
  Oolite [ai.takeAction] AI.m:411: Behemoth - Nellie 237 to take action setSpeedTo: 0.0
  Oolite [ai.takeAction] AI.m:411: Behemoth - Nellie 237 to take action performIdle
//
Oolite [ai.message.receive] AI.m:353: AI hofd-nellieAI.plist for Behemoth - Nellie 237 in state 'ABANDON_SHIP' receives message 'ENERGY_LOW'
Oolite [ai.message.receive] AI.m:353: AI hofd-nellieAI.plist for Behemoth - Nellie 237 in state 'ABANDON_SHIP' receives message 'ATTACKED_BY_CLOAKED'
Oolite [ai.message.receive] AI.m:353: AI hofd-nellieAI.plist for Behemoth - Nellie 237 in state 'ABANDON_SHIP' receives message 'ENERGY_LOW'
Oolite [ai.message.receive] AI.m:353: AI hofd-nellieAI.plist for Behemoth - Nellie 237 in state 'ABANDON_SHIP' receives message 'DOCKING_REQUESTED'   <====== Should not happen
Oolite [ai.message.receive] AI.m:353: AI hofd-nellieAI.plist for Behemoth - Nellie 237 in state 'ABANDON_SHIP' receives message 'ATTACKED_BY_CLOAKED'
Oolite [ai.message.receive] AI.m:353: AI hofd-nellieAI.plist for Behemoth - Nellie 237 in state 'ABANDON_SHIP' receives message 'ENERGY_LOW'
Oolite [ai.message.receive] AI.m:353: AI hofd-nellieAI.plist for Behemoth - Nellie 237 in state 'ABANDON_SHIP' receives message 'ATTACKED_BY_CLOAKED'
Oolite [ai.message.receive] AI.m:353: AI hofd-nellieAI.plist for Behemoth - Nellie 237 in state 'ABANDON_SHIP' receives message 'ENERGY_LOW'
The launch command is issued. But the ship is interrupted by docking requests from far away trader escorts.
By adding my altered dockingAI back in, those escorts dock at the nearest station to them and not to the player. Almost immediately I saw Kurtz launching.

So also add my altered AI files from above message. But the problem with the escort docking should really be fixed in code not in AI for a future Oolite release
User avatar
Nemoricus
---- E L I T E ----
---- E L I T E ----
Posts: 388
Joined: Mon May 18, 2009 8:51 pm

Post by Nemoricus »

I see you also fixed the flasher code while you were at it.

Thanks for explaining what was wrong.

Also, I figured out why Nellie's AI script did not set that mission variable. If it still exists, Kurtz will return to it, and therefore not escape. It's only after it's destroyed that the variable must be set.

However, if the AI script is working properly, adding that spawn command in Nellie's death script could lead to a second copy of Kurtz's shuttle being generated.
Dream as if you'll live forever
Live as if you'll die tomorrow
Capt. Slog
Dangerous
Dangerous
Posts: 84
Joined: Sun Apr 26, 2009 10:24 pm

Post by Capt. Slog »

Eric,
Thanks for your help. I must learn how to debug these problems myself. Have posted solution on applicable forum. Perhaps you should edit out your instructions as regards capturing Kurtz?

Nemoricus,
It worked. Not a bad oxp, and you are right, it has potential to go further.
Post Reply