AFAIK there is no performance difference between configFile and
missionConfigFile.
Using missionConfigFile by default simplifies loot scripts and makes the
extra config variable unnecessary. It's one less step for admins to
customize their tables.
* Update stringtable.xml
Adding string support for AA12 ammo
* Update Rifles.hpp
Adding a few missing weapons.
* Update LMG.hpp
Adding one new LMG
* Update ShotgunAmmo.hpp
Adding AA12 ammo
* Update BanditAmmunition.hpp
Adding SCAR ammo
* Update BanditWeapons.hpp
Adding Mk17 Sniper and M110 NVG.
* Update FriendlyAssaultRifle.hpp
Adding Mk16 and L85 variations.
* Update FriendlyLightMachineGun.hpp
Adding L86A2 LSW
* Update NeutralBlackMarketAmmo.hpp
Adding new ammo AA12 and Mk17
* Update NeutralBlackMarketWeapons.hpp
Adding AA12 Shotgun and Mk17 variants.
* Update Weapons.hpp
Adding many new weapons.
* Update Ammo.hpp
Adding new AA12, Mk17 ammo to loot.
* Update AmmoBox.hpp
Adding SCAR ammo to eu2 box.
* Update Shotgun.hpp
Adding re-combine action for new AA12 ammo
* Update NeutralHelicopterUnarmed.hpp
Adding UH60M_MEV_EP1 to trader.
* Update NeutralBlackMarketAmmo.hpp
Removing AA12 HE
* Update Ammo.hpp
Comment out AA12 HE ammo
* Update Weapons.hpp
Lowering DMR spawnrate
* Update Generic.hpp
Adding some magazines
* Update Police.hpp
Adding Loot Group AmmoCivilian and removing magazines
* Update Industrial.hpp
Removing Sandbags, Wire and Tank Traps from normal Industrial spawn and moved them to Military Industrial- Lowering spawn chance of Planks, Consumable and Generic. Ive tested the new loot chances and they working fine.
* Update Hangar.hpp
Changing spawn chances of almost every item and adding PartEngine, PartGeneric, PartGlass to loot table. New hanger loot works good and feels much better than before.
* Update Military.hpp
Removing Loot Group Generic and Sandbags from Military and MilitarySpecial Loot. Adding Engine, Sandbags, Tank Traps, Wire and Loot Group Generic to MilitaryIndustrial. That works very well.
If you looting baracks and finding most of the time sandbags and generic loot it is frustrating. Now it feels better and more balanced.
* Update Military.hpp
Updating loot chances
* Added one new skin
* Added one new skin
* Added one new skin and class RepairVehicle
Added one new skin and class RepairVehicle: None { show = 0; };
* Added one new skin
* Added one new skin
* Update EpochSkins.hpp
* Added one new skin
* Added one new skin
* Added one new skin
* New Skins
Added all new skins to the loot table.
* Added new skins
* New skins for trading
* New skins for trading
* New skins for trading
* Added new skins
* Added new skins
* Strings for new skins
* Added new skins to player classes
* Added weight for new skins
Vanilla development commit:
db96d1c8c5
Note: does not affect buildings with Epoch loot positions. Vanilla
positions are commented out on those buildings.
It does not feel right, when you enter a military area and see only Worker Zombies. I changed the Zombie Typs of the buildings to look more like a military area.
I did not realize lootPosSmall positions can only fit small objects like
soda cans etc., so it is not okay to merge them with the main lootPos
arrays. This separates them back out.
This solution will work like 1.0.5.1 CfgLootSmall. <GroupName>Small is
used to spawn additional loot if the building type has lootPosSmall
positions available. It is not necessary to add a <GroupName>Small for
types that do not have lootPosSmall positions.
Some of these objects may still be too big or too small (knife,
binoculars, matchbox, etc.) for the positions and look out of place. If
that is the case please submit a pull with any problematic ones removed
from the <GroupName>Small groups (check if they aren't in 1051
CfgLootSmall first). Balance and rates may need adjustment as I just
took the normal groups and removed large objects from them while trying
to keep similar items to 1.0.5.1 CfgLootSmall.
Epoch has custom loot positions for many buildings. Most lootPos have
not changed in vanilla since pre 1.7.x.
The vanilla lootPos are now commented out and custom Epoch ones are
added back. LootPosSmall positions are now included in lootPos and
marked with //DZE EXTRA
LootPosSmall are included and used by default in 1051, so it is simpler
to add them to the main lootPos lists instead of having a separate loop
in buildingSpawnLoot.sqf for them.
I just changed the spawing zombie typ for the military special loot. I noticed that there are only "z_new_worker2-4" zombies in the baracks and got a bit confused. So now we have the military zombies back.
Also moved the dayz_epoch_b stringtable into a dayz_epoch package in the
dayz_code stringtable.
This makes it easier to maintain and search for code strings. Epoch_b
only holds extra models and textures now.
Tool breaking is disabled by default.
Also made all scripts use Epoch sledge, which is a different model from
vanilla sledge.
PK_DZ was a duplicate of the new PKM_DZ.
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?
See:
634214570c
@icomrade - IMO we should use the new blood type system and take out the
config variable. It is not something that can be easily switched between
because it requires manually changing the loot tables and traders which
adds some big files to the mission. Some admins will get confused when
they change the config variable and it doesn't change the loot spawns or
traders.
Admins can make bloodBagONEG abundant on their server if they
don't like it. I think most people will want to use it since it is a
nice extra realism feature and consistent with 1.8.7. We can still leave
the ItemBloodbag class defined in cfgMagazines so admins can go back to
using it if they wish. 1.8.7 even took out the class completely.
