AI rebuilding level 2 pods when level 3 are already there -1 reply

Please wait...

mutrumbo

The new guy

50 XP

12th October 2008

0 Uploads

12 Posts

0 Threads

#1 12 years ago

You all know how I can stop the AI's from building new level 2 pods when they've already upgraded to level 3 pods on that upgrade station?




086goinfast

NObama

50 XP

6th March 2006

0 Uploads

9,633 Posts

0 Threads

#2 12 years ago

Just remove the double entries from the AIP files for the level 2 pods.




mutrumbo

The new guy

50 XP

12th October 2008

0 Uploads

12 Posts

0 Threads

#3 12 years ago

There isn't a double entry. Here's an example:

"tosfupgrade", 1,0, -1, 5, // ship upgrade station "tosfwantcon", 3,0, 1, -6, // "tosfconsti_up1", 2,0, 1, 0, // "tosfedpod11", 1,0, -1, 0, // weapon upgrade level 2 "tosfconsti_up1", 2,0, 1, 0, // "tosfedpod12", 1,0, -1, 0, // shield upgrade level 2 "tosfconsti_up1", 2,0, 1, 0, // "tosfedpod14", 1,0, -1, 0, // engine upgrade level 2 "tosfconsti_up1", 2,0, 1, 0, // "tosfedpod13", 1,0, -1, 0, // sensor upgrade level 2 "tosfconsti_up1", 2,0, 1, 0, // "tosfedpod15", 1,0, -1, 0, // life support upgrade level 2 "tosfconsti_up1", 2,0, 1, 0, //

"tosfedpod21", 1,0, -1, 0, // weapon upgrade level 3 "tosfconsti_up1", 3,0, 1, 0, // "tosfedpod22", 1,0, -1, 0, // shield upgrade level 3 "tosfconsti_up1", 3,0, 1, 0, // "tosfedpod24", 1,0, -1, 0, // engine upgrade level 3 "tosfconsti_up2", 3,0, 1, 0, // "tosfedpod23", 1,0, -1, 0, // sensor upgrade level 3 "tosfconsti_up2", 3,0, 1, 0, // "tosfedpod25", 1,0, -1, 0, // life support upgrade level 3

For some reason, as soon as it builds the Weapon Upgrade level 3, it then builds another Weapon Upgrade level 2 on an outcropping already occupied by another pod.

Then, it'll build the Shield Upgrade level 3. Then, the Shield Upgrade level 2. And, so on with Engine, Sensor, and finally Life Support.

So, what I get is it building 15 pods to get the full 10 want.

Pretty strange too... I can click both the level 2 and 3 pods on each outcropping after they're complete.




mutrumbo

The new guy

50 XP

12th October 2008

0 Uploads

12 Posts

0 Threads

#4 12 years ago

And, I realize that changing the lines to read like

"tosfedpod12", 1,0, 1, 0, // shield upgrade level 3

would eliminate that problem.. but it would also make it so that if one of the level 2's were destroyed, the level 3 would never be made...which isn't what I want either.




rifraf

Avid Gamer, Novice Modder

50 XP

24th July 2003

0 Uploads

180 Posts

0 Threads

#5 8 years ago

Sorry to dig up an old thread, but I noticed my game doing this too. I've been doing some modding of it but nothing to research except changing the latinum/dilithium/metal quantities and they do rebuild the pods over and over like stated above. haven't found any other threads about this either.

I never noticed this in stock but can't say I was looking but now that I really watch it it's a waste of resources to do this instead of build ships. Did anyone ever find a fix? The double entries in some files were already // commented out but I deleted them anyway to no avail.

The Cardassian upgrade station only has 5 hardpoints so I assume it is building a pod on 1 then rebuilding another pod on the same one and so on? Can you build 2 things on the same hardpoint? The Kling and Rom stations have 9 or 10 hardpoints but I noticed them rebuilding the same pods over and over as well.




rifraf

Avid Gamer, Novice Modder

50 XP

24th July 2003

0 Uploads

180 Posts

0 Threads

#6 8 years ago

Everyone's probably already figured this out and I couldn't find any other threads about it, but the way that seems to fix it is by adjusting the upgrade station pod builds. It won't work for the Cardassians since their upgrade station only has 5 build hardpoints, but the other races all have 10 build hardpoints.

Where it says buildItem = 0 through 4 then the next set is secondaryBuildItem = 0 through 4, change the secondary #'s to 5 through 9 and it'll use the other build hardpoints and you won't build a pod on a hardpoint already taken by a pod so it won't keep rebuilding pods over and over. They'll each have their own build hardpoint.

Species 8472 is a little different since their upgrade station has 8 build hardpoints. So change the secondaryBuildItem #'s to 4 through 7 since they have 8 upgrades total instead of 10.