The current Github version of DZAI is now updated to version 2.1.0 here: https://github.com/dayzai/DZAI A (mostly) copy-and paste of some important points from the pre-release announcement: Q: I'm currently running an older version of DZAI. What do I need to know before I upgrade? A: I highly recommend you remove your current installation of DZAI and reinstall from scratch. The instructions for installing DZAI have changed slightly (you just need an extra  before the call compile line). I highly discourage users from reusing old DZAI files due to the large amount of changes. This includes all config files. Q: Where is the changelog for 2.1.0? A: You can find the changelog for 2.1.0 by following this link. Q: I have a pre-release build of 2.1.0 installed, do I still need to reinstall? A: If you have pre-release build 6 then you don't need to re-install. If you have an earlier pre-release build or are unsure what build you have, reinstall with the most updated version from Github. Q: Where did the global_classnames.sqf file go? A: It's been merged with dzai_config.sqf Q: Where did the dzai_settings_override.sqf file go? A: It has been removed and is now only used for dev purposes. Q: What are the custom spawn functions? A: DZAI_spawn (custom spawn function) has been renamed to DZAI_spawn_units DZAI_spawn_vehicle (custom vehicle AI spawn function) has been added Further instructions are provided in custom spawn config files Q: What goes inside the square brackets  in the call for dzai_initserver.sqf? A: Optional startup parameters may be inserted in the call for dzai_initserver.sqf: "readoverridefile" and "enabledebugmarkers" For example: Code: ["readoverridefile"] call compile preprocessFileLineNumbers "\z\addons\dayz_server\DZAI\init\dzai_initserver.sqf"; The readoverridefile startup parameter will let DZAI read from a file named dzai_settings_override.sqf placed directly inside the DZAI folder. This is a file used for development and may not be relevant to regular users The enabledebugmarkers startup parameter will allow DZAI to create debug markers indicating the positions of AI units and active spawn locations. This is meant for debugging and development purposes only. I won't respond (helpfully) to requests to adapt this feature for everyday non-development/debugging use.