aegidian ships

[Eric Walch]

I updated two oxp's with aegidian ships: aegidian-special.oxp & aegidian-x-ships.oxp: Wiki oxp index page

Both oxp's contain the same cylindrical and red cargo barrel. This barrel had no scan-class defined which did result in addition of those barrels with the default yellow scanclass when added by script. Those barrels are also not scoopeble with a default scan-class. I now added an explicit cargo scan-class to those barrels.

When Oolite itself adds barrels on death of ships it always gives them scan-class cargo and there is no problem. This is far the majority of the cases.
With Oolite 1.65 this missing scan-class was never a problem as oolites own barrels also had no scan-class defined. Therefor no scripter would think of adding a default barrel by script as this way they all were wrongly added into the system.

With current Oolite versions, all oolite's internal barrels have their scanclass defined as cargo. Scripters now can add default barrels by script. But, when hitting one of the eagidian's nu-barrels they enter the system with the unwanted default yellow scanclass.

This problem is still rare as I have only seen a few of those till now. e.g. the pirates in deep-space-pirates.oxp can spawn barrels by script in their death action.

Looking more closely at both oxp's I noticed they both contain the same barrel and asp-special. I left it this way as this does no real harm and I want it to stay as original as possible.

---
Neighter of the oxp's had a version number but I know there were several releases of at least one of them. I now gave both a version number 1.1.
I added an info.plist inside. This info file is mainly useful for mac users. On a mac an oxp is not a folder but a file. You can't simply open it as a normal folder but the info.plist makes that when you ask file-info for that file, the finder will show its version number in the info window.
Window users won't have this but they simply can open the info.plist as a text file and also read this version numbers.

[Micha]

As a more cross-platform versioning scheme, I like encoding the version-number into the name of the OXP.

eg,
myExpansion_v0.1.oxp
yourExpansion_v1.3.oxp

etc.

That way it's immediately obvious what versions of OXPs are installed - handy if you go on an OXP-updating spree on the first of the month or whatever.