You use it when you want 1 cons to build several buildings in succesion. For a single building I would not use it (iirc it has no use).
It may become more effective when you build 2 cons, one for building and one for fieldwork and want to prevent the AIPs using fieldcons to build say a GT in the base, which than may also stall the rest of the plans from triggering untill it has done its job.
The way I do bases it by placing paths on the map and allowing the cons to build a proper base before any is send out. If something changes while 1 cons is doing fieldwork, it likelly is still busy if a previous buildplan is triggered and so the one in the base is again used.
Code: Select all
[Plan1]
planType = "BaseBuildMinimums"
planPriority = 100
buildType1 = "ibpgen"
buildCount1 = 1
buildLoc1 = "power"
buildType2 = "ibpgen"
buildCount2 = 1
buildLoc2 = "power2"
buildType3 = "ibpgen"
buildCount3 = 1
buildLoc3 = "power3"
This wil build 3 Pgens at the specified locations, wont build a 4th, and will revert back to building at the specified locations when one of those Pgens gets knocked out. The risk of using paths however is that you probably dont want anything to be build outside any paths as than you may prevent other buildplans from executing properly (although that can again be avoided by carefully setting up -all- AIPs to build in a very specific order).
In other words, have yet to see a reason why you would want to build stuff from a loop as it at most would slow down your AIP from calling its plans.
