Skip to content

Configuration Game and Interface

smallketchup82 edited this page Oct 29, 2026 · 3 revisions

Start message and commander marker

Open the lobby’s Settings → Game tab. Both options default to On and can be changed independently:

Setting Behavior
ZkMacOS start message Sends Playing on ZkMacOS; sorry if technical issues disconnect me. to all chat when a game starts
ZkMacOS start marker Places a shared Playing on ZkMacOS map marker at your starting commander’s spawn position

They do not announce while spectating, watching a replay, or reloading the UI mid-game. The marker waits until the game’s initial marker cleanup has finished, then remains as an ordinary shared map marker. The widget uses your owned commander in shared teams.

The manual engine settings are MacAnnounceChat = 1 and MacAnnounceMarker = 1; use 0 to turn either off. Saved lobby selections are reapplied on later launches.

Window and cursor behavior

The lobby has separate display choices for the menu and game. Both start windowed. To change mouse capture, use Settings → Interface → Mouse Cursor → Lock Cursor to Window in game; it starts disabled.

Notchful fullscreen is optional and requires a full app restart. Its resource-bar layout activates only when the window actually covers the notch.

Steam login

Start the normal macOS Steam client and sign in before opening Zero-K. Use the lobby's Steam login option; the bundled helper handles the connection to Steam. You do not need a macOS Zero-K installation from the Steam store, and the app does not bundle the Steam client or anyone else's account.

Steam is optional. Use ordinary Zero-K account login or offline play if you do not want Steam integration. If Steam login does not respond, check that Steam is running and signed in, then fully quit and reopen Zero-K.

First-launch warning

The startup warning is acknowledged separately for each app version. Acknowledgments are stored in startup-warning-versions.json under Application Support. The warning links to the ZkMacOS issue tracker and explains the risks of using an experimental third-party client.

Crash and error reporting

All reporting controls now live in Settings → Telemetry. See Telemetry for automatic reporting, per-report consent, optional attachments, privacy, the restart-required master switch and manual bug reports.

Clone this wiki locally