Oo-Haul - random escort missions (v.1.5)

[Lestradae]

Hey people!

Which AI do you mean? The OXP, as downloaded via the wiki OXP page, contains only 'oohaulAI', 'oohaulmisgoAI', and 'Pi-42SandwichBoardAI'.

It is the 'Pi-42SandwichBoardAI' although i think that the reason is inside the shipdata plist

Wow!

I just noted an old copy & paste error I made back in the very first days of Realistic Shipyards: It also contains the oohaulAI and Pi-42SandwichBoardAI!



I really have to apologize there ... do some of you people have RS installed? Then that could be the culprit by overwriting stuff with older versions of those AI's!

I did want to put in the Oo-Hauler ship, but forgot and then forgot to take out the already copied files again

But, how the juggernaut.dat found its way into the oo-haul oxp is a mystery to me. It's from RS, an altered version of the Behemoth model.

Will obviously take this out for OSE, for the moment I guess you will have to rename the AI if it shall stay compatible with RS (which's download numbers are now beyond the number of registered people on this board)



L

[Commander McLane]

I would guess because it may be overwriting something from YAH.oxp. I can't say, though, whether it's a necessity to have it loaded after YAH.

Well it does not.
The script of oohaul search for a ship with the role constore, constores added in the game by the script of youradhere. I assume that Dc Nill wanted to be sure that the script of youradhere will run before the script of oohaul. This is the only logical explanation, for why he did this, that i can see.

Which would have been a wrong assumption of his. The order scripts are run with is purely random, and has nothing to do with the order the OXPs are loaded with. The only things that are affected by the loading order are non-script property lists (like shipdata), AIs, models, textures, images, and sounds. In short: everything that is not a legacy script. This would only be overwritten by another script with the same name, but this does not seem to be the case between OOHaul and YAH.

But if you want to know Dr Nil's reason for naming the OXP as he did, I would suggest that you simply dig up the OOHaul thread in the Expansion Pack forum, and read it. It will certainly contain an explanation.

[Ark]

But if you want to know Dr Nil's reason for naming the OXP as he did, I would suggest that you simply dig up the OOHaul thread in the Expansion Pack forum, and read it. It will certainly contain an explanation.

The name? ZZ because space truckers listen to ZZ Toop? Zz because simulations may cause drowsiness in todays give-me-it-all-before-now culture? Nah - just easier to have the script read after the script in Your Ad Here!.

You are right. Me bad

[Ark]

Now that the task with the new version of youradhere is over I will continue the update of oohaul

Things I have done so far:
1.Change the deprecated command "scriptActionOnTarget" with "safeScriptActionOnTarget" in the AI of the mission ship (It works fine!!)
2.Escort missions can be offered now in all constore types not only pi-42s
3.Some minor bug fixes in the shipdata plist

Things that is still broken:

1.The pi-42 clerk does not function properly (although is not essential for the missions, its existence is only for giving you the hint that an escort mission is waiting for you in the constore). I suspect that the Pi-42SandwichBoardAI.plist is not responsible but somehow the

Code: Select all

<key>like_ship</key>
<string>escape-capsule</string>

inside the shipdata plist do all the damage. It does not transmit the messages inside its AI and you can even scoop it and get a slave !!!

2.Something must be wrong with the death actions of Oohauler_crate01 although I am pretty sure that it worked in the past (previous version of oolite or the oxp)

Code: Select all

	<key>Oohauler_crate01</key>
	<dict>
		<key>ai_type</key>
		<string>nullAI.plist</string>
		<key>death_actions</key>
		<array>
		      <string>spawn: oohaulcargo 15</string>
		</array>
		<key>likely_cargo</key>
		<integer>20</integer>
		<key>max_cargo</key>
		<integer>50</integer>
		<key>max_energy</key>
		<real>150</real>
		<key>model</key>
		<string>Oohauler_crate01.dat</string>
		<key>name</key>
		<string>Oohaul Crate</string>
		<key>roles</key>
		<string>Oohauler_crate01</string>
	</dict>
	<key>oohaulcargo</key>
	<dict>
		<key>scanClass</key>
		<string>CLASS_CARGO</string>
		<key>roles</key>
		<string>oohaulcargo</string>
		<key>ai_type</key>
		<string>dumbAI.plist</string>
		<key>bounty</key>
		<integer>1</integer>
		<key>cargo_type</key>
		<string>CARGO_SCRIPTED_ITEM</string>
		<key>energy_recharge_rate</key>
		<real>0.0</real>
		<key>forward_weapon_type</key>
		<string>WEAPON_NONE</string>
		<key>likely_cargo</key>
		<integer>0</integer>
		<key>max_cargo</key>
		<integer>0</integer>
		<key>max_energy</key>
		<real>1</real>
		<key>max_flight_pitch</key>
		<real>0.5</real>
		<key>max_flight_roll</key>
		<real>0.5</real>
		<key>max_flight_speed</key>
		<real>50</real>
		<key>missiles</key>
		<integer>0</integer>
		<key>model</key>
		<string>barrel.dat</string>
		<key>name</key>
		<string>Cargo container</string>
		<key>thrust</key>
		<real>0.0</real>
		<key>unpiloted</key>
		<true/>
		<key>weapon_energy</key>
		<real>0.0</real>
		<key>weapon_offset_x</key>
		<real>0.0</real>
		<key>script_actions</key>
		<array>
				<string>awardCargo: 1 Computers</string>
		</array>
	</dict>

it seems that the 15 cargo crates connot be spawed anymore.
Moreover i am unable to understand why he uses script actions when the crates always give you a computer. It would be replaced with

Code: Select all

<key>cargo_type</key>
<string>CARGO_COMPUTERS</string>

Any help in the above 2 problem will be appreciated
Also if any of you had detect any other bugs now it is a very good time to share that knowledge with the rest of us

[DaddyHoggy]

@Ark see here: https://bb.oolite.space/viewtopic.php?t=2888

Me and Doc never got to the bottom of the dodgy cargo spawning.

It would seem there are no images in this thread as my homepage.ntlworld homepage is no longer accessible

[Ark]

The situation with the not spawned cargo can be easily corrected via JS but this means that the new version of oohaul will not be compatible with the last stable so I want at least try fixing it traditionally. The bad thing is either I am blind or the reason for that is not so obvious. HELP!!

[dima]

Do the escort missions of the (current) oo-haul version downloadable from the Wiki work with Oolite 1.72.2?

[Ark]

Do the escort missions of the (current) oo-haul version downloadable from the Wiki work with Oolite 1.72.2?

Yes but the offered only in a PI-42 constore

[dima]

Hm, sounds not too bad - is there any problem in that?

[Ark]

Hm, sounds not too bad - is there any problem in that?

Yes the problem is that are more 4 types of constores appart from the Pi-42 constore

[dima]

...so that makes those missions too rare?

[Ark]

...so that makes those missions too rare?

yes!!

[dima]

[dima]

Something else I wanted to ask about this oxp,

Is there any way to get the escort missions without Your Ad Here? Or would it be possible for me to alter the script so that the missions are offered on any normal station? I really like the idea of escort missions but do not use the Your Ad Here modification so I can't get escorts (rare or not rare as I don't have the constores.

[DaddyHoggy]

@dima - you could (I think) but it would make no sense - the Oo-hauler missions (IIRC) are in-system escort missions - you go from the Constore at the WSB to the Main Station, for those who prefer a more sedate pace...