A fast 2D and 3D game engine — TypeScript SDK, C++/WebAssembly core, visual editor. Ship one project to web, desktop, WeChat MiniGames, playable ads, and native Android / iOS.
TypeScript 2d-game-engine3d3d-game-engineandroidcppecsgame-editorgame-enginegamedeviostypescriptwebassemblywebglwebgpuwechat-minigame
chore: release v0.73.0
esenginefc098924aace
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 00a9779d5..2d70bce5c 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -14,18 +14,20 @@ published separately; it ships inside the editor.## [Unreleased]+## [0.73.0] - 2026-09-25+### Added-- The Frame Debugger captures and replays the frame of a connected native build (desktop and Android) as it does a web or mini-game one.-- A native development build names its device to the editor — `macOS · Mac16,10`, `Android · Pixel 8` — as web and mini-game builds already did.-- A desktop (native) development build connects to the editor like a web or mini-game one — log, profiler, the world, content status, pause and step; its renderer cannot capture frames yet and says so. The native host gained a `ws://` client for it.-- Profiling a connected development build, the Profiler shows which content revision it runs, the one its next launch starts on, and a hot update it has found but not applied; `device_update_status` answers the same for an agent.-- The build's size report shows the start screen on its own line — the markup and any logo inlined into index.html, which is on screen before anything else loads.-- Connected development builds are named by the device they run on — `web (Chrome · Android)`, a phone's model on a mini-game — and numbered when two read alike, in the Profiler, Outliner, Frame Debugger and `device_targets`.-- Profiling a connected development build, the Profiler's Frame section shows what its debug channel costs the device per frame (and `profile_frames` reports it as `channelMs`).-- In the Outliner, a connected development build's world can be shown instead of this editor's (read-only, with live values in Details).-- A development build connected to the editor shows its log in the Output Log (from before the editor connected, too), can be profiled in the Profiler on its own frame clock, and can be paused, stepped and frame-capped from there; the log says which project and content version connected.-- The Frame Debugger can capture and replay a frame of a development build running outside the editor — a browser or a mini-game host, on this machine or another on the network: export with the Development configuration and "Frame debugger connection", then pick the device in the panel. Native apps cannot connect yet.+- **A connected native build's frame can be captured and replayed.** The Frame Debugger does it for desktop and Android builds as it does for a web or mini-game one.+- **A native development build names its device to the editor.** `macOS · Mac16,10`, `Android · Pixel 8` — as web and mini-game builds already did.+- **A native development build connects to the editor.** Desktop and Android, like a web or mini-game one — log, profiler, the world, content status, pause and step. The native host gained a `ws://` client for it.+- **The Profiler shows which content revision a connected build runs.** Also the one its next launch starts on, and a hot update it has found but not applied; `device_update_status` answers the same for an agent.+- **The build's size report shows the start screen on its own line.** The markup and any logo inlined into index.html, which is on screen before anything else loads.+- **Connected development builds are named by the device they run on.** `web (Chrome · Android)`, a phone's model on a mini-game — numbered when two read alike, in the Profiler, Outliner, Frame Debugger and `device_targets`.+- **The Profiler shows what the debug channel costs a connected build per frame.** In its Frame section; `profile_frames` reports it as `channelMs`.+- **The Outliner can show a connected development build's world.** Instead of this editor's — read-only, with live values in Details.+- **A development build connected to the editor can be watched and driven from it.** Its log shows in the Output Log (from before the editor connected, too); it can be profiled in the Profiler on its own frame clock and paused, stepped and frame-capped from there; the log says which project and content version connected.+- **The Frame Debugger can capture and replay a frame of a development build running outside the editor.** A browser or a mini-game host, on this machine or another on the network: export with the Development configuration and "Frame debugger connection", then pick the device in the panel.### Fixed@@ -13707,7 +13709,8 @@ not kept before this file was introduced — see the Git history at`github.com/esengine/estella` for the full commit-level record since the firstcommit on 2026-01-25.-[Unreleased]: https://github.com/esengine/estella/compare/v0.72.0...HEAD+[Unreleased]: https://github.com/esengine/estella/compare/v0.73.0...HEAD+[0.73.0]: https://github.com/esengine/estella/compare/v0.72.0...v0.73.0[0.72.0]: https://github.com/esengine/estella/compare/v0.71.0...v0.72.0[0.71.0]: https://github.com/esengine/estella/compare/v0.70.0...v0.71.0[0.70.0]: https://github.com/esengine/estella/compare/v0.69.0...v0.70.0diff --git a/SECURITY.md b/SECURITY.mdindex eae408580..7c3e3fa6b 100644--- a/SECURITY.md+++ b/SECURITY.md@@ -7,8 +7,8 @@ upgrading to the latest release is the supported path to a fix.| Version | Supported ||---------|-----------|-| 0.72.x | Yes |-| < 0.72 | No |+| 0.73.x | Yes |+| < 0.73 | No |`tools/check-release-metadata.mjs` fails the build if this table stops matchingthe version being shipped, so it cannot quietly fall behind again.diff --git a/desktop b/desktopindex e99bc068c..2ee68a2b8 160000--- a/desktop+++ b/desktop@@ -1 +1 @@-Subproject commit e99bc068ca3fd25138aee21d143d0723f7805400+Subproject commit 2ee68a2b82c1b9a1f582d8f399e17c88f41e8be9diff --git a/package.json b/package.jsonindex 6df76dd13..8fc9f6c59 100644--- a/package.json+++ b/package.json@@ -1,6 +1,6 @@{"name": "estella",- "version": "0.72.0",+ "version": "0.73.0","private": true,"type": "module","description": "Estella - A fast 2D/3D game engine powered by WebAssembly and ECS",diff --git a/tools/goldenProjects.mjs b/tools/goldenProjects.mjsindex 6c47d8e70..3719819da 100644--- a/tools/goldenProjects.mjs+++ b/tools/goldenProjects.mjs@@ -90,6 +90,27 @@ export const CENSUS_FLOOR = '0.60.0';* that does not exist, and release notes are a different act. Theirs is ungated.*/export const SHIPPED = {+ // — 0.73.0 —+ 'A connected native build\'s frame can be captured and replayed':+ { notCertifiable: 'a development tool over a frame the game already draws; sdk/tests/frame-capture-copy.test.ts holds the native read path, and it was run on the macOS host and in the Android emulator' },+ 'A native development build names its device to the editor':+ { notCertifiable: 'how the editor labels a connected build, not something a game does; sdk/tests/native-host-bridge.test.ts holds it' },+ 'A native development build connects to the editor':+ { notCertifiable: 'a development build\'s line to the editor, which no shipping game carries; sdk/tests/native-socket.test.ts holds the socket, and it was run on the macOS host and in the Android emulator' },+ 'The Profiler shows which content revision a connected build runs':+ { notCertifiable: 'an editor readout of a device\'s hot-update state; the remote-frame-debugger editor check and verify-remote-capture (web and WeChat) hold it' },+ 'The build\'s size report shows the start screen on its own line':+ { notCertifiable: 'a line in the build report, not game behaviour; pipeline/tests/export-splash.test.ts holds it' },+ 'Connected development builds are named by the device they run on':+ { notCertifiable: 'how the editor labels a connected build; the remote-frame-debugger editor check and verify-remote-capture (web and WeChat) hold it' },+ 'The Profiler shows what the debug channel costs a connected build':+ { notCertifiable: 'an editor readout of the channel\'s own cost; the remote-frame-debugger editor check and verify-remote-capture (web and WeChat) hold it' },+ 'The Outliner can show a connected development build\'s world':+ { notCertifiable: 'an editor view of a device\'s world, read-only; the remote-frame-debugger editor check and verify-remote-capture (web and WeChat) hold it' },+ 'A development build connected to the editor can be watched and driven from it':+ { notCertifiable: 'development tooling around a build no shipping game is; the remote-frame-debugger editor check and verify-remote-capture (web and WeChat) hold it' },+ 'The Frame Debugger can capture and replay a frame of a development build running outside the editor':+ { notCertifiable: 'development tooling over a frame the game already draws; the remote-frame-debugger editor check and verify-remote-capture (web and WeChat) hold it' },// — 0.72.0 —'A frame can be captured draw call by draw call, and replayed up to any one of them.':{ notCertifiable: 'an editor panel and three agent tools over a frame the game already draws; the frame-debugger editor check and the frame-debugger-2d/3d/split render scenes hold it on both backends' },diff --git a/tools/releaseNotes.mjs b/tools/releaseNotes.mjsindex 526646d74..d36ba274b 100644--- a/tools/releaseNotes.mjs+++ b/tools/releaseNotes.mjs@@ -1057,23 +1057,23 @@ export const NOTED = {'fix(recorder): a Douyin recording the host ends on its own keeps its video':{ note: 'A Douyin recording the host ends on its own keeps its video, and an interruption is not counted as recorded time.' },'feat(frame-debugger): a development build can be captured from the editor over the network':- { note: 'The Frame Debugger can capture and replay a frame of a development build running outside the editor — a browser or a mini-game host, on this machine or another on the network: export with the Development configuration and "Frame debugger connection", then pick the device in the panel. Native apps cannot connect yet.' },+ { note: 'The Frame Debugger can capture and replay a frame of a development build running outside the editor.' },'feat(frame-debugger): capture a frame from a development build running elsewhere':- { note: 'The Frame Debugger can capture and replay a frame of a development build running outside the editor — a browser or a mini-game host, on this machine or another on the network: export with the Development configuration and "Frame debugger connection", then pick the device in the panel. Native apps cannot connect yet.' },+ { note: 'The Frame Debugger can capture and replay a frame of a development build running outside the editor.' },'fix(hot-update): an update says which stages it reached, and the next launch starts on a whole version':{ note: 'A hot update reports how far it got — verified, applied, stored for the next launch, cached for offline — instead of one `ok`; two updates at once no longer both commit or lose the newer one; and an update stored by an older build no longer covers a newer one the player installed.' },'fix(minigame): a hot update reaches a mini-game, and survives its next launch offline':{ note: 'A hot update on a mini-game is stored for the next launch and its assets are cached on the device, so the updated game starts offline; before, a mini-game went back to what shipped.' },'feat(debug): a development build\'s log, frame stats and controls reach the editor':- { note: 'A development build connected to the editor shows its log in the Output Log (from before the editor connected, too), can be profiled in the Profiler on its own frame clock, and can be paused, stepped and frame-capped from there; the log says which project and content version connected.' },+ { note: 'A development build connected to the editor can be watched and driven from it.' },'feat(profiler): a development build\'s frames, log and clock, read and driven from the editor':- { note: 'A development build connected to the editor shows its log in the Output Log (from before the editor connected, too), can be profiled in the Profiler on its own frame clock, and can be paused, stepped and frame-capped from there; the log says which project and content version connected.' },+ { note: 'A development build connected to the editor can be watched and driven from it.' },'fix(app): a frame-rate cap keeps a cadence, so 30 on a 60 Hz display is 30':{ note: 'A frame-rate cap now holds: `setTargetFrameRate(30)` on a 60 Hz display runs at 30, not 24.' },'feat(debug): a device answers with its world, and a question asked while it boots waits':- { note: 'In the Outliner, a connected development build\'s world can be shown instead of this editor\'s (read-only, with live values in Details).' },+ { note: 'The Outliner can show a connected development build\'s world.' },'feat(outliner): a connected build\'s world, shown read-only beside this editor\'s':- { note: 'In the Outliner, a connected development build\'s world can be shown instead of this editor\'s (read-only, with live values in Details).' },+ { note: 'The Outliner can show a connected development build\'s world.' },'feat(debug): the debug channel reports what it costs the game it watches':{ internal: 'a number the channel reports for its own budget check; the profiler does not show it yet' },'fix(minigame): a WeChat development build reaches the editor, and its replays come back':@@ -1101,13 +1101,13 @@ export const NOTED = {'fix(debug): a device in the background refuses a capture at once':{ note: 'Capturing a development build whose tab is in the background says so at once, instead of waiting 30 seconds for a frame the browser will not draw.' },'feat(profiler): the Profiler shows what a connected device spends on its debug channel':- { note: 'Profiling a connected development build, the Profiler\'s Frame section shows what its debug channel costs the device per frame (and `profile_frames` reports it as `channelMs`).' },+ { note: 'The Profiler shows what the debug channel costs a connected build per frame.' },'feat(profiler): a device\'s frame shows what its debug channel costs':- { note: 'Profiling a connected development build, the Profiler\'s Frame section shows what its debug channel costs the device per frame (and `profile_frames` reports it as `channelMs`).' },+ { note: 'The Profiler shows what the debug channel costs a connected build per frame.' },'feat(debug): a connected build says what device it runs on':- { note: 'Connected development builds are named by the device they run on — `web (Chrome · Android)`, a phone\'s model on a mini-game — and numbered when two read alike, in the Profiler, Outliner, Frame Debugger and `device_targets`.' },+ { note: 'Connected development builds are named by the device they run on.' },'feat(debug): connected builds are named by the device they run on':- { note: 'Connected development builds are named by the device they run on — `web (Chrome · Android)`, a phone\'s model on a mini-game — and numbered when two read alike, in the Profiler, Outliner, Frame Debugger and `device_targets`.' },+ { note: 'Connected development builds are named by the device they run on.' },'fix(debug): a shipping package no longer carries the debug channel':{ note: 'A shipping package no longer carries the development debug channel\'s code (13 KB on a WeChat package): only a development export that names an editor imports it, as `esengine/debug-channel`.' },'fix(net): a mini-game socket whose dial is refused on a phone redials':@@ -1119,21 +1119,21 @@ export const NOTED = {'fix(minigame): the pixel ratio is read once, not on every frame':{ note: 'A mini-game reads the host\'s pixel ratio once and again after a resize, instead of calling getSystemInfoSync several times a frame (on vivo, a synchronous call across its bridge each time).' },'feat(export): the size report says what the start screen weighs':- { note: 'The build\'s size report shows the start screen on its own line — the markup and any logo inlined into index.html, which is on screen before anything else loads.' },+ { note: 'The build\'s size report shows the start screen on its own line.' },'feat(build): the size panel names what the start screen weighs':- { note: 'The build\'s size report shows the start screen on its own line — the markup and any logo inlined into index.html, which is on screen before anything else loads.' },+ { note: 'The build\'s size report shows the start screen on its own line.' },'feat(debug): a connected build reports its hot-update status to the editor':- { note: 'Profiling a connected development build, the Profiler shows which content revision it runs, the one its next launch starts on, and a hot update it has found but not applied; `device_update_status` answers the same for an agent.' },+ { note: 'The Profiler shows which content revision a connected build runs.' },'feat(profiler): a connected build says which content it runs and what update waits':- { note: 'Profiling a connected development build, the Profiler shows which content revision it runs, the one its next launch starts on, and a hot update it has found but not applied; `device_update_status` answers the same for an agent.' },+ { note: 'The Profiler shows which content revision a connected build runs.' },'feat(native): a native build can connect to the editor over the debug channel':- { note: 'A desktop (native) development build connects to the editor like a web or mini-game one — log, profiler, the world, content status, pause and step; its renderer cannot capture frames yet and says so. The native host gained a `ws://` client for it.' },+ { note: 'A native development build connects to the editor.' },'feat(build): a desktop development build can dial the editor':- { note: 'A desktop (native) development build connects to the editor like a web or mini-game one — log, profiler, the world, content status, pause and step; its renderer cannot capture frames yet and says so. The native host gained a `ws://` client for it.' },+ { note: 'A native development build connects to the editor.' },'fix(android): a native Android app can reach the network':{ note: 'A native Android app can reach the network: its manifest never asked for it, so a remote group\'s assets, hot updates and the debug channel all failed on Android. A development build also allows plain http (a LAN CDN); a shipping build is held to https, and the export warns when its CDN is http.' },'feat(native): a native build names its device when it connects':- { note: 'A native development build names its device to the editor — `macOS · Mac16,10`, `Android · Pixel 8` — as web and mini-game builds already did.' },+ { note: 'A native development build names its device to the editor.' },'feat(build): an Android development build can dial the editor':{ note: 'A native Android app can reach the network: its manifest never asked for it, so a remote group\'s assets, hot updates and the debug channel all failed on Android. A development build also allows plain http (a LAN CDN); a shipping build is held to https, and the export warns when its CDN is http.' },'test(android): a Studio project\'s manifest has every placeholder filled':@@ -1141,5 +1141,5 @@ export const NOTED = {'fix(android): every Android package fills its manifest from one list':{ note: 'A native Android app can reach the network: its manifest never asked for it, so a remote group\'s assets, hot updates and the debug channel all failed on Android. A development build also allows plain http (a LAN CDN); a shipping build is held to https, and the export warns when its CDN is http.' },'feat(native): a native build\'s frame can be captured and replayed':- { note: 'The Frame Debugger captures and replays the frame of a connected native build (desktop and Android) as it does a web or mini-game one.' },+ { note: 'A connected native build\'s frame can be captured and replayed.' },};