Why shouldn't it be possible to include conditions in death_actions? However I'm not so sure that setDesiredRangeTo and scanForShipsWithRole would work, as they are AI-methods, not general methods. Have you tested that?Arexack_Heretic wrote:Is it really impossible to include conditions in death_actions?
The script_actions can (As in the cloakingdevice).
The two entries seem similar in function.
I would try this (but have not the time to test it) :Code: Select all
<key>death_actions</key> <array> <string>setDesiredRange: 50000</string> <string>scanForShipsWithRole: player</string> <dict> <key>conditions</key> <array> <string>shipsFound_number morethan 0</string> </array> <key>do</key> <array> <string>set: mission_conhunt CONSTRICTOR_DESTROYED</string> </array> </dict> </array>
How did that happen?
Moderators: winston, another_commander
- Commander McLane
- ---- E L I T E ----
- Posts: 9520
- Joined: Thu Dec 14, 2006 9:08 am
- Location: a Hacker Outpost in a moderately remote area
- Contact:
@ generally: the killing of the Constrictor gives you exactly 256 kills as a reward. (It's been long, long ago, but I think I remember in C64-Elite killing the Constrictor was the moment I became ELITE.)
- Arexack_Heretic
- Dangerous Subversive Element
- Posts: 1876
- Joined: Tue Jun 07, 2005 7:32 pm
- Location: [%H] = Earth surface, Lattitude 52°10'58.19"N, longtitude 4°30'0.25"E.
- Contact:
I haven't tested it. I said so.
I think I'll have some time this afternoon though,
so I'll test it in the rubberduckship I'm testing with a simple "commsMessage: you killed me!" in stead of "set: Mission...."
If it doesn't work, maybe putting it in the AI could work.
Tricky bit is triggering it before the entity is gone, but after energylow. Using EXIT =(); might do the job.
I think I'll have some time this afternoon though,
so I'll test it in the rubberduckship I'm testing with a simple "commsMessage: you killed me!" in stead of "set: Mission...."
If it doesn't work, maybe putting it in the AI could work.
Tricky bit is triggering it before the entity is gone, but after energylow. Using EXIT =(); might do the job.
Riding the Rocket!
- Arexack_Heretic
- Dangerous Subversive Element
- Posts: 1876
- Joined: Tue Jun 07, 2005 7:32 pm
- Location: [%H] = Earth surface, Lattitude 52°10'58.19"N, longtitude 4°30'0.25"E.
- Contact:
Code: Select all
<key>death_actions</key>
<array>
<string>setDesiredRange: 50000</string>
<string>scanForShipsWithRole: player</string>
<dict>
<key>conditions</key>
<array>
<string>shipsFound_number morethan 0</string>
</array>
<key>do</key>
<array>
<string>commsMessage: you killed me!</string>
</array>
<key>else</key>
<array>
<string>commsMessage: this doesn't work! :(</string>
</array>
</dict>
</array>
I'll test again.
I get this again at PBR.
Conditions work, so the role 'player' does not work probably.
Ideas?
Riding the Rocket!