Companions of the Lance 0.1.0
================================

How to play
-----------
1. Unzip this folder anywhere (keep its files together: Companions.exe needs
   Companions.pck next to it, and so does Companions.console.exe).
2. Run Companions.exe. The Login screen opens with a server list:
   - Krynn (companions.leisureforce.games:7777, encrypted): the public server. The
     connection is encrypted with DTLS and the client only trusts the server's own
     certificate, which ships inside this game. If the server shows any other
     certificate, the client refuses before sending anything.
   - Play solo: your own Chronicle on this computer; nothing leaves the machine.
   - Another server (LAN or custom host): a friend's server on your own network.
     Leave "Encrypted" unticked and accept the warning: only the Krynn server holds
     the key this client trusts, so a friend's server runs unencrypted and your
     password crosses the network in clear. Use it only on a network you trust, and
     never with a password you use anywhere else. "Encrypted" is only for a server
     that holds the official Krynn key (for example the public server reached by its
     address); for any other server it fails with "it is not the Krynn server".
3. Tick "New to the Chronicle (register)" the first time, choose a name (3-16 of
   a-z, 0-9, _) and a password (8-64 characters), then "Inscribe my name". Later,
   choose the server and press "Enter the Chronicle".

Firewall
--------
- Playing online needs outgoing UDP to port 7777. If Windows Defender Firewall asks,
  allow Companions.exe on private and public networks (it never opens a listening
  port for online play).
- Play solo only uses 127.0.0.1 on this computer; no firewall rule is needed.
- Hosting a LAN server for friends needs incoming UDP on the port you choose
  (default 7777) on the hosting PC.

Your data
---------
Settings and the sign-in token live in %APPDATA%\Companions of the Lance\.
Your solo Chronicle's save is there too (folder "save").

Connection check (optional, from a Command Prompt or PowerShell in this folder)
--------------------------------------------------------------------------------
  Companions.console.exe --headless -- --healthcheck
prints "healthcheck ok ... tls=on" (exit code 0) when the public server is up and its
certificate matches, or "healthcheck FAILED ... reason=..." (exit code 1). It never
sends an account or a password. Use Companions.console.exe here: a terminal does not
wait for Companions.exe, so its answer would be lost.

Build
-----
version 0.1.0, content hash 7df357570378761113f14ac0ac1613cdb3e1510ac52e6f6342b947735b17802b
pinned certificate SHA-256 B3:E3:06:FD:8C:78:BE:35:8D:E5:5A:AF:30:72:AB:4B:89:9C:A8:D3:36:78:36:A0:C4:31:B9:D2:3F:CD:E1:86
