MCAR future development

[Sa8Gecko]

I cannot guarantee it, but the final (1.0 version, non beta)
would be a stand-alone pbo, that is addon makers would
not have to include the scripts in their pbo files, but it
will suffice for them to write a global array in config.cpp
containing all the information to launch and guide the
missile: custom missile type or an existing MCAR one, max
speed, acceleration-deceleration curve, max range, guidance
code (even custom ones, provided they're written the right
way) and so on.
Having the latest MCAR files installed (few kb, excluded the MCAR
standard missiles and units, that will be optional), the user
won't need anymore to downlad a huge pack containing
the fixes for the MCAR scripts, and the same way the
addon maker won't need to upload a huge fix file.
I hope it would be as easy as setting standard missiles
parameter in config.cpp: well, actually a little more complicated
because you'll need to specify the guidance code you'd
prefer the missile to have (blank for standard one, though), but more flexible.

Well, you are encouraged to leave your suggestions/critics
below.

[Sa8Gecko]

about the global array mentioned above:
this would be set by calling a function from the init eventhandler.
The function itself will be written above a template we
(PSYProd.) will distribute along with the 1.0 version.
The addon maker would be required to simply fill in the
blanks with its chosen missile parameters, i.e.:

...
_maxspeed = ;
_maxTurnRate = ;
_acceleration = ;
...

and then tag the function and make a call from the init
eventhandler itself to this function to define a tagged
global array which will be used by our scripts.
This should be as easy (if not more) as setting the parameters
for a normal OFP missile (initspeed, maxRange and so on)