Configure and operate a multi-map DayZ cluster.
This documentation describes the normal end-product workflow for MapLink customers and administrators. Your installed release may hide options that are unavailable or not applicable to the current configuration.
What MapLink controls
MapLink coordinates cross-map character authority. It does not replace Steam Workshop, DayZ persistence or the server manager that owns the DayZ processes.
Windows platform
Control Center, Broker, Supervisor, update/recovery logic, logs and local configuration.
DayZ Core
Workshop-loaded runtime for admission, terminal/countdown behavior, character transfer orchestration and client target handoff.
Portal & release services
maplink.at handles accounts/licensing. updates.maplink.at publishes cryptographically verified release metadata and packages.
Requirements
- Windows host with administrative rights for the initial installation/service registration.
- At least two participating DayZ servers.
- Each server already starts and stops reliably through its normal process manager.
- Steam Workshop access for MapLink Core and matching client mod distribution.
- A MapLink license with enough active-installation and cluster-server capacity.
- Stable server IDs, game ports and public connection endpoints for each participating server.
- Safe arrival coordinates and planned terminal positions for every route you intend to enable.
License and account
A license is issued to an email address. Create or sign in to My MapLink, claim the license if necessary, and keep account recovery/2FA current.
| Active installations | Number of separate Windows MapLink platforms that may hold a current activation. |
|---|---|
| Servers in cluster | Maximum DayZ servers managed by one licensed cluster. Minimum is two. |
| Expiry | Optional entitlement expiry. A no-expiry license has no fixed contractual date in the license record. |
| Pre-release access | Controls eligibility for Beta and Alpha pre-release channels in addition to Stable. |
During first-run activation, the Control Center exchanges the license key for an installation activation token and signed lease. Subsequent refreshes use the activation token, not the plaintext license key.
Install the MapLink platform
- Sign in to My MapLink, verify your email, accept the current EULA and download the entitled MapLink Setup.exe through the protected download center.
- Verify the Windows publisher/signature when the public signed installer is available.
- Choose a dedicated installation folder; the recommended default is under Program Files.
- Complete UAC elevation. The installer registers only MapLink components.
- Open the local Control Center. A new installation enters the guided Setup Wizard automatically.
- Activate your license when prompted.
Add participating DayZ servers
Add each source/target server once with a stable MapLink server ID. Use the same identity after restarts and updates.
| Display name | Human-readable name shown in routes, status and audit logs. |
|---|---|
| Server ID | Stable unique MapLink identity. Do not casually change it after transfers exist. |
| World / map | The DayZ world loaded by this server instance. |
| Public host | Address clients use for the automatic target connection. |
| Game port | DayZ game port for the target handoff. |
| Join password | Only when the DayZ server is password protected. Stored locally and used by automatic reconnect/handoff. |
| Runtime path / detection | Local server/profile/runtime metadata used for health and compatibility checks; normally discovered by the wizard where supported. |
When using CFTools, continue managing DayZ processes and Workshop updates through CFTools. MapLink only observes the state it needs for safe transfer/update decisions.
Install MapLink Core
MapLink Core is a normal DayZ client mod. Install the same Workshop item/version on every participating server and require clients to load it. Do not maintain an unrelated serverMod-only Core copy as a second source of truth.
- All participating servers use a transfer-contract-compatible Core.
- The server key/signature matches the published Workshop build.
- Clients receive the same Workshop update before joining.
- After a Core update, restart DayZ through the normal manager and let Control Center re-check compatibility.
Create routes
Routes are directional and explicit. Create A → B and B → A separately when both directions are desired.
| Route ID | Stable identifier used in diagnostics/audit. |
|---|---|
| Source server | Server on which the player starts the transfer. |
| Target server | Server that will claim and restore the prepared character. |
| Enabled | Only enable after all terminals, target arrival and compatibility checks are valid. |
| Require target online | When enabled, preflight refuses the transfer if target readiness cannot be proven. |
Configure terminals and arrival
Every terminal must use real in-world coordinates and a radius appropriate to the object/area. Keep arrival positions clear of geometry, locked rooms, water, map edges and hostile scripted zones unless intentionally designed.
| Terminal ID/name | Stable identifier and clear operator label. |
|---|---|
| Source X/Z | World coordinates for eligibility checks. |
| Radius | Horizontal departure radius. A smaller radius is more precise; use enough room for normal player movement. |
| Vertical bounds | Optional height restriction to prevent triggers above/below the intended terminal. |
| Target arrival | Safe position on the target server/map used after restore. |
| Countdown | Delay before prepare; the player must remain eligible for the configured countdown behavior. |
Transfer feedback
Choose the feedback mode supported by your release: chat, on-screen UI or both. Transfer feedback must be passive and must not steal mouse/keyboard focus from normal DayZ menus.
Use concise messages such as destination, countdown, cancellation reason and connection state. Avoid exposing internal IDs or secrets to players.
Commission a route before normal player use
- Confirm Broker healthy and all participating servers show the expected Core/contract version.
- Perform one controlled acceptance transfer in the route direction with a non-critical character.
- Enter the real terminal and verify preflight/countdown.
- Confirm normal player controls and menus remain usable during countdown.
- Stay within the terminal until prepare completes.
- Do not manually select the target; verify automatic target connection.
- Confirm target restore, equipment/inventory, position and commit.
- Log out normally on the target and verify the next normal login remains on that target.
- Only then commission the reverse route and additional terminals.
Normal daily use
Once configured, MapLink is designed to recover its Broker/Supervisor automatically after Windows restarts. Routine operation should not require PowerShell commands.
- Control Center shows Broker and participating server health.
- Routes/terminals remain enabled only while their safety prerequisites are valid.
- Transfer Audit is the source for player-specific transfer history and failure codes.
- License state is refreshed automatically within its signed lease policy.
- Your existing manager remains responsible for DayZ restarts and maintenance windows.
Update safely
Compatible Windows/backend update
Check → cryptographic verification → download/stage → transactional backup → install → Broker healthcheck → rollback on failure.
Transfer-contract-changing update
The Update Center stages the Windows release but does not blindly activate it. Update the MapLink Core Workshop item on every participating server, perform the required maintenance through your server manager, verify all servers report the exact compatible contract, then authorize the guarded Windows activation.
Backup, restore and migration
- Back up MapLink local configuration/data and update backups on the Windows host.
- Back up the maplink.at MariaDB database.
- Back up the protected portal configuration containing the private Ed25519 license-signing key in an encrypted offline location.
- Never commit private keys, database passwords or DayZ join passwords to GitHub.
- When moving the Windows platform, deactivate the old license installation when possible and follow the Control Center migration/restore workflow.
Diagnostics workflow
| No countdown | Read preflight: terminal geometry, route enabled, target readiness, recovery/pending state, compatibility. |
|---|---|
| Countdown cancels | Check departure radius/vertical bounds and any eligibility condition that changed during countdown. |
| Disconnect but no target connect | Check target endpoint/port/password, handoff ticket creation and client reconnect trace. |
| Target connect but no restore | Check admission, claim, serializer, arrival validation, restore verification and commit. |
| Update blocked | Check contract compatibility, server maintenance state, pending transfers/recovery and Core version synchronization. |
When contacting support, include version, source/target server IDs, route/terminal ID, timestamp and sanitized relevant logs. Never include secrets.
Operational security rules
- Keep the Control Center local-only unless an officially supported remote-access method is introduced.
- Use a unique My MapLink/admin password and enable TOTP.
- Keep DayZ join passwords and license activation tokens out of screenshots/support posts.
- Apply signed updates only from the configured MapLink release channel.
- Preserve audit/history rather than manually deleting production database records.