Eric chose option B on #72. The drop is now the GDD's launch: - A packet ship sails a seeded straight line past the island, offshore, as close in as it can while keeping 45 m of open water from any land (eight-way probes; up to 32 headings, then the four world sides). - Jump fires the lifeline mortar along the look heading. How high the player aims sets the charge (-10 to 45 degrees: 16 to 110 m/s over the ground; every shot climbs at 75 m/s). The climb can't be steered and the kite can't open until the arc tops out. Riders still aboard at the end are fired towards the middle of the island. - Drop.reach() mirrors the fall for both ways down (kite at the top, or a fall with the kite opening by itself); bots, the soak and autoplay clients and the tutorial pilot aim with Drop.aim_charge(). - Bots fire at their landing spot once abeam of it, when in easy reach at their own staggered moment, or just before the route ends, and open the kite early only when the spot is beyond the rest of a fall. - Art: VesselModels.ship() (two-masted packet, tanned square sails, a salt-white boot-top, a bowsprit and the mortar on its bed, mirrored to face the island), the figure's gull-kite (figure.py), and a lifeline cord from the muzzle to each player still climbing. - Renamed barge to ship and wing-sail to gull-kite throughout code, tests, captures, docs and the tutorial text. make match now defaults to seed 2, where the scripted player still harvests and builds. Closes #72 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.
- Play: docs/PLAY.md: install, controls, how a match goes, graphics and troubleshooting.
- Host: docs/SERVER.md: dedicated servers, options, ports, Docker and systemd.
- Contribute: CONTRIBUTING.md. Credits: CREDITS.md.
Status
v1.0.0. The release gates (all tests, a whole offline match and a 24-client network soak) pass automatically, but the game has not yet been played by a person on real hardware. That playtest (#65) is next, and fixes from it will come as point releases.
What works and is tested automatically:
- Whole matches, lobby to results, offline against bots or on a dedicated server, with up to 24 players and bots.
- The rising tide on every generated island, with flooding that follows the terrain, breakwaters that hold water back, storm surges and sudden death.
- Building walls, floors, ramps, roofs and breakwaters in driftwood, stone and salvage iron, with collapse; harvesting with the boathook; seven weapons, including a harpoon gun and a line thrower, and thrown powder kegs that blast through walls and breakwaters, in four tiers; healing and armor; sea chests and crates.
- Bots at three difficulties. Balance was tuned over 200 bot matches (median match 13 minutes; see docs/BALANCE.md).
- Multiplayer with client prediction, tested with 24 network clients over two matches under simulated latency, jitter and loss; LAN discovery; list servers; joining by address.
- Menus, HUD, chart, settings with rebindable keys, generated art and synthesized sound and music.
- A release tarball and a Debian package, both checked outside the source tree, and a container image for servers. A 50-match run of one server showed no crash and flat memory.
All of this is checked headless or with software rendering in a container. No frame rate on a real GPU, and nothing about how the game feels, has been measured yet.
Known limitations
- Untested on real hardware. No real GPU, Wayland session or hybrid-graphics machine has run it yet (docs/PLAY.md).
- The 1.0.0 packages are solo only. Duos with downs and revives (#30) are on
mainsince 1.0.0 was tagged:--team-size=2on a server,--duosor the Practice menu's Crew offline. Bots play as teammates and revive, but don't otherwise stick together. - Bots carry powder kegs but don't throw them (#83).
- Most bots fall early in a match (#74). Bots build on
mainsince 1.0.0 was tagged (#29), but only cover walls, ramps and a last-stand ring of breakwaters, not forts. The 1.0.0 packages have bots that don't build. - The 1.0.0 packages have no gamepad support, accessibility options or tutorial. All three are on
mainsince 1.0.0 was tagged (#53, #52); the gamepad has only been tested with simulated input. No character customization (#43) or editing of placed pieces (#18). - The Join menu only searches the LAN (#82). List servers work from the command line (
--browse --list=...); in the menu, join other servers by address. - Under OpenGL (the fallback when Vulkan can't start) the sun casts no shadows, because that renderer drew them with washed-out colours (#81).
- One network soak saw a single transient world-hash mismatch that hasn't been reproduced since (#80).
- The name is a working name until it has been cleared.
The milestones and issues track the rest.
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 (LICENSE). Original art and audio: CC BY-SA 4.0 (LICENSE-ASSETS). The Godot engine is MIT-licensed; see CREDITS.md.