Installing Community Framework (CF) Mods
Install and configure Community Framework, the server-side mod required by trader systems, custom NPCs, and most advanced DayZ mod packs.
Overview
Community Framework (CF) is a server-side mod that provides shared scripting infrastructure for advanced DayZ mods. Trader systems (Dr. Jones Trader, Expansion Market), custom NPC frameworks, quest systems, and many popular mod packs all require CF as a dependency. CF must load before any mod that depends on it, making load order the most common source of CF-related errors.
What CF Provides
- Shared configuration loading system
- Server-side object and NPC management APIs
- Custom menu framework for trader interfaces
- Persistent storage hooks used by trader mods
- Approximately 50–100ms additional server frame time overhead (unavoidable)
Step 1: Download CF
CF is distributed on the Steam Workshop. Use DZSA Launcher or download manually:
- Steam Workshop ID:
1559212036(Community Framework)
Upload the mod folder to your server's mods directory:
/home/container/@CF/
Step 2: Set the Mod Load Order
CF must be first in your mod list. In your Pterodactyl/WISP startup parameters, set the -mod= flag:
-mod=@CF;@ExpansionMod;@ExpansionMarket
For a full mod stack example:
-mod=@CF;@VanillaPlusPlusMap;@DrJonesTrader;@VPPAdminTools
Never place CF anywhere but position 1 in the list. Any mod that depends on CF will fail to initialize if CF loads after it.
Step 3: serverDZ.cfg Mod Entry
Some older mod documentation suggests adding CF to serverDZ.cfg:
mods = "CF;ExpansionMod;ExpansionMarket";
In current DayZ server versions, the startup parameter -mod= is the authoritative way to load mods. If your panel uses startup parameters, use that. The mods = entry in serverDZ.cfg is redundant if startup parameters are set and can cause conflicts — use one or the other, not both.
Step 4: CF Configuration (if applicable)
CF itself has minimal configuration. Mods that depend on CF configure themselves in their own folders within server_profile/. For example, Dr. Jones Trader creates:
server_profile/Trader/
TraderConfig.txt
These are generated on first run. Start the server once after installing CF and dependent mods to let them create their default config files, then stop the server and customize.
Common Errors
"script error: cf not found" or similar
CF is not first in the mod load order. Move @CF to position 1 in the -mod= flag.
"missing config" or mod fails to initialize
The mod folder is incomplete or corrupt. Re-download the mod from Workshop and re-upload.
Server crashes on startup with CF mods
Check server_profile/logs/script.log for the specific SQF error. Common cause: a dependent mod requires a newer version of CF than what is installed. Update CF.
Trader NPC not spawning
CF initialized but the trader mod's config has an error. Check the trader mod's config file (e.g., server_profile/Trader/TraderConfig.txt) for syntax errors.
Performance Considerations
CF and mods using it add overhead to every server frame. Expected impact:
- CF alone: ~50ms additional frame time
- CF + 1 trader mod: ~80–120ms
- CF + full expansion pack: ~150–200ms additional
On a server targeting 60 FPS (16ms frame budget), this is significant. Set -cpuCount appropriately and monitor server_profile/logs/scheduler.log for frame timing after adding CF-dependent mods. See Server Performance Tuning and Player Count Scaling for tuning guidance.
Updating CF
When updating CF, always update all dependent mods at the same time. CF version mismatches with dependent mods are a common source of crashes and script errors. Recommended update process:
- Stop server
- Backup
server_profile/ - Replace all mod folders with updated versions
- Start server and monitor logs