I wonder if Jagged uploaded it. I can see the "author" in the vault but not the up loader. In any case I found out the fixes from the error messages. Whoever renamed the module "Jaggeds_Infrastructure_Pack 3.0" did NOT modify the source lines in various LUA files with import and iconpath statements referring to the original Mod's path. So multi-file edit - search for "Jaggeds_Infrastructure_Pack" replace with "Jaggeds_Infrastructure_Pack 3.0" With this fix in place and testing - T2 storage now works as expected.

@Gladry Seems a bit of Miss Communication. what i would do is the following UnitBlueprint { BlueprintId = "tbu0029", Merge = true, Weapon = { { Damage = 30, }, {}, }, } UnitBlueprint { BlueprintId = "gmrb402", Merge = true, Intel = { VisionRadius = 20, }, Weapon = { { Damage = 30, }, {}, }, }

There is indeed a small memory leak in the base game - it may very well be caused by the same unit blueprint issues that often cause mods to have sizable memory leaks. Either way, it's mostly a problem that can be substantially addressed in the LUA codebase, and not the engine.