criminal cargopods

Discussion and information relevant to creating special missions, new ships, skins etc.

Moderators: winston, another_commander

Post Reply
User avatar
Commander McLane
---- E L I T E ----
---- E L I T E ----
Posts: 9520
Joined: Thu Dec 14, 2006 9:08 am
Location: a Hacker Outpost in a moderately remote area
Contact:

criminal cargopods

Post by Commander McLane »

I just found the last offender for producing unscoopable, criminal cargopods (at least the last on my system). It's the nubarrel from aegidian-special.oxp. I had inserted the explicit scan_class CLASS_CARGO in all shipdata from Cargo&Wrecks.oxp and Pods.oxp, but still got a criminal cargopod every once in a while. Turns out I had missed the nubarrel.

Cargopods need their scan_class explicitely set if they're spawned by script. If generated normally they get the correct scan_class from the engine.
User avatar
Eric Walch
Slightly Grand Rear Admiral
Slightly Grand Rear Admiral
Posts: 5536
Joined: Sat Jun 16, 2007 3:48 pm
Location: Netherlands

Re: criminal cargopods

Post by Eric Walch »

Commander McLane wrote:
....Turns out I had missed the nubarrel.
That should be fixed long ago. From the readMe:
History:
v 1.2 Moved Energy unit from standard to optional equipment because some Oolite versions handled it wrong.
v 1.1 Added cargo class to the container so it will work properly with Oolite 1.70+
v 1.0 original release
User avatar
Commander McLane
---- E L I T E ----
---- E L I T E ----
Posts: 9520
Joined: Thu Dec 14, 2006 9:08 am
Location: a Hacker Outpost in a moderately remote area
Contact:

Re: criminal cargopods

Post by Commander McLane »

Eric Walch wrote:
Commander McLane wrote:
....Turns out I had missed the nubarrel.
That should be fixed long ago. From the readMe:
History:
v 1.2 Moved Energy unit from standard to optional equipment because some Oolite versions handled it wrong.
v 1.1 Added cargo class to the container so it will work properly with Oolite 1.70+
v 1.0 original release
Which probably means that I'm still using v 1.0. :oops:
Post Reply