cfgloot and cfglootsmall, why BOTH?

[Wesley]

seems to me that CFGloot.hpp contains all information needed for cfglootsmall.hpp, yet there is a NEED for cfglootsmall.hpp?

Seems like it is covered by cfgloot.hpp

 

and in spawn_loot_small.cfg you could replace cfglootsmall with cfgloot and be perfectly fine?

[Glenn]

CfgBuildingLoot = Deals with items or item types that spawns in buildings, and what Zombies will spawn from the buildings, and what possible loot the Zombies will have a chance to drop. 

CfgBuildingPos = the exact positions inside the building that a loot point is possible to spawn at + Zombie spawn (without loot) that is needed for the building. Note that this is in addition to the CfgBuildingLoot.

CfgLoot = the various arrays available that holds the main loot (weapons and such).

CfgLootSmall = the various small loot content (think 23 mags and a flashlight) that is not weapons. 

 

When the server decides to create a loot spawn, it will look in the Building Loot as to what the building is and the number of Zeds to spawn from it (and what loot those Zed has a chance of having).

then it gets the positions that the loot will be placed on, and then for each point it decides to spawn, it checks the CfgLoot and see what it should add. 

 

CfgLootSmall is used when the building calls for the use of it, and it is there so that the server knows how to create it. "addweaponcargo" calls are made for a category in the CfgLoot, while the same category in CfgLootSmall is likely to use "addmagazinecargo". Separation there means that the server will work properly and not freak out when it starts to read in the Custom loot info. :) 

Probably are better examples out there than my block of text... but until something better comes along - there you go. :)