ad0fd2695dd775627f4cdcf98fa5ad7cf189c43d
When a match's results begin, Match starts the next match's Simulation on a WorkerThreadPool task (its seed is fixed by then) and collects it when the lobby opens. The same task plans the island's tide levels (Simulation.plan_tide) and runs a prepare_next hook, which ServerLoop uses to build the bots' NavGrid and BotWorld for the island. All of these read only the new simulation, so the results are the ones the main thread would have made: tests compare the state hash, terrain, solids, props, tide levels and navigation with fresh ones, and the ten-matches test still matches its references. A Match freed while its task runs waits for it. Measured: a 24-bot server paced in real time through the results, lobby, countdown and 3 s of the next drop has a worst tick of 5.4 ms; it was 1.8 s. In the 24-client soak at 2% loss, moving the island alone left a 0.82 s tick (the bots' navigation) and moving that too left 74 ms at the next match's start (planning the tide), which this also moves. The soak hasn't been run again since that last step. Closes #79 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tidewall (working name)
A free and open-source third-person battle royale for Linux, made with Godot.
Up to 24 players or bots drop onto a procedurally generated island. Scavenge, fight and build. The sea rises in phases and swallows the low ground, so the last safe land keeps getting higher and smaller, and what you build can keep you above water.
Status: in development. See the milestones and issues. v1.0.0 is targeted for 2026-11-16.
Originality
Tidewall works in the build-and-survive battle royale genre, but it is its own game. Its name, characters, art, audio, world and UI are all original. It contains no assets, names or designs from any commercial game.
Licence
Code: GPL-3.0-or-later. Original art and audio: CC BY-SA 4.0.
Languages
GDScript
93.6%
Shell
3.2%
Python
1.5%
GDShader
0.7%
Makefile
0.5%
Other
0.5%