Treat the lines as rough guidelines but the paths are all correctly listed.

Be clear that this is a mikeros issue, not a vanilla file issue.

But as a separate function I guess.

It's a request for a function to be able to use them in a programming sense so it's possible to have a more dynamically programmed loot system across multiple maps, instead of having to set up individual mission files for every map in existence.

Seems to work, yes.

couple more

couple more bad out refs:

I'm going to bump this with the request of both feature paths mentioned.

As mentioned, try it out on experimental and see if you still have the same issues.

Currently the only method using tiles like this, and matching structure edges with more pieces.

config.cpp edit used

class CfgVehicles
{
	class Armband_Black;
	class Armband_test_4_1 : Armband_Black
	{
		storageCategory = 1;
		itemSize[] = {4,1};
	};
	class Armband_test_1_4 : Armband_Black 
	{
		storageCategory = 1;
		itemSize[] = {1,4};
	};		
};

similarly, could also be fixed with the following powershell code and o2script run in the DZ folder to not have to worry about breaking anything.
gives people the option to spawn, check memory point "Origin" position then adjust as needed for any p3d.

with the bottom 02script and powershell code it could be fixed internally with some folder selection to not break things not actually wanted to be placed on maps inheritly.

geometry missing / binarize ignored property autocenter with value of 0.

It's a reply to this statement. "we always strive to ensure we affect those creations as little as possible."

So following this up, does that mean warnings found in script log marked as "FIX-ME" never need to be fixed, and the others can be ignored as nothing will be changed to make those more than just warnings?

Moving forward BI shouldn't be worried about mods losing compatibility. That's on the mod makers go keep their mods updated.
Should go one step further and change the script log "FIX-ME" warning to an error. It's been months, and mod makers have had plenty of warning.

Same objects can be spawned in runtime and retain the inheritance, and proxies are shown.
(CoT object spawner as example method.)

-this was fixed. Can close.