Oolite Bulletins

Am i right in thinking its possible to equip a ship with more than 1 front laser if so what the syntax needed for the shipdata.plist file? I've had a go but can't get it working

sabre wrote:

Am i right in thinking its possible to equip a ship with more than 1 front laser if so what the syntax needed for the shipdata.plist file? I've had a go but can't get it working

Unfortunately not. I believe that player ships can only have a single laser mounting on any one facing (buy a Wolf Mk. II and see). I think this was hard-coded in, so the only way to overrule it is to alter the source code.

Captain Hesperus

…but it is possible for NPC ships, by simply gluing a bunch of ships together (aka using subentities).

Great I'll try that. As it happens the ship is made up of subs ents so should be easy

can that be made to work for pc's?

Cool that sub ent thing works. When im done I 'll stick a copy of the ship on the web. It's kinda based on the Liberator from Blakes 7. Will have 4 front mounted lasers when it completed.

I've put the Liberator under:

http://www.leebennett.force9.co.uk/oolite

With its 4 fronted mounted military lasers. It needs work be a good start....

sabre wrote:

When im done I 'll stick a copy of the ship on the web. It's kinda based on the Liberator from Blakes 7. Will have 4 front mounted lasers when it completed.

You bloody sadist , I want one, let me at them thar thargoids.

Ahruman wrote:

…but it is possible for NPC ships, by simply gluing a bunch of ships together (aka using subentities).

Aha! Would that be why I sometimes seem to blow wings off Iguanas and Cats?

hmmmm, now i'll have to try that one out. ^^

Man, that's nice work. Kudos for getting the poly cont nice and low and still making a pretty ship.

Texture needs a little work, but damn you kick ass. Love the glowy reactor power engine thingy.

Your right the texture needs some work but to be honest they aren't really my thing.

Some notes from the head nit-picker:

• Please give your files and ships unique names. Names like “rear.png” are very bad, because the chance of someone else using that name are very high. A good name would be “sabre-liberator-rear.png”. The same goes for the DAT files, and the ship key in shipdata.plist – “sabre-liberator”, “sabre-liberator-port-sub” etc. would be better than “liberator”, “lib-port-sub” etc. If you call bits of your model “center.dat”, there will be an OXP conflict at some point.
• The Liberator has both the pirate and trader roles, and the pirate AI. This means that a script using addScripts: n trader might summon a Liberator which will then behave as a pirate. The fix for this is to add <key>auto_ai</key><true /> to the shipdata.plist entry. This won’t have any effect before 1.69.1, but it won’t hurt, either. (I’m considering defaulting to true for this, rather than false.)

Thanks for the advice I'll make those changes

so let us know when we can download the new and improved model, please! =D