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?
... so wrapper should read all lines ( not just a file name as it does now ), compare and fix double entries from all ini files user may have , and then merge them with preserved structure ( cos some ini files mustn't get alphabetically rearranged ) ? Is that what you're saying ?
Z
That... or two wrappers... One wrapper dedicated to that ONE type of file...
.... if someone come out with that routine ( manipulating with all types of ini files ) wouldn't it be better if that gets included in installation procedure of those mods ? It would decrease loading time ( wrapper must go through all of that every time game gets loaded) and it would be easier to detect possible errors ( certain mod )
Z
No sir - you looking at as if there were two ini files with the same information
I would say that the objects ini files contain ONLY the CHANGES made
so making up an example
[buildings.House$CrimeaBarnStucco]
blah
blah
[buildings.House$CrimeaBarnWood]
blah
blah
[buildings.House$CrimeaChurch]
blah
blah
is OM standard
then Cannon wouldn't include the above
ONLY his NEW objects
//=======================================================
[***]
Title Brit_Iron
//=======================================================
[buildings.House$Brit_IronBSA]
blah
blah
[buildings.House$Brit_IronTriumph]
blah
blah
[buildings.House$Brit_IronM21]
blah
blah
so there would be no duplicate names only new names, so no sorting needed and it would append on to the end on OM static.ini the unique new objects from CAN_static.ini instead of object/ship makers providing WORKING ini files the would provide only the NEW OBJECT ini names in thier ini
the problem as you've explained it to me (simplified i assume) is developing a program that can parse, identify multiple lines under one heading and remove duplicates without removing a duplicate under a different heading.
I point you toward FC's ShipPack2 - I got this idea from his "AddTo Ini" where he has ONLY the changes and NO duplicates, so you do not need to PARSE for duplicates.
Granted there would need to be a protocol from AAA and a vetting process so that existing object headings are not repeated, but don't you sort of do that already?
... whatever you say , good luck
Z
Well here's a little program I heard about here somewhere
It's allowed me to combine a few static.ini files into one. But make backups first of course.
Good luck
Triad
Hmmm... that's strange. Still works for me. Not sure what it isn't working.
Maybe try here- same product and it's free
Thank you Triad I too use WinMerge
What i was asking for was something AAA sponsored. I can use ShipPacks and Hangers and everything but I can't dare you any online because if i make a mission using a new object then others online get load errors if the don't have the same objects installed.
i personally have added the objects without to much problem (OK maybe a little problem) but we need something AAA Unified sponsored so EVERYONE has the same set.
