Modding Structure – DayZ
Jump to navigation
Jump to search
mNo edit summary |
|||
Line 7: | Line 7: | ||
== Mod structure == | == Mod structure == | ||
Mod is loaded using the '''-mod=''' launch parameter | |||
''-mod=C:\MyMods\TestMod'' | |||
Typical mod folder downloaded from steam workshop will contain: | |||
* '''Addons''' folder, holds the mod's '''.pbo''' files | |||
* '''Keys''' folder, contains public .bikey used to sign the .pbo files (required for client-server signature verification) | |||
* '''meta.cpp''' file, holds workshop meta data (will be automatically created during mod publishing) | |||
* '''mod.cpp''' optional config file, holds information for mod presentation | |||
== PBO structure == | == PBO structure == | ||
== Mod presentation == | == Mod presentation == |
Revision as of 14:21, 13 June 2019
This page details the structure of DayZ mods as well as their configuration and presentation.
Mod structure
Mod is loaded using the -mod= launch parameter
-mod=C:\MyMods\TestMod
Typical mod folder downloaded from steam workshop will contain:
- Addons folder, holds the mod's .pbo files
- Keys folder, contains public .bikey used to sign the .pbo files (required for client-server signature verification)
- meta.cpp file, holds workshop meta data (will be automatically created during mod publishing)
- mod.cpp optional config file, holds information for mod presentation