R3: Player, server and contributor documentation
- docs/PLAY.md is now the player guide: install from the tarball or .deb, starting a match, controls, how a match goes, settings files and troubleshooting, ahead of the graphics and tested-configuration sections. - docs/SERVER.md: quick start, every option, ports, being found, logs, Docker and systemd, memory, and what was checked. - CONTRIBUTING.md (engine setup, rules, commits, licence of contributions) and CREDITS.md. - README: status and known limitations as they are. - GDD controls table matched to the real defaults (B, Tab, G, 1 to 6). Running the documented commands from an unpacked release found two bugs, fixed here: - `tidewall --connect=HOST` ignored the option unless it came after `--`. ClientConfig.game_args() now takes the game's own options from the engine's arguments when there is no `--`; tested. - A headless run with no mode printed a line and never exited; it quits now. The renderer option is given as the pair the capture tests use (`--rendering-method gl_compatibility --rendering-driver opengl3`) in the docs, the tarball README and the man page. The Join menu only searching the LAN is documented and filed as #82. Closes #62 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Vendored
+2
-1
@@ -1,5 +1,6 @@
|
||||
#!/usr/bin/env sh
|
||||
# Starts Tidewall from wherever this folder is, whatever the current directory, and
|
||||
# through a symlink too. Options are passed to the game (e.g. --rendering-driver opengl3).
|
||||
# through a symlink too. Options are passed to the game (e.g. --connect=HOST, or
|
||||
# --rendering-method gl_compatibility --rendering-driver opengl3).
|
||||
here="$(dirname "$(readlink -f "$0")")"
|
||||
exec "$here/tidewall.x86_64" "$@"
|
||||
|
||||
Reference in New Issue
Block a user