Frequently asked questions

MapLink is a DayZ multi-map transfer platform. It coordinates a player transfer between participating DayZ servers while maintaining one authoritative character state across the configured cluster.

A normal MapLink installation consists of the MapLink Core Workshop mod on each participating DayZ server, the local Windows Broker/Supervisor, the local-only Control Center and the signed update service.

No. Your existing server manager remains authoritative for DayZ process lifecycle. MapLink starts, monitors and repairs its own Broker/Supervisor components only.

At least two. A transfer needs a source and a target. Licenses and configuration therefore reject a cluster limit below two servers.

Yes, when your license and installed MapLink release allow the required cluster size. Routes are configured independently, so a server can participate in one or many directional connections.

No. Licensing and My MapLink are for the server operator. Players only need the same required DayZ Workshop mod set as the server, including MapLink Core.

The core routing model is map-independent, but production use still depends on the installed release certifying the required character serializer, persistence cleanup and any third-party integration adapters. The Control Center exposes only supported/certified capabilities and keeps unsafe combinations disabled.

No. The operational dashboard is designed for local administration on the Windows host. The public maplink.at portal is separate and handles product information, accounts and licensing.

A license is issued to an email address by MapLink or an authorized seller/operator. The plaintext key is shown once when issued. The portal stores only a one-way hash of the key.

Open Sign in → My MapLink → Create account with a license. Enter the issued license key, the exact email to which it was issued, your display/community name and a strong password. If email delivery is enabled, verify the address from the message sent to you.

An active installation is one Windows MapLink platform bound to the license. A single Windows installation can manage multiple participating DayZ servers up to the licensed cluster-server limit.

Human-facing downloads are available through My MapLink only. The account must be active, the email address verified, at least one linked license must be usable for the requested release channel, and the current EULA must be accepted before the portal issues a download ticket.

The EULA defines the rights granted by a MapLink license and the restrictions on redistribution, rebranding, modified distribution and circumvention of licensing/security mechanisms. The acceptance checkbox is not preselected. My MapLink records the EULA version and a cryptographic hash of the accepted terms.

No, except where a mandatory legal right applies or MapLink gives written authorization. Documented server configuration is allowed, but the standard license does not permit publishing altered MapLink builds, removing attribution, rebranding MapLink or claiming authorship of MapLink code, binaries or documentation.

A web download ticket is short-lived and one-time. The current portal issues it for ten minutes and binds it to the signed release, customer account, selected license, channel and accepted EULA version.

Yes. Deactivate the old installation from My MapLink when possible, then activate the replacement installation. If the old host is lost, an administrator can revoke its activation.

MapLink uses short-lived cryptographically signed license leases with a bounded offline-grace period. A brief portal outage does not stop DayZ. Once the permitted lease/grace window expires, new MapLink transfers can be blocked until validation succeeds again.

No. Licensing is scoped to MapLink functionality. It must not stop DayZ, CFTools or the local Control Center. Expired/revoked licensing blocks new transfer authorization after the signed lease rules require it.

No. Account passwords are stored as password hashes. License keys are stored as one-way hashes after the one-time plaintext display. A key can be rotated, not recovered from the database.

Install it on the Windows host that has local access to the participating DayZ server environment. The recommended default is under Program Files, but the installer allows another dedicated local folder.

The finished installer and Control Center are intended to handle prerequisites and configuration for normal operators. JSON and command-line tools remain advanced/recovery options rather than the routine setup workflow.

MapLink Core is installed through Steam Workshop as a normal DayZ client mod on every participating server. Players connect with the same Workshop mod loaded. It is not a separate serverMod-only copy.

Yes. Configure the join password for that server in the local Control Center. MapLink uses it for its automatic admission reconnect and target handoff; the password is treated as a local secret.

For routes configured to require an online target, yes. Preflight rejects the transfer before destructive steps if the target is unavailable.

No. Normal administration is local-only. Only your existing DayZ game/query ports and any infrastructure you intentionally expose remain public.

A cluster is the set of DayZ servers that share the same MapLink authority. Each server has a stable ID, world/map identity, connection endpoint and runtime compatibility information.

Only within the limits explicitly granted by that license. “Active installations” counts Windows MapLink platform installations, while “servers in cluster” limits the DayZ servers managed by an entitled cluster. Use separate entitlements when independent production environments require separate installations beyond the licensed limit.

No. Routes are directional. Server A → Server B and Server B → Server A are separate routes so operators can use different terminals, arrival points, rules or enablement states in each direction.

