Split: Errors after building trunk

[Kaks]

They were removed from trunk in rev2787, Oolite doesn't need those particular .dat files anymore.
Rev2893 just reintroduced them, for oxp compatibility.

Not too sure how you managed to keep them for the OE build, but all's well that ends well!

[JensAyton]

I /do/ build from trunk and my trunk build does come with these files?!?

You should probably “make clean” every now and then. :-)

[Screet]

I /do/ build from trunk and my trunk build does come with these files?!?

You should probably “make clean” every now and then.

If you now tell me that make clean does delete resource files, I'm astonished I rather expect that svn didn't delete the unused files. Indeed I do make clean sometimes, but not everytime...

Screet

[Eric Walch]

Next two errors...

[ai.unpermittedMethod]: Handler "INCOMING_MISSILE" for state "AVOID_HAZARD_POINT2" in AI "junkAI.plist" uses "What", which is not a permitted AI method. In a future version of Oolite, this method will be removed from the handler. If you believe the handler should be a permitted method, please report it to [email protected].

[script.addShips.failed]: ***** SCRIPT ERROR: in "<system script_actions>", addShipsAt: could not add 1 ships with role "krait"

where found to have been caused by the Lave1.70 oxp.

The "krait" bug is an incompatibly between two oxps that both try to overwrite oolites own krait. Lave overwrites it to add krait to its roles, and after that another (neolites.oxp ??) overwrites it again wit a roleset without the krait role. Using a like_ship would have been a better method that avoided this incompatibility.
Overwriting internal ships is always a bad method because it only works for one oxp. When there are two doing it, you have a conflict!
(I'll upload a 1.71 version of Murgh's Lave.oxp soon)