mirror of
https://github.com/EpochModTeam/DayZ-Epoch.git
synced 2025-12-14 04:02:37 +03:00
8201643c00
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?
26 lines
869 B
C++
26 lines
869 B
C++
/*
|
|
If using DZE_MissionLootTable = true; without changing anything in lootPos then use
|
|
an include instead of copying the files to your mission.
|
|
|
|
#include "\z\addons\dayz_code\Configs\CfgLoot\CfgBuildingPos.hpp"
|
|
*/
|
|
|
|
#include "Buildings\Residential.hpp"
|
|
#include "Buildings\Boat.hpp"
|
|
#include "Buildings\Castle.hpp"
|
|
#include "Buildings\Church.hpp"
|
|
#include "Buildings\Construction.hpp"
|
|
#include "Buildings\CrashSite.hpp"
|
|
#include "Buildings\Farm.hpp"
|
|
#include "Buildings\Hospital.hpp"
|
|
#include "Buildings\Hunting.hpp"
|
|
#include "Buildings\Industrial.hpp"
|
|
#include "Buildings\InfectedCamp.hpp"
|
|
#include "Buildings\Military.hpp"
|
|
#include "Buildings\Office.hpp"
|
|
#include "Buildings\Powerlines.hpp"
|
|
#include "Buildings\ResidentialRuins.hpp"
|
|
#include "Buildings\Supermarket.hpp"
|
|
#include "Buildings\Toilet.hpp"
|
|
#include "Buildings\Roaming.hpp"
|
|
#include "Buildings\Misc.hpp" |