From license to a commissioned MapLink cluster.
Use this workflow for a normal new installation. The Control Center intentionally reveals only the steps and settings that are relevant to the current stage.
1. Get or claim your license
Use My MapLink to claim the license issued to your email address. Verify your email and enable TOTP where appropriate. Make sure the license permits the number of Windows installations and DayZ servers you plan to use.
2. Download the official installer
Sign in to My MapLink, verify your email address and accept the current MapLink EULA. The protected download center then exposes only release channels covered by your active license and issues a short-lived ticket for the selected signed package. Prefer the Authenticode-signed Setup.exe when public installer signing is enabled.
3. Install the Windows platform
Run the installer as administrator, choose a dedicated folder (recommended: Program Files) and allow it to register MapLink services/tasks. Do not install MapLink inside a DayZ server directory.
4. Activate MapLink
The local Control Center opens automatically and asks for the license key. Activation binds this Windows installation to a licensed slot and stores the returned activation token/lease locally.
5. Add your DayZ servers
Add each participating server with a stable MapLink ID, display name, world/map, public host and game port. If a server requires a DayZ join password, enter it in the protected server settings so automatic reconnects can use it.
6. Install MapLink Core
Subscribe/install the official MapLink Core Workshop item on every participating server as a normal DayZ client mod. Players load the same item. Keep Workshop/Core versions synchronized across the cluster.
7. Create directional routes
Create each intended source → target route separately. Select the source/target server and target-online policy. A reverse route is a separate configuration.
8. Add terminals and arrivals
For each route, enter the real source terminal coordinates/radius and a verified safe arrival position on the target. Use stable names/IDs so failures are easy to identify in audit logs.
9. Configure player feedback
Choose chat, on-screen feedback or both when supported. Set countdown behavior and confirm that MapLink feedback remains passive and does not block normal DayZ input.
10. Complete the readiness checks
The Control Center checks Broker health, license, server mappings, Core/contract compatibility, routes and recovery state. Incomplete/unsafe routes stay disabled.
11. Commission the first route
Before opening a route to normal players, perform a controlled acceptance transfer with a non-critical character and verify the complete sequence: preflight, countdown, prepare, controlled disconnect, automatic target connect, restore, verification and commit. Then perform a normal logout/login on the destination.
12. Enable the remaining routes
After the first route passes, commission the reverse direction and additional terminals one at a time. Keep Transfer Audit open during initial production use.
After Windows restart
Supervisor/Broker recovery is automatic. Your DayZ server manager remains responsible for DayZ processes.
After a Windows-only MapLink update
Compatible releases can be installed transactionally from Update Center with verification and rollback.
After a Core/contract update
Synchronize the Workshop Core on all servers first, then use the guarded activation flow in the Control Center.