Evaluate Luanti 5.12+ camera API and set a minimum engine version #8

Closed
opened 2026-11-07 18:27:40 +00:00 by claude · 1 comment
Member

5.12 adds a server-side set_camera API. Investigate whether it allows a fixed third-person side camera, removing the attachment rig and server-side movement (and with it the input latency). Decide on min_minetest_version for game.conf. Debian 13 ships 5.10.

5.12 adds a server-side `set_camera` API. Investigate whether it allows a fixed third-person side camera, removing the attachment rig and server-side movement (and with it the input latency). Decide on `min_minetest_version` for game.conf. Debian 13 ships 5.10.
claude added this to the v0.2 Core Feel milestone 2026-11-07 18:27:40 +00:00
claude added the
type
tech
priority
medium
area/camera-controls
labels 2026-11-07 18:27:40 +00:00
eric added this to the Strata Roadmap project 2026-11-07 18:36:27 +00:00
eric moved this to To Do in Strata Roadmap on 2026-11-07 18:37:23 +00:00
eric closed this issue 2026-11-09 06:18:31 +00:00
Author
Member

Result: set_camera doesn't help, so the minimum engine stays at 5.10 (9f9d0af).

I checked the current upstream doc/lua_api.md on the master branch, which documents features up to 5.16. ObjectRef:set_camera(params) has one field, mode: any, first, third or third_front (client support since 5.12.0). It only picks which of the existing camera modes the player gets. It can't position a camera or separate it from the look direction, and I found no other API that does. So the rig and server-side movement stay, and the input latency with them.

I judged this from the API documentation, so I didn't build a branch or try a newer engine: there's no parameter to build on.

  • game.conf now has min_minetest_version = 5.10, the version the tests and CI run on.
  • docs/DESIGN.md no longer implies 5.12 brings a free camera.
  • The one useful part is mode = "first", which locks the C toggle on 5.12+. That went into #10.

Per the plan Eric approved on #7, #7 is parked (see that issue).

**Result: `set_camera` doesn't help, so the minimum engine stays at 5.10** (9f9d0af). I checked the current upstream `doc/lua_api.md` on the `master` branch, which documents features up to 5.16. `ObjectRef:set_camera(params)` has one field, `mode`: `any`, `first`, `third` or `third_front` (client support since 5.12.0). It only picks which of the existing camera modes the player gets. It can't position a camera or separate it from the look direction, and I found no other API that does. So the rig and server-side movement stay, and the input latency with them. I judged this from the API documentation, so I didn't build a branch or try a newer engine: there's no parameter to build on. - `game.conf` now has `min_minetest_version = 5.10`, the version the tests and CI run on. - `docs/DESIGN.md` no longer implies 5.12 brings a free camera. - The one useful part is `mode = "first"`, which locks the C toggle on 5.12+. That went into #10. Per the plan Eric approved on #7, #7 is parked (see that issue).
Sign in to join this conversation.