General Setup

Zen's Enormous Package

This guide is for setting up my master modpack Zen's Enormous Package.

However, the instructions for setting up each individual mod are the same for everyone whether you use my big modpack or not - so I still recommend reading through these guides.

The only information which doesn't apply to you if you are not using my modpack is the info regarding the master config file (ZenModPackConfig.json) and any mods listed in the wiki guides which I have not released publicly on the Steam Workshop yet.

Requirements

This modpack requires Community Framework and Zen Mod Core in your server's modlist or your server will not run.

XML Config

The first thing I recommend doing is setting up a custom types.xml folder structure to keep all my mod entries separate from other mods and vanilla config.

The way to do this is easy, just open this file:

server_folder/mpmissions/map_name/cfgeconomycore.xml

And add this code to it underneath the </defaults> tag:

    <ce folder="db/Zenarchist">
        <file name="types.xml" type="types" />
        <file name="events.xml" type="events" />
        <file name="cfgspawnabletypes.xml" type="spawnabletypes" />
    </ce>

Then create a new folder in the db folder, so you have this folder structure: server_folder/mpmissions/map_name/db/Zenarchist

And either paste in the XML files from this example XML config, or create these two text files and add the types in separately for each mod you plan to use:

server_folder/mpmissions/map_name/db/Zenarchist/types.xml

server_folder/mpmissions/map_name/db/Zenarchist/cfgspawnabletypes.xml

This will keep all my mod's types entries separate from other mods + the vanilla XMLs.

Inside the Zen's Enormous Package mod folder downloaded from the Steam Workshop you will find the default *.xml files with all modded classname entries contained in them. To see this files, simply click this button:

For those new to server admin'ing, you can do this approach for separating any mod's types.xml.

You can also have multiple types files in the same folder (eg. types_music.xml + types_treasure.xml for my mods etc), and you can even split up the vanilla types.xml to separate food/ammo/weapons etc to keep things better organized.

Just don't forget to add every new type's filepath in cfgeconomycore.xml as explained above.

MapGroupProto.xml

The mapgroupproto.xml additions are only needed if you want hunting loot to spawn in my static treehouses (which must be placed using DayZ Editor or admin tools).

The mapgroupproto.xml file controls the loot spawn locations on an object, and can be found in mpmissions/mapgroupproto.xml. Simply add my extra treehouse entries into that file to turn item spawns on.

You will also need to add the positions of any objects you want to spawn loot into the mpmissions/mapgrouppos.xml file. If you are using my treehouse mod, the easiest way to do this is to use the DayZ Editor to place the treehouse objects, and then export the mapgrouppos.xml file from inside the Editor and merge the new XML entries into your vanilla mapgrouppos.xml file.

JSON Config

The JSON config files for each mod will be automatically generated the first time you start your server with any of my mods installed.

There's a lot to learn and tweak with these mods, but I've made them as auto-pilot as possible and configuring them individually is mostly optional - but I highly recommend looking through the wiki guide for each mod you want to set up to see what each setting does.

TYPES NOTE

NOTE: You will need to set up your own loot economy (ie. spawn counts).

Area and usage tags differ from map to map - my recommendation is to look through your vanilla types.xml for items similar to whatever item you are trying to set up of mine, and copy the vanilla usage flags etc to avoid issue with your loot not spawning as expected.

These tags can differ from map to map and some types might not exist on the map you are setting up (including Tiers) - so always check vanilla config for examples:

<category name="x"/>
<usage name="x"/>
<tag name="x"/>
<value name="x" />

To see a full list of Tiers, usage, flag and value tags which are valid for your chosen map, read through the server_folder/mpmissions/map_name/cfglimitsdefinition.xml file which lists all valid tags.