Repository navigation
Hydra v0.1.0-beta.2
Pre-release
Pre-release
HydraFE for the phone ships through TestFlight, not as a file here.
The Linux build needs glibc 2.39 or newer (Ubuntu 24.04 and later,
or a comparably recent distro).
Changes since v0.1.0-beta.1
- One Menu, on the hub and on every play window's title bar
- Settings holds every editor, and lists the tools
- The badge brightened: it read too dark on a taskbar
- Hydra's badge, the one icon everywhere
- Triggers, by name: every word a player reads that said highlight
- The Ebon Gate merchants, and pictures a script places in the story
- Packs listed by kind and by tens; compass sets in both layouts
- The Compass widget draws a compass set: its rose, each way out lit
- The ready signals wait for the game's settings: team logins all come in
- A blank line the game sends is drawn a line tall
- Whitespace inside a game panel's markup is not text
- A key is caught with its modifier held, not as the modifier
- Restart now: Hydra starts again into the update, its characters with it
- The hub and the tray offer a newer Hydra, and fetch it
- hydra-update: a newer release found, fetched, checked and put in place
- A release names its beta, and signs its checksums
- A window's title takes a colour and a size of its own
- A bar's words take a colour and an outline of the player's own
- The Command line widget draws the command line inside itself
- The story's newest line holds the bottom in the frame lines come
- Custom indicators: a name, a look, and a rule of the player's own
- Indicators as icons: a sheet's cell or a picture, its size, hidden while off
- Floating windows: a widget window's background, down to clear, and kept above the others
- Keep on top: the settings menu and every editor window; Add a widget above every widget window
- Indicators: one the game has not reported is drawn off, with no question mark
- The guide's hub picture, the author's new screenshot
- Highlights: .highlight import reads Vellum's too
- The windows open on Vulkan where a graphics card has it, and say what their opening took
- Cards: the name and the connection each a part of its own
- The guide: the hub with characters playing, and the tray menu, from the author's screenshots
- The Mac app keeps its files in Application Support; the Windows exe carries its C runtime
- The guide needs mdBook alone: the install page has a section per system, not tabs
- The guide's first pages: how Hydra works, and getting started
- The guide's pictures, drawn by the GUI's tests
- Hydra opens with no console window, and logs how long its start takes
- The guide: an mdBook at the docs site's root, the API reference under api/
- The Windows jobs run their steps under bash
- The Windows steps every build runs are cmd, not PowerShell
- The Mac builds skip the cache action too
- Releases and the docs site go to the public hydra repository
- The Windows jobs put Git's bash on their own PATH
- Snapshot tolerances per operating system
- The Mac builds ask for the Mac by name