make stability (tools/stability.sh, StabilityReport) runs one dedicated server for 50 bot matches back to back, unthrottled, sampling its resident memory, and fails on a crash, hang, engine or script error, a match with no winner, or memory that grows after the first five matches. The first run had no crash, hang or error, but showed two leaks: - ServerLoop kept every tick's duration in an array (8 bytes a tick, about 21 MB a day at 30 Hz) and copied and sorted all of it for every progress line. TickTimes keeps exact statistics in fixed memory: a one-microsecond histogram up to 65 ms, plus the rare slower ticks. - Resident memory grew about 28 MB a match (905 MB after 42 matches): glibc gives each thread its own malloc arena, and every next island is built on a worker thread. The server launchers (packaging/server, packaging/dist, so also the .deb, Docker image and systemd unit) and tools/godot.sh for --server now set MALLOC_ARENA_MAX=1 unless already set. Tick times were unchanged (p50 501 vs 507 us, p99 1635 vs 1625). After: 50 matches (seed 4242) in 756 s, all with a winner, exit 0, no errors; static memory +1.6 KiB and resident +145 KiB a match, flat at 204 MB from match 26 on. No match crashed, so there is no crash seed to turn into a regression test. Tests: TickTimes against a sorted list, its fixed memory, the launchers' setting, and StabilityReport. make check, dist-check and server-package-check pass. Closes #57 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tidewall for Linux (x86_64)
A free and open-source build-and-survive battle royale. The sea rises in phases and swallows the low ground, so the last dry land keeps getting higher and smaller.
Play
./tidewall
tidewall starts the game from this folder whatever directory you are in, and works
through a symlink too (for example ln -s "$PWD/tidewall" ~/.local/bin/tidewall).
To add Tidewall to your desktop's application menu, for you alone:
./install-desktop-entry.sh
Run it again if you move the folder, and ./install-desktop-entry.sh --remove to take
the entry away. On Debian or Ubuntu, the .deb package does all of this system-wide.
The game opens on its main menu: practice against bots offline, or join a server on
your network or by address. It needs a Vulkan-capable GPU and driver (Forward+). On
hardware without Vulkan, start it with --rendering-driver opengl3 to use OpenGL.
Settings and key bindings are saved in ~/.local/share/godot/app_userdata/Tidewall/.
Run a server
./tidewall-server --config=server.cfg
server.cfg is an example: it takes players over UDP on port 24650, answers LAN
discovery on 24651, and fills empty places with bots. Every option can also be given
on the command line (--port=24650, --bots=1, --name=...). SIGTERM or Ctrl+C stops
the server cleanly. Logs are JSON lines on standard output.
What's here
| File | |
|---|---|
tidewall |
Starts the game |
install-desktop-entry.sh |
Adds the game to your application menu |
tidewall.x86_64 |
The Godot 4.7.2 engine (official release template) |
tidewall.pck |
The game |
tidewall-server |
Runs the same game headless as a dedicated server |
server.cfg |
Example server configuration |
VERSION |
Version, commit and engine |
tidewall.png |
The application icon |
PROVENANCE.md |
How every model, texture and sound was made |
ENGINE-LICENSES.txt |
The Godot engine's licence and the notices of the code built into it |
Licence
Code: GPL-3.0-or-later (LICENSE). Art and audio, all generated by scripts in the
source repository: CC BY-SA 4.0 (LICENSE-ASSETS). The Godot engine is MIT-licensed;
its licence and the notices of the third-party code built into it are in
ENGINE-LICENSES.txt.