19.05.2009, 05:13
I see no problem with that...
BTW no offense taken...
I always look at the static.ini like a list of objects (which it is) ....called upon by a map or mission
if they are called for by the map or mission and appear in your list...OK
if they are not in your list...problem
if their data in the MODS folder is missing or incorrect...... they simply do not appear upon the map or in the mission....but do not cause the map or mission to crash
no maps use every object available in our list.... so this tells me that.....having lots of extra stuff in your static.ini isn't a problem ....only when something is required which you don't have...
we require some of the ingredients in our larder to bake a cake...but not all
we cannot make the cake if any ingredients are missing
BTW no offense taken...
I always look at the static.ini like a list of objects (which it is) ....called upon by a map or mission
if they are called for by the map or mission and appear in your list...OK
if they are not in your list...problem
if their data in the MODS folder is missing or incorrect...... they simply do not appear upon the map or in the mission....but do not cause the map or mission to crash
no maps use every object available in our list.... so this tells me that.....having lots of extra stuff in your static.ini isn't a problem ....only when something is required which you don't have...
we require some of the ingredients in our larder to bake a cake...but not all
we cannot make the cake if any ingredients are missing