Deploy to server (Pro+)
Push the .miz straight to your DCS server.
Skip the download / upload / SCP dance. Tell the engine your server's name and the built .miz lands in the right folder.
Requirements
- Pro tier or above.
- Your DCS server is on the Fox3 fleet (Tailscale-reachable, WinRM enabled). If you self-host elsewhere, this feature isn't available — download the
.miznormally. - You know your server's Tailscale name (e.g.
dcs-atl-254).
How it works
- On /build, fill in the Deploy to server card's Host field.
- Optionally set a Path. Default is
C:\Users\luck\Saved Games\DCS.openbeta_server\Missions, which is where the standard Fox3 fleet runs DCS from. - Click Build & Deploy (the button label changes when a host is set).
- The engine builds the
.mizas usual, then opens a WinRM session to your server and writes the file via base64 → PowerShellWriteAllBytes. - The result panel shows green ✓ on success or red ✗ with the error.
If deploy fails, the build still counts as completed — you can always download the .miz manually from the result panel as a fallback.
Common failure modes
- “Connection refused.” WinRM (port 5985) is not open or the host name doesn't resolve. Verify the Tailscale name and that the server is online.
- “Access denied.” The Mission Curator service account doesn't have write permission to the target path. The default path is the standard Fox3 fleet path; custom paths may need a permission adjustment.
- “Path not found.” The folder doesn't exist on the remote machine. Either create it or use the default.
Fleet tier auto-push
On the Fleet tier, Mission of the Day auto-deploys to up to 5 servers every morning at 00:05 UTC. No manual builds needed; your servers always have a fresh mission ready.