Export your modpack as a server configuration file that’s ready to use with Project Zomboid dedicated servers. This guide covers version selection, export configuration, downloading files, and installation on your server.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/Greens-Organization/pz-packs/llms.txt
Use this file to discover all available pages before exploring further.
Overview
PZ Packs generates server configuration files containing three critical sections:- Mods - Mod IDs in the correct format for your PZ version
- WorkshopItems - Steam Workshop IDs for automatic downloading
- Map - Custom map folders plus default maps
Export files are generated in the background and are user-specific. Your export configuration (mod order, variant selection) is saved separately from other team members.
Choosing a Project Zomboid Version
Select your server version
PZ Packs supports two Project Zomboid versions:
- Build 42.x - Latest unstable/beta branch (recommended for new servers)
- Build 41.x - Stable branch (for established servers)
Understand format differences
Build 42.x format:Build 41.x format:The only difference is the backslash prefix (
\) required in Build 42.x.Configuring Export Settings
Before exporting, you can customize how mods are included in your server file.Mod Load Order
Mod order can affect gameplay and compatibility:Set your preferred load order
Configure
modsOrder to specify the exact sequence mods should load. This is saved in your personal export configuration.Selecting Mod Variants
Some Workshop items contain multiple mod IDs (variants or optional components):Review mods with multiple variants
Mods with multiple Steam Mod IDs appear with checkboxes or selection options in the export configuration.
Configure variant selection
Use the Only the selected variants will appear in the exported file.
modConfig setting to choose which variants to include:Saving Export Configuration
Your export configuration is saved per user and per modpack:- Configuration persists between exports
- Changes only affect your exports, not other team members
- Modpack owner can set default configuration for all members
Requesting a Server File Export
Navigate to the export dialog
On your modpack page, click the “Export” or “Download Server File” button.
Submit export request
Click “Export” to queue the file generation.The system will:
- Create an export request in the database
- Add a background job to generate the file
- Return an export ID for tracking
Understanding the Generated File
The exported file contains three sections:Mods Section
Lists all mod IDs in the format appropriate for your selected version:- Includes selected variants only
- Duplicates are automatically removed
- Order matches your
modsOrderconfiguration
WorkshopItems Section
Lists Steam Workshop IDs for automatic mod downloading:- Contains Workshop IDs from all included mods
- Used by the server to auto-download mods from Steam
- Duplicates are automatically removed
Map Section
Includes custom map folders plus the default Muldraugh map:- Automatically includes
Muldraugh, KYas the default spawn - Custom map folders are extracted from mod metadata
- Only includes maps from active, selected mods
The default map “Muldraugh, KY” is always included. Remove it manually if you want a custom map-only server.
Downloading the Server File
Wait for completion
When the export status shows “Completed”, the download button becomes available.
Download the file
Click the download button to retrieve your server configuration file.The file is a plain text
.ini file containing the three configuration sections.Installing on Your Project Zomboid Server
Locate your server configuration file
On your dedicated server, find the server configuration file:Windows:Linux:
Update configuration sections
Open your server’s Replace them with the values from your exported file.
.ini file and find these lines:Restart the server
Restart your Project Zomboid dedicated server to load the new mods.On first launch:
- Server downloads all Workshop items from Steam
- This can take several minutes for large mod lists
- Monitor server logs for download progress
Troubleshooting Common Issues
Mods Not Loading
Issue: Server starts but mods don’t load Solutions:- Verify the
Mods=format matches your server version - Build 42.x requires backslash prefix:
\ModID - Build 41.x has no prefix:
ModID - Check that Workshop items downloaded (look in server logs)
Workshop Download Failures
Issue: Some Workshop items fail to download Solutions:- Verify your server has Steam Workshop access enabled
- Check if the Workshop item was removed from Steam
- Try manually subscribing to the Workshop item
- Remove the problematic Workshop ID from the config
Map Not Loading
Issue: Custom maps don’t appear in-game Solutions:- Ensure map mods are in both
Mods=andWorkshopItems= - Verify the map folder name in
Map=is correct - Some maps require specific load order - try loading them first
- Check mod description for special installation instructions
Export Fails
Issue: Export status shows “Failed” Solutions:- Try exporting again (temporary server issue)
- Verify all mods in the modpack are valid
- Check for mods with missing metadata
- Contact support if the issue persists
Best Practices
Regular exports
Re-export whenever you add or remove mods from your modpack to keep your server in sync.
Test before production
Test exported configurations on a development server before deploying to production.
Version consistency
Keep your server version and export version in sync. Don’t mix 41.x exports with 42.x servers.
Document custom changes
If you manually edit the exported file, document your changes so you can reapply them after future exports.
Related Resources
- Importing from Steam - Add mods to your modpack from Steam Workshop
- Managing Permissions - Control who can modify and export your modpack
- API Reference: Export Server File - API documentation for exports