Battlezone Forums

Hmm, turretEnemy3 and 4 seem to work in mpi too.
I used to know all this stuff.
1st test on mpi fever. Result: Mr2's lame noob butt on a plate

what was the form of the mpic_???? unit definitions? ie both races hmmm mpic_ivtank_fvtank ?
Probably not a good idea to use them, in case it goes funny with mods.

There is a way to use generic pathpoints, but I am not sure if the following format is correct.
mpic_*vturret

Something like that forces the dll to try and use a unit for the used AI race.
But I advice you to search the modlogs before actually using it ..

weird, they are not specified in the code; preplaced, maybe?

Also redid the mpic*/mpih* pathpoint code, used between IA, MPI
DLLs. It can support only one item, e.g. a name of "mpic1_ivturr", or
the more traditional "mpic1_fvturr_ivturr". If it starts with
mpic/mpih, it checks the ODF(s) specified, and builds them only if the
race matches the current cpu/human team. Alternatively, if it starts
with mpiC/mpiH (note the capitalization!), it replaces the first
character of the ODF(s) [note the pural!] with the current race of the
team, and builds the object(s). This allows you to do something like
"mpiC1_*vturr", which will build a CPU turret of the current CPU race,
no matter what the CPU race is. [NM]

weird, they are not specified in the code; preplaced, maybe?

I don't know it all gets a bit confusing what with turrets spawning at gtow points and moving to hold positions as well.
They are not preplaced.
I think the "mpiC1_*vturr" is probably the thing to use, it will work ok as long as modders use the standard naming conventions.

it probably does that since, unlike spires, gtows are not self-powered.

BuildStartingVehicle(m_CPUTeamNumber, m_CPUTeamRace, "*bspir", "*vturr", "gtow2");
BuildStartingVehicle(m_CPUTeamNumber, m_CPUTeamRace, "*bspir", "*vturr", "gtow3");

linked to some more mpi map conversions in the first post.

I assume these maps also contain the 1.3 path points for AI assault towers and anti-air?

- Edit NVM I read previous posts.

Do you mind if I use these in my mod?

It seems there is a need to add some custom units, specifically fvartl with poppers and laser poppers. maybe even a cpu only one with gas too.
Scion cpu team have no air defense in their stock state other than fvturr's.

MrTwosheds wrote:It seems there is a need to add some custom units, specifically fvartl with poppers and laser poppers. maybe even a cpu only one with gas too.
Scion cpu team have no air defense in their stock state other than fvturr's.

Scion CPU's can start with Scion Rocket Towers if the Path is found by the DLL.

Yes. But I was trying to do these maps with just the traditional stock units and I notice that there are no fvartl variants.
There is an ivrcktaa, an ISDF rocket tank with hornet.
Just to give a cpu base a basic defense rather than the GH style fortress.

Not only that, the tower is a 'works untill destroyed' defensive feature and wont be rebuild while the AI-ISDF will rebuild lost AA-Rtanks. Not even mentioning its other limitations.

It will not rebuild ivrcktaa the aip does not build these. It certainly won't park them on top of mountains. And it won't send them off to attack.
I'm not trying to build massive defenses, just give the cpu a limited defense to start off with.

good catch; i have them in the base map, but hadn't finished copying the mpic/mpiC/mpih/mpiH path points to the rest of the maps yet. :-/ should have left a note for myself after i took a break from it. i think i'll leave the gh path points out for now, though (at least on the small maps).

i've made the isdf half of the gh aip's so far, so i'll be sure to add some gh scion units.

Just use the Hold Priority? I'm sure it will re-build if it's missing a defensive unit. + If you're converting maps, you can put the necessary path point in for the hold plan

hold priority? saw the missing path points in logs h-b sent me.