Skip to main content

​
Transitioning the Theater of War

In the DayZ Standalone architecture, the physical world and its associated logic are governed by the Mission Folder. Whether you are transitioning to the freezing landscapes of Namalsk, the overgrown ruins of Livonia, or a community-made map, you must correctly synchronize the terrain assets with the corresponding server-side mission repository. The FREAKHOSTING Game Panel provides a structured environment for managing these files, ensuring a stable and immersive world transition for your community.

Difficulty

Intermediate

Time

10 Minutes

​
Technical Deployment Workflow

Follow these steps to correctly initialize a new map on your dedicated server.
1

Deploy Terrain Assets

Ensure the physical map modification (e.g., @Namalsk_Island) is correctly uploaded and added to your server’s -mod= startup parameter. Without the actual terrain data, the mission files will fail to initialize.
2

Migrate Mission Repositories

Acquire the multiplayer mission files for your specific map (typically provided by the map author on GitHub). Upload the resulting folder (e.g., regular.namalsk) directly into your server’s root /mpmissions/ directory.
3

Configure Global Variables

Locate and open the serverDZ.cfg file in the root directory. Navigate to the class Missions block at the conclusion of the file and update the template variable.
class Missions
{
    class DayZ
    {
        template="regular.namalsk"; // This must precisely match your folder name
    };
};
4

Initialize the World

Save your changes and Restart the server. The engine will now load the new map definitions and begin populating the Central Economy.

​
Strategic Database Management

When migrating to a completely different map, we strongly recommend deleting the storage_1 folder located within your mission directory. This forces the server to regenerate a clean player and world database. Attempting to load legacy player positions or items that are incompatible with the new terrain will lead to immediate server crashes or corrupted character states.
Each mission folder contains unique configuration files, such as map_info.xml and cfggameplay.json. You can modify these files to customize the world’s lighting, weather patterns, and fundamental physics specifically for that map instance.

​
Case Sensitivity

Our high-performance servers use a Linux-based environment, which is strictly case-sensitive. If your mission folder is named Regular.Namalsk but you define it as regular.namalsk in the configuration, the engine will fail to locate the path and the server will not start.

​
Need Extra Help?

If you encounter any issues, our support team is ready to assist:

​
Save on Your Hosting

Ready to get a new server? Use code KB20 at checkout for 20% off your first month!
Last Updated: January 2026 | Missions: Fresh starts in new lands.