MrTwosheds wrote:One of the advantages with SwitchAIP is that it allows you to make each aip simpler. Make sure they have the basic base building commands for whatever tech level the aip deals with and then add the unit builds, attacks or whatever that that particular strategic path requires. Its much easier than trying to make just one AIP that does everything.
I dont like 1 AIP either, but I do like 'switches' in my AIP's, like the no-bomber and bomber versions of my AIP's are wrapped up in 1 AIP with a simple condition to check if the B-bay should be build. I however like the AIP switching to be done from dll and in such way can make 1 AIP for building a base and the others just create units/additional defences/etc and when base-buildings get destroyed the AIP switches back or to a 'desperate defence' plan (more or less assuming the AI will never get back to a full base again).
MrTwosheds wrote:Some people find that learning a programming language is not the easiest way to put chains on a scout...
You'll need to learn it at some point, or be ok with limitations that can not be overcome with an odf/aip-edits. Plus point here is that the source-code is available and the stuff you should understand is in them. You dont want to know how long I did some basic programming without knowing about arrays, it was like a world opened up for me when I first learned about those.
The advantage with the ODF technique is that the aip maker is now in a position to alter any of the units other attributes, should he wish to.
Sure Dll's are essential, but it seems a difficult way to do something simple like change a weapon to me. The AIP I made for LOS had 3-4 tech levels to advance through as the AIP's progress, all the unit loadouts changed more than once and sometimes would even regress back to a previous tech level if it needed to. The upgraded units sometimes required different weapon masks and other tweaks that would (I imagine) be quite difficult to do via dll.
The Silence continues. The War Of Lies has no end.
By simply removing an 'installed weapon' you force the unit to use its other weapons. You can also remove the HP's from the ODF, but that means you cant install weapons, above method leaves you a choice.
weaponMask = 00111
On a stock Sabre it would allow the AI unit to use its main cannon (the 5th number) and its chains (3rd and 4th numbers) but not its mortar or special, but It would only do this if weapon linking was enabled for that unit.
weaponMask = 00110
would prevent the AI Sabre from using its cannon and cause it to fire its chains instead.
The Silence continues. The War Of Lies has no end.
Odf's are just plain text files, any text editor can be used to create or modify one. The example at the top of the page will work if pasted into a txt file, you then rename its extension to odf. eg Mytank.txt - Mytank.odf
So a scout that has chains but only fires its missile (whatever it is) looks like this
