Skip to content

Releases

Labrador 0.4.0

Choose a tag to compare

@matt439 matt439 released this 17 Nov 03:09
Immutable release. Only release title and notes can be modified.

Download labrador-starter-v0.4.0.zip, then follow Get the starter project.

Releases are versioned, and before 1.0 a release promises a record, not compatibility. A 0.x tag promises one thing about the tag before it: every consumer-visible change between the two is an entry in CHANGES.md, with its migration where it has one.

What changed: CHANGES.md at v0.4.0.

The API settles after twelve weeks and two 0.x tags in which CHANGES.md gains no entry. Unmet: CHANGES.md's newest entry is dated 2026-11-17, under this release, so no tag without an entry has been cut since it.

Supported revisions: The latest tag and master are supported; a fix ships as a new tag from master, never as a patch to an old tag. Nothing older than the latest tag receives fixes.

What a release promises: PHILOSOPHY.md at v0.4.0.

labrador-starter-v0.4.0.zip is the Get Started project with this release inside it, built without Git: https://labradorengine.com/docs/get-started/starter/.

labrador-docs-v0.4.0.tar.gz is the website's frozen copy of this release's documentation, published at https://labradorengine.com/versions/v0.4.0/; a reader does not need to download it.

This release adds game-authored HLSL post-processing materials through labrador_add_material: one full-screen post pass with eight float4 parameter groups. The renderer retains the material's source, selection and values across device/context restoration; overlay views remain unprocessed. See Write a post-processing shader.

Direct3D uses the existing shader tools. GL/WebGL2 authoring additionally needs host directx-dxc and spirv-cross dependencies in the game's own manifest. Per-sprite materials, game-owned render targets and multi-pass effects remain separate work.

When moving an engine pin, direct read_sprite_sheet(path, texture) calls now require atlas dimensions as their third argument. Manifest-based loading supplies those dimensions automatically. The linked change list records this and the other source/behaviour migrations, including positional ApplicationOptions construction.

Labrador 0.3.0

Choose a tag to compare

@matt439 matt439 released this 03 Nov 08:09
Immutable release. Only release title and notes can be modified.

The third release of Labrador, a 2D game engine in C++20 for Windows and a desktop browser. It is the first release with its own documentation, frozen at this tag, and the first with a starter ZIP, so Get Started can begin without Git.

Releases are versioned, and before 1.0 a release promises a record, not compatibility. A 0.x tag promises one thing about the tag before it: every consumer-visible change between the two is an entry in CHANGES.md, with its migration where it has one.

Every consumer-visible change since v0.2.0: CHANGES.md, v0.3.0. Moving a game from v0.2.0 meets two source breaks: the math library moved from mattmath to labrador, with its target renamed from MattMath to LabradorMath, and constants are now spelt in snake_case (Vector2F::ZERO is now Vector2F::zero). Update your code for a newer Labrador makes both edits with commands to copy. New public names are not consumer-visible and are not listed there; among those this release adds are a seeded Random that gives the same stream on every platform, hiding and confining the pointer, and controller vibration.

labrador-starter-v0.3.0.zip is the Get Started project with this release inside it, built without Git: Get the starter project.

The settle criterion. The API settles after twelve weeks and two 0.x tags in which CHANGES.md gains no entry; 1.0 is the first tag cut once both have run. Unmet: CHANGES.md's newest entry is d98ef3d, dated 2026-10-29, and no 0.x tag has been cut since it.

Supported revisions. The latest tag and master are supported; a fix ships as a new tag from master, never as a patch to an old tag (SECURITY.md).

What a release promises, and how a public name leaves the engine: PHILOSOPHY, The public face.

Labrador 0.2.0

Choose a tag to compare

@matt439 matt439 released this 25 Oct 21:07

The second release of Labrador, a 2D game engine in C++20 for Windows and a desktop browser. It is the revision Get Started now checks out, so the pin and the guides, which document master, teach the same names again.

Releases are versioned, and before 1.0 a release promises a record, not compatibility. A 0.x tag promises one thing about the tag before it: every consumer-visible change between the two is an entry in CHANGES.md, with its migration where it has one.

Every consumer-visible change since v0.1.0: CHANGES.md, v0.2.0. New public names are not consumer-visible and are not listed there; among those this release adds are white_texture_name, parse_json, add_sound_group, the world point under a pixel on Camera, Scene::remove, the view's camera and viewport on DrawList, a name for every key, and the last frame's CPU phase times from Application. The Get Started project also gains a test target, a smoke test, a browser build and a Windows release folder, each with its guide.

The settle criterion. The API settles after twelve weeks and two 0.x tags in which CHANGES.md gains no entry; 1.0 is the first tag cut once both have run. Unmet: CHANGES.md's newest entry is 1bf68e9, dated 2026-10-25, and no 0.x tag has been cut since it.

Supported revisions. The latest tag and master are supported; a fix ships as a new tag from master, never as a patch to an old tag (SECURITY.md).

What a release promises, and how a public name leaves the engine: PHILOSOPHY, The public face.

Labrador 0.1.0

Choose a tag to compare

@matt439 matt439 released this 13 Oct 11:11

The first release of Labrador, a 2D game engine in C++20 for Windows and a desktop browser.

Releases are versioned, and before 1.0 a release promises a record, not compatibility. A 0.x tag promises one thing about the tag before it: every consumer-visible change between the two is an entry in CHANGES.md, with its migration where it has one.

v0.1.0 has no tag before it, so it records every consumer-visible change since ColourWars' pin, 4cefb68, which CHANGES.md's backfill covers: moving a pin from 4cefb68, in short.

The settle criterion. The API settles after twelve weeks and two 0.x tags in which CHANGES.md gains no entry; 1.0 is the first tag cut once both have run. Unmet: CHANGES.md's newest entry is eaa9b3f, dated 2026-10-11, and no 0.x tag has been cut since it.

Supported revisions. The latest tag and master are supported; a fix ships as a new tag from master, never as a patch to an old tag (SECURITY.md).

What a release promises, and how a public name leaves the engine: PHILOSOPHY, The public face.