[Request] - Buildyard Improvements

posted on May 16th, 2011, 2:15 pm

I would like for the buildyard to transfer it's name to the unit it's constructing when construction is complete.  Currently, it looks like the name of the vessel changes because technically, the buildyard and the ship under construction are two separate units, but made to look like the same unit.  Having the buildyard transfer it's name would make it look better.

Second, I would like an ODF command to be added to the buildyard to prevent it from breaking up when construction is complete.  I did an experiment with the Nebula class and it looks like the vessel is breaking up when it finishes construction.  Maybe a command that preserves certain mesh groups within the model or only breaks up a single mesh group but causes the other groups to just disappear.

posted on May 16th, 2011, 2:45 pm

Maybe it's the headache, but i cannot figure out exactly what it is you are asking. 

posted on May 16th, 2011, 2:50 pm

Maybe it's the headache, but i cannot figure out exactly what it is you are asking. 

i think he wants to do a module system for a nebula, going from a nebula with no pod on top, installing module(s) and getting a pod. but the name changes cos currently its only used on borg uplinks.

the second thing he wants is for a line in the odf to stop the little "explosion" of parts at the end of construction.

why dont u just have your nebula refit like the generix class? theres no explosion at the end of that, and the name carries over for gens.

posted on May 16th, 2011, 3:19 pm

it is not planned to extend the buildyard for ship upgrades further. it wasn't thought to be used for that and currently only is a temporary solution for ship upgrades.
you can prevent the buildYard from breaking up with the "vanishEffect" command.
0 is default for chunk explosion
1 is a disassembling effect
2 is instant gone

as myles said, i'd recommend too to look at how we've integrated the current upgrade system

posted on May 16th, 2011, 4:47 pm

Interesting.  Do all ship refits now use that method?

posted on May 16th, 2011, 6:56 pm

nope, actually none uses it at the moment. but we had a few test implementations using it, thats probably what DOCa was refering too

posted on May 16th, 2011, 7:10 pm

the better yes, that's what i was referring too. ignore my recommendation then

posted on May 16th, 2011, 7:24 pm

Okay, I'm confused.  How do you currently require a set amount of time to refit a vessel?

posted on May 16th, 2011, 8:01 pm

It's just a yard, that's why you see a build queue. But we are working on a better solution for one of the next patches. nevertheless, it works well the way it is and should so in mods too. Check the rom_generix_spcP for reference

posted on May 16th, 2011, 9:24 pm

The buildyard would be good at saving ODFs if multiple refits are available.

i think he wants to do a module system for a nebula, going from a nebula with no pod on top, installing module(s) and getting a pod. but the name changes cos currently its only used on borg uplinks.

The only thing is that you can only select one module.  It beats giving you multiple refit ODFs plus the refit is required unless you don't mind having an un-armed Nebula running around the map.  Should Eraudi Yard + Level 2 Chassis be high enough for such a vessel?

posted on May 16th, 2011, 10:49 pm

Level 2 seems right or even a little high. Isn't the Neb chassis like 40 years old now? old tech. Could also be level 1 with a long build time.

posted on May 16th, 2011, 10:59 pm

So is the Galaxy chassis.  But the latest information we have is that both chassis were being built while Voyager was in the Delta Quadrant.  I think Starfleet stops building new ships from a chassis when the chassis is more than 60 years old.  I believe that the Sovereign chassis is 30 years old.

[Tyler]

posted on May 16th, 2011, 11:04 pm

Last edited by Tyler on May 16th, 2011, 11:06 pm, edited 1 time in total.

Galaxy is about 50, probably around 60 for the Nebula. Galaxy is younger.

Chassis level doesn't consider age, though.