Scripters cove

[Rorschachhamster]

Worked after I made the orbit height a property of the ship (satellite).
Dumbed down the AI to "Just fly around it, do not care if there's somethign in the way..."
Now I just have to spawn them randomly around the planet.... and two more models.

[GGShinobi]

Dumbed down the AI to "Just fly around it, do not care if there's somethign in the way..."

I think this is actually pretty cool! Real trains don't stop or evade, either!

[Rorschachhamster]

Dumbed down the AI to "Just fly around it, do not care if there's somethign in the way..."

I think this is actually pretty cool! Real trains don't stop or evade, either!

Oh, this is not about the trains. They should evade asteroids, stations etc. Maybe not spaceships...
I just make something inbetween to look with fresh eyes at the train AI and I think I stumbled about what's the problem already...

[HAL]

Hello everyone,

Today I tried to write an OXP...

I followed the tutorial on the wiki, and got nothing. Because the mac was awkward with file saving, I had a go with my old linux laptop, and still, nothing. Then I copied and pasted a sample requires.plist, to no effect. I then altered a copy of oldships, so that there was only the player cat ship, and renamed it, gave it roll and pitch of 2, and made it cost 4 credits for testing. Still nothing. I think I must be doing something drastically wrong, but can't tell what. Any ideas?

[Smivs]

Can you post your latest log please?

[HAL]

How do I find the log? And while we're on the subject, what is a log? Sorry, I just don't have a background in programming

[HAL]

Ah, found it!

20:47:13.275 [plist.parse.failed]: Failed to parse /Users/.../Documents/Oolite 1.77/AddOns/erubadhron.oxp/Config/shipdata.plist as a property list.
Close tag on line 169 does not match open tag plist
20:47:13.849 [shipData.load.shipyard.unknown]: ----- WARNING: the shipyard.plist entry "erubadhron" does not have a corresponding shipdata.plist entry, ignoring.

[Smivs]

