Aeternalis Evolution - engineering client {{IDENTITY}}
=====================================================

Internal engineering test build. No licence is granted for this software; do not
redistribute it. Third-party components keep their own licences: see
THIRD-PARTY-NOTICES.txt and the LICENSES folder.

Built from commit {{COMMIT}} ({{COMMIT_TIME}} UTC). BUILD-INFO.txt lists the
toolchain and dependency versions; SHA256SUMS.txt lists every file's checksum.
Please quote the identity printed by `evo-client --version` in every report.

Requirements
------------
Windows 10 or 11, x64. No installer and no Visual C++ redistributable is needed:
the client uses the static Microsoft C++ runtime and only Windows system DLLs plus
the bundled SDL3.dll and msquic.dll. Minimum hardware is not yet qualified.

Running
-------
Extract the whole folder anywhere and run evo-client.exe. A launcher opens:

* Local fixture - an in-memory stand-in for an environment with static organisms.
  It is not a server, not an ecosystem and not authoritative.
* Connect to a dev region - needs an endpoint (default: the dev route,
  void.aeternalisgames.com:7400, UDP), the server name, the dev CA file
  (dev-ca.pem) and a grant bundle file. These are issued separately by the
  development team and are never part of this package. Files are read when you
  press Connect; nothing is saved. Do not share grant bundles: each grant opens one
  session, a bundle expires as a whole, and a second client using the same bundle
  takes the session over. The view follows the region until you pan; then it
  follows the camera (15 x 15 cells around it).

Controls (defaults, rebindable in Controls...): W A S D move, arrow keys pan,
mouse wheel zooms, left click selects, Tab toggles UI capture. Key names refer to
US-layout key positions. Changed controls are saved in
%APPDATA%\Aeternalis Games\Evolution Engineering Client\controls-v1.txt.
No other settings, logs or credentials are written by the client.

Useful options: --version, --fixture, --renderer software, --controls FILE.
Any unknown option prints the full usage.

Verifying the download
----------------------
The .zip is accompanied by a .zip.sha256 file. Inside the folder, every file's
SHA-256 is listed in SHA256SUMS.txt (for example: Get-FileHash -Algorithm SHA256).
