Files
DayZ-Epoch/SQF/dayz_code/Configs/CfgLoot/CfgBuildingLoot.hpp
ebaydayz 8201643c00 Cleanup CfgLoot
There is no point in having CfgBuildingPos.hpp in dayz_epoch_b too. It
was identical to the one in dayz_code and can be included in the mission
from there.

@icomrade couple questions:

1. Why keep a CfgLootLegacy? I know they are very different formats, but
it will just make things messier and more confusing. Also it will be a
PITA to maintain and update two different sets of loot tables in the
long run. I don't think catering to lazy admins is a good enough reason.
It's not that hard to convert to the new format.

2. Why not use the new _DZ weapon classes in the loot tables like
PDW_DZ, AKM_DZ, etc.?

3. Why not use the new box names like DZ_AmmoBoxRU, DZ_AmmoBoxUS,
DZ_MedBox,  etc. in the loot tables?

4. Why remove the attachments from the loot tables?
2016-03-12 17:17:38 -05:00

26 lines
977 B
C++

/*
Moved here for easier unmodified mission include:
#include "\z\addons\dayz_code\Configs\CfgLoot\CfgBuildingLoot.hpp"
If legacy is removed these should be put back in CfgLoot.hpp
*/
#include "Groups\Buildings\Boat.hpp"
#include "Groups\Buildings\Castle.hpp"
#include "Groups\Buildings\Church.hpp"
#include "Groups\Buildings\Construction.hpp"
#include "Groups\Buildings\Farm.hpp"
#include "Groups\Buildings\Hospital.hpp"
#include "Groups\Buildings\Hunting.hpp"
#include "Groups\Buildings\Industrial.hpp"
#include "Groups\Buildings\Military.hpp"
#include "Groups\Buildings\Office.hpp"
#include "Groups\Buildings\Powerlines.hpp"
#include "Groups\Buildings\Residential.hpp"
#include "Groups\Buildings\ResidentialRuins.hpp"
#include "Groups\Buildings\Supermarket.hpp"
#include "Groups\Buildings\Toilet.hpp"
#include "Groups\Buildings\Hangar.hpp"
#include "Groups\Buildings\DZE_Other.hpp"
// Can be removed if not using legacy loot tables
#include "CfgBuildingLootLegacy.hpp"