OK, so two problems, one with the shipdata.plist and one with the shipyard.plist, which could be a shipdata error as well.
Can you post the shipdata.plist here inside 'Code' tags (you'll find a button for these above where you type your comment).

[HAL]

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>erubadhron</key>
	<dict>
		<key>aft_eject_position</key>
		<string>0.0 -7.2 -6.0</string>
		<key>energy_recharge_rate</key>
		<real>3</real>
		<key>exhaust</key>
		<array>
			<string>5.0 0.0 -28.0 3 4 10.0</string>
			<string>-5.0 0.0 -28.0 3 4 10.0</string>
		</array>
		<key>forward_weapon_type</key>
		<string>WEAPON_BEAM_LASER</string>
		<key>laser_color</key>
		<string>yellowColor</string>
		<key>max_cargo</key>
		<integer>2</integer>
		<key>max_energy</key>
		<real>384</real>
		<key>max_flight_pitch</key>
		<real>2</real>
		<key>max_flight_roll</key>
		<real>2</real>
		<key>max_flight_speed</key>
		<real>365</real>
		<key>max_missiles</key>
		<integer>4</integer>
		<key>missile_launch_position</key>
		<string>0.0 -1.5 12</string>
		<key>missiles</key>
		<integer>1</integer>
		<key>model</key>
		<string>cat.dat</string>
		<key>name</key>
		<string>Cat Mark I</string>
		<key>roles</key>
		<string>player</string>
		<key>subentities</key>
		<array>
			<string>catwing	0.0 0.0 0.0	    1 0 0 0</string>
			<string>catwing	0.0 0.0 0.0	    0 0 0 1</string>
		</array>
		<key>thrust</key>
		<real>45</real>
		<key>view_position_aft</key>
		<string>0.0 9.0 -30.0</string>
		<key>view_position_forward</key>
		<string>0.0 9.0 8.0</string>
		<key>view_position_port</key>
		<string>-7.0 9.0 8.0</string>
		<key>view_position_starboard</key>
		<string>7.0 9.0 8.0</string>
		<key>weapon_position_aft</key>
		<string>0.0 0.0 -30.0</string>
		<key>weapon_position_forward</key>
		<string>0.0 4.6 30.0</string>
		<key>weapon_position_port</key>
		<string>-10.0 0.0 15.0</string>
		<key>weapon_position_starboard</key>
		<string>10.0 0.0 15.0</string>
		<key>custom_views</key>
		<array>
			<dict>
				<key>view_description</key>
				<string>External View 1</string>
				<key>view_position</key>
				<string>0.0 40.0 -200.0</string>
				<key>view_orientation</key>
				<string>1.0 0.0 0.0 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 2</string>
				<key>view_position</key>
				<string>140.71 40.0 -140.71</string>
				<key>view_orientation</key>
				<string>0.9239 0.0 0.3827 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 3</string>
				<key>view_position</key>
				<string>200.0 40.0 0.0</string>
				<key>view_orientation</key>
				<string>0.7071 0.0 0.7071 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 4</string>
				<key>view_position</key>
				<string>140.71 40.0 140.71</string>
				<key>view_orientation</key>
				<string>0.3827 0.0 0.9239 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 5</string>
				<key>view_position</key>
				<string>0.0 40.0 200.0</string>
				<key>view_orientation</key>
				<string>0.0 0.0 1.0 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 6</string>
				<key>view_position</key>
				<string>-140.71 40.0 140.71</string>
				<key>view_orientation</key>
				<string>0.3827 0.0 -0.9239 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 7</string>
				<key>view_position</key>
				<string>-200.0 40.0 0.0</string>
				<key>view_orientation</key>
				<string>0.7071 0.0 -0.7071 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
			<dict>
				<key>view_description</key>
				<string>External View 8</string>
				<key>view_position</key>
				<string>-140.71 40.0 -140.71</string>
				<key>view_orientation</key>
				<string>0.9239 0.0 -0.3827 0.0</string>
				<key>weapon_facing</key>
				<string>FORWARD</string>
			</dict>
		</array>
	</dict>
	<key>catwing1</key>
	<dict>
		<key>ai_type</key>
		<string>nullAI.plist</string>
		<key>energy_recharge_rate</key>
		<real>1.5</real>
		<key>forward_weapon_type</key>
		<string>WEAPON_MILITARY_LASER</string>
		<key>laser_color</key>
		<string>orangeColor</string>
		<key>max_energy</key>
		<real>60</real>
		<key>model</key>
		<string>catwing.dat</string>
		<key>name</key>
		<string>Cat Wing</string>
		<key>roles</key>
		<string>catwing</string>
	</dict>	
		</dict>
</dict>
</plist>

[Smivs]

Aaaargh! Sorry, but I really can't read XML plists! It looks like you might have closed too many dictionaries (</dict>) at the end but without going through the whole thing which will take time, I can't say for sure. Maybe someone happier with XML will see this. I'll get back to you later when I've had a chance to look at it if not.
Oolite itself and most OXPs no longer use XML (although it is perfectly OK) because it is so cumbersome. If you are going to get into OXPs take a look at the preferred openStep format - maybe download a newer ship OXP as a template, or just look at the core game's plists in the resources folder.
openStep is a much more compact and human-friendly format which makes it easier to write and easier to bugfix in my opinion.

[HAL]

Okay, I'll try deleting a </dict> or two, and if that doesn't work I'll try modifying a core plist as an OXP as you suggested. I thought XML looked a bit easier, plus the fact that it's the only one in the tutorial on the wiki... I'd better change then! Thanks

[HAL]

YES! Somehow, it works. For some reason, I applied the change, checked, nope. Got cabal common library for snoopers to work, and saw my ship!

[Thargoid]

Modifications within OXPs aren't picked up unless you start the game with the shift key held down. Otherwise the cached version from before the modification will continue to be used instead. But the game does detect if an OXP is added, removed or renamed. It then marks the cache as stale and rebuilds it automatically.

It sounds like your snoopers change caused a cache rebuild which also caused your other mod in this OXP to also get picked up too.

[HAL]

Maybe that was it... but I did do that always_flush_cache secret setting thing, so it should have refreshed it anyway.

[Smivs]

Glad it's working