17.09.2008, 18:30
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
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