History

Orkuncakilkaya 28e8769a8b fix(input): mouse_dx/dy report no motion on the first frame or across a cursor-mode change The delta was this frame's position minus the last, and the last started at 0,0, so the first frame reported the cursor's whole distance from the corner as motion. A cursor-mode change did the same, switching between a locked cursor's virtual reticle and the real cursor. Maroon Lake's camera adds mouse_dy to its pitch and came up pointing at the ground. examples/library/input_mouse_rebase.ludic covers both cases, plus ordinary motion and re-setting the mode already in force. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-14 15:35:26 +03:00
..
mouse-delta-rebase.md	fix(input): mouse_dx/dy report no motion on the first frame or across a cursor-mode change	2026-09-14 15:35:26 +03:00
README.md	refactor(cli)!: split the contributor tool out of the ludic CLI	2026-09-05 23:15:12 +03:00

Orkuncakilkaya 28e8769a8b fix(input): mouse_dx/dy report no motion on the first frame or across a cursor-mode change

The delta was this frame's position minus the last, and the last started at 0,0, so the
first frame reported the cursor's whole distance from the corner as motion. A cursor-mode
change did the same, switching between a locked cursor's virtual reticle and the real
cursor. Maroon Lake's camera adds mouse_dy to its pitch and came up pointing at the ground.

examples/library/input_mouse_rebase.ludic covers both cases, plus ordinary motion and
re-setting the mode already in force.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-09-14 15:35:26 +03:00

mouse-delta-rebase.md

fix(input): mouse_dx/dy report no motion on the first frame or across a cursor-mode change

2026-09-14 15:35:26 +03:00

README.md

refactor(cli)!: split the contributor tool out of the ludic CLI

2026-09-05 23:15:12 +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