Sam Sung 94fb118517 The UI ticks on the paced frame step the world gets (#1870) ...

The UI ticked on raw `Time<Real>`, which under pipelined rendering mis-splits shown frames (26.4 and 8.0 ms for two 16.7 ms frames), so a held paperdoll arrow turned in uneven steps while the bones, on paced `Time<Virtual>`, did not.

1.12.1 hands `OnUpdate` the loop's own frame time, unclamped (`0x420f70` → `0x885608` → `0x76b2c0`).

Now the pacer publishes one step per frame (`FrameStep`) that `Time<Virtual>` and the UI both read: `OnUpdate`'s elapsed, `GetTime` (a `Deviation:`, since 1.12.1 reads its clock live at `0x515ea0`), the cooldown anchor, aura expiries and `GetFramerate`. A stall reaches the UI whole. The pacer keeps every millisecond, drains its carry, and no longer jumps after a pause or splits a long hitch. Tests replay a stream measured on this machine.

Fixes #1846

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

2026-10-18 10:58:30 +07:00

..

CONTRIBUTING.md

Run the script host on benilla-lua; remove the vendored C Lua and mlua (#1255)

2026-10-17 08:51:37 +07:00

DEVIATIONS.md

The UI ticks on the paced frame step the world gets (#1870)

2026-10-18 10:58:30 +07:00

MAP.md

The Lua library answers as 1.12.1's does (#1862)

2026-10-18 10:35:43 +07:00

METHOD.md

A player-clippy gate lints the shipped player build (#1471)

2026-10-16 20:03:00 +07:00