17.09.2008, 16:36
I have an idea I would like to ask about
I love the new objects, I love the new ships, but for the life of me I can't figure out how to merge multiple static.ini, etc in a form that would be universally acceptable to AAA for inclusion into the Unified Installer, so I can't make missions using the new objects until this is resolved.
So here my Idea, Have the wrapper merge static.ini similar to the way it picks mods over originals then assign initials to object developers just like you did maps.
If we had Lal_RONE's objects he would include a LR1_static.ini. and Cannon's objects would include a CAN_Static.ini, and FC's ShipPack2 would include an FC__Static.ini, then when wrapper ran it would append the multiple ini files into the single Static.ini file IL2 recognizes.
Do the same for all the ini and properties files. If AAA had an agreed upon convention it wouldn't even NEED to parse the files so it would be faster.
what do you think oh mighty AAA?
I love the new objects, I love the new ships, but for the life of me I can't figure out how to merge multiple static.ini, etc in a form that would be universally acceptable to AAA for inclusion into the Unified Installer, so I can't make missions using the new objects until this is resolved.
So here my Idea, Have the wrapper merge static.ini similar to the way it picks mods over originals then assign initials to object developers just like you did maps.
If we had Lal_RONE's objects he would include a LR1_static.ini. and Cannon's objects would include a CAN_Static.ini, and FC's ShipPack2 would include an FC__Static.ini, then when wrapper ran it would append the multiple ini files into the single Static.ini file IL2 recognizes.
Do the same for all the ini and properties files. If AAA had an agreed upon convention it wouldn't even NEED to parse the files so it would be faster.
what do you think oh mighty AAA?