History

Orkuncakilkaya 182cbf3cc3 fix(render3d): a leaf is not matte Foliage roughness was pinned to 1.0 and grazing Fresnel switched off, so nothing green in the game had a highlight anywhere. The glint off waxy leaves and wet needles is most of what makes a stand look alive rather than painted. The reason it was off is real: a crown is card quads, and at a grazing angle the card's normal is a lie, so a specular lobe frosted whole crowns white against the sky. The sheen returns as its own term gated on exactly that - it fades as the card turns edge-on, which is where its normal stops meaning anything. A tight lobe for the glint, a weak wide one for the waxy rim, nothing at the angles that frosted. Translucency reaches 260 m rather than 140, and a dense crown passes 0.45 of it rather than 0.3, so a backlit stand glows for as far as you can see it. 400 frames: GL 7.1 s, VK 7.4 s. Backends agree to 0.14/255. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>		2026-09-19 16:41:33 +03:00
..
a-leaf-is-not-matte.md	fix(render3d): a leaf is not matte	2026-09-19 16:41:33 +03:00
light-air-and-the-hour.md	feat(render3d): the air and the light are the hour's, not one constant apiece	2026-09-19 14:42:30 +03:00
light-you-can-see.md	feat(render3d): light you can see - sun shafts and valley mist	2026-09-19 16:06:16 +03:00
README.md	refactor(cli)!: split the contributor tool out of the ludic CLI	2026-09-05 23:15:12 +03:00
the-ground-up-close.md	fix(render3d): the ground keeps more of its own colour, and the rock keeps all of it	2026-09-19 16:29:17 +03:00

README.md

Changesets

A changeset is one small Markdown file describing a single user-facing change, dropped in this directory. ludic-dev release consumes every changeset here into a new CHANGELOG.md section, bumps VERSION, and deletes the consumed files.

Format

bump: minor
type: feat
One or more lines describing the change, in the past-agnostic imperative used in
the changelog. Markdown is fine.

bump: — major, minor, or patch (SemVer). The release version is bumped by the highest level among the pending changesets (unless ludic-dev release <level> overrides it).
type: — the Conventional Commit type (feat, fix, perf, docs, …). It decides which group the change lands in: feat → Features, fix → Fixes, perf → Performance, and so on, in that order. A type with no known heading gets one named after itself.

Writing the body

The body is markdown and reaches the changelog as markdown: it becomes one list item, with continuation lines indented to stay inside it. Nested bullets, blank lines between paragraphs and inline code all survive.

bump: minor
type: feat
**Tiled map support** — load and draw Tiled maps.

- **TMX/TSX** — the XML formats, decoded to the same intermediate as JSON.
- **Collision** — the `collision` layer projects onto the engine tilemap.

Lead with the thing that changed, not with the mechanism. A reader scanning the release should be able to stop after your first clause.

Adding one

Create a file with a short, unique name, e.g. changes/regex-namespace.md. Any filename works except this README.md, which the release step always skips.

Preview how the next release will read before cutting it — this writes nothing:

ludic-dev release --dry-run