A terminal is the configured source area where a player is eligible to start a route. It normally includes coordinates, radius and optional vertical limits. The player must remain within the allowed area during the countdown.

The arrival point is the validated target position used after restore. Configure a safe location that cannot place the player inside geometry, restricted zones or unsafe map edges.

Yes. Multiple terminals can lead to the same or different target servers. Give each terminal a stable ID and descriptive name so audit logs and diagnostics remain understandable.

The Control Center keeps incomplete or unsafe routes disabled. Typical causes are a missing target mapping, invalid terminal geometry, absent arrival coordinates, incompatible Core/Broker contract or an unavailable required target.

The normal flow is: enter/use terminal → preflight → countdown → character snapshot/prepare → controlled disconnect → main menu → automatic target connection → claim/restore → verify → commit.

No. A successful handoff is designed to reconnect the client to the configured target automatically.

The transfer is cancelled. MapLink continuously validates the configured departure bounds until the transfer enters the prepared phase.

No transfer is started. The Control Center/Broker records an actionable reason such as outside terminal, target offline, route disabled, compatibility mismatch or pending recovery state.

MapLink uses explicit prepared/recovery states rather than pretending the transfer succeeded. Recovery logic is designed to preserve authority and prevent duplicated or silently lost character state.

The committed destination becomes the authoritative current server/map. A later normal login therefore returns the player there until another successful MapLink transfer changes authority.

No. Character death is not used as a substitute for a transfer contract. Production-safe source cleanup and restore logic must be explicitly certified by the installed release.

The Update Center checks signed release metadata, downloads the package, verifies hashes/signatures, creates a transactional backup, installs MapLink components, checks Broker health and rolls back if activation fails.

Only compatible Windows/backend updates may be eligible for automatic installation when the operator enables that policy. Updates that change the DayZ transfer contract require a guarded Core/Workshop synchronization step.

Update the same MapLink Core Workshop item on every participating server through your normal Workshop/CFTools workflow, ensure clients receive that version, then let the Control Center verify exact compatibility before enabling the matching Windows release.

No. MapLink update operations are scoped to MapLink services. When a DayZ maintenance window is required for a contract-changing release, DayZ is stopped/restarted through the existing server manager.

The updater is designed to keep transactional backups of managed files and restore the previous working MapLink state if the new Broker cannot pass health validation.

DayZ join passwords and local runtime secrets remain on the MapLink host. Portal account passwords, license keys and activation tokens are stored as one-way hashes where recovery of the plaintext is not required.

Activation requests can include the license key, installation ID, a one-way machine-fingerprint hash, cluster ID and product version. Refreshes use a separate activation token rather than repeatedly sending the license key.

The current portal does not require advertising, cross-site tracking or behavioural analytics. Authenticated areas use strictly necessary security/session cookies. See Privacy for the current processing inventory.

Admin access controls licenses, activations and security settings. TOTP substantially reduces the risk of a stolen password being enough to compromise the portal. Customers can enable TOTP for My MapLink as well.

Back up the MapLink Windows configuration/data, the portal MariaDB database and the protected portal configuration containing the private license-signing key. Keep at least one encrypted copy outside the production host. Never publish the signing key in support bundles or source control.

Start with Control Center → Diagnostics/Transfer Audit. Use the route/terminal ID, source and target server IDs, player/session identifiers, timestamps and the exact failure code. Generate a sanitized support bundle when escalation is required.

Use the contact shown on the Security and Imprint pages. Do not post private keys, license keys, passwords or unredacted sensitive logs publicly.

No. MapLink is an independent project. DayZ and Bohemia Interactive names and trademarks belong to their respective owners.

Confirm the route is enabled, the target is eligible/online if required, the player is actually inside the configured terminal radius/height and no transfer/recovery state is already pending. The preflight reason is the first diagnostic to read.

Check that source prepare succeeded, the handoff ticket was issued, the target endpoint/port is correct and a required DayZ join password is configured. Then inspect the client handoff and Broker audit entries for the same transfer ID.

Inspect target admission, claim, serializer/restore, arrival validation and commit logs. Do not repeatedly retry or manually edit persistence until the recovery state is understood.

An administrator may revoke a specific activation when a machine is lost or compromised. The license can remain valid for another allowed installation unless the whole license itself is suspended/revoked.

Use Forgot password on the customer sign-in page. A short-lived reset link is sent if transactional email is configured and the account is eligible. Admin accounts use the separate administrative recovery process and TOTP recovery codes.