Skip to content

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.

chore: release v0.70.0

esenginec053b602761c
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 985d2f3d7..2aecbd35f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -14,41 +14,107 @@ published separately; it ships inside the editor.
## [Unreleased]
-### Added
+## [0.70.0] - 2026-09-22
-- **The build's size bar stopped borrowing Play's green.** Within budget was drawn in the transport's running-green, which reads as a state the build is in rather than as a measurement — and a green bar invites "fine, keep going" where the honest message is that there is nothing to report yet. It is now the panel's own neutral, and goes amber then red, which is the whole vocabulary it needs. The two progress bars in that panel were also 6px and 8px side by side; they are one shape now.
+### Added
-- **A Play session that times out now says whether it ever started.** The realm announces itself when its page runs, before a line of the engine is read — previously its only signal was the host module's last statement, so a machine still parsing the SDK and a frame that never ran gave the same ninety seconds of silence, and both were reported as the editor being broken. The two now read differently, and only one of them is the machine's.
+- **The start screen is yours: a logo, a background and a minimum display time.** The exported page has shown real boot progress for a while, but always as the game's name on the engine's own dark ground. A project can now put its logo there — inlined into the page, because an image fetched over the network arrives in the same window the engine does, with nothing left to cover — pick the colour behind it, and hold the screen for a minimum time, so a boot that finishes in 120ms stops flashing a bar that appears and vanishes. The page also emits `esengine:bootprogress` and `esengine:firstframe`, which a portal's own loading screen can listen for before the game's bundle has run.
-- **When a 分包 will not come down, the package says which one and why.** The generated entry logged the vendor's error object, which reaches a device's console as `[object Object]` — the one place you get to look. It is stringified now, and the headless launcher can be told to refuse a named 分包 (`--fail-subpackage`) so the path a bad network takes is something a build can be run against rather than waited for.
+- **The build dialog states a platform's size caps before you package.** They were reported only after a package existed, in the size panel, so the ceiling a build had to fit under was visible only once it was too late to plan around — and the difference matters: a package that fits WeChat's 30MB is 10MB over Douyin's 20MB. Each target's caps now sit under its description, and hovering them gives the platform's own wording rather than our paraphrase. A platform a project defines itself states the caps it declared.
-- **A package whose engine ships in a 分包 now starts.** Its generated entry called the host's loading indicator on its first line without checking the host has one — and that call is optional in the API — so on a host that does not implement it the game died before reaching `loadSubpackage`. Every indicator call in a generated entry is guarded now; a progress message must never be what takes a boot down.
+- **A UI node can keep clear of WeChat's capsule menu, which the safe area does not cover.**
+ `SafeArea.avoidHostMenu` pushes the top inset past the host's own overlay. Measured on the
+ iPhone 12 the simulator offers, the capsule's bottom edge is 29px *inside* the safe area,
+ so a node anchored to the top of the safe area can still be under it. No engine offers
+ this: every game converts the rect to layout units by hand, which is the arithmetic the
+ safe area already does here.
-- **A group that failed to load says so instead of handing back an empty bundle.** `Assets.loadGroup` settled every asset and returned whatever survived, so a subpackage that downloaded but staged nothing — or a CDN answering 404 — read exactly like a group that was always empty. It now names the assets that failed, the way a scene preload already did.
+- **Douyin is selectable in the build dialog and has its own texture Import Settings tab.**
+ The export existed — the same runtime as WeChat, judged against Douyin's own 20MB cap —
+ but the editor's platform list was written by hand, so nothing offered the target that
+ had shipped. The list is the platform registry's now, in its order.
-- **A mini-game's side modules compress too, not just its engine.** Brotli was applied to the engine binary alone, so a package that transcodes KTX2 textures still carried Basis at its full 1.1MB — 27% of WeChat's 4MB main-package cap on its own. They compress on the same switch now, and the loader is told which suffix the build staged instead of spelling `.wasm` itself. Measured on the platformer template: its WeChat package was 108% of the cap and is now 51.5%, with the side modules accounting for 902KB of that.
+- **A mini-game says how far along its boot is, not just that it is loading.** The web
+ export got a start screen with a real progress bar; a mini-game could not have one,
+ because the display canvas is already the GL surface and nothing can be drawn over it.
+ It now reports through the host's own loading indicator instead — *Starting the
+ engine 54%* — driven by the same eight weighted stages the web overlay uses, from one
+ list, so the two cannot disagree about how far along the same boot is. A host without
+ that API boots exactly as before: an indicator is something a boot shows, never
+ something it can fail on.
-- **A mini-game says it is starting before it parses the game.** The host's loading indicator only appeared once `initMiniGameRuntime` ran, which is after the entry has required a megabyte of bundle — the longest silent stretch of a cold start. The generated entry now raises it on its first line.
+- **A project can be exported as a Douyin (抖音) mini-game.** Pick *Douyin* in Package
+ Project and the same content that makes a WeChat package makes a Douyin one, judged
+ against Douyin's own caps — 4MB for the main package and **20MB in total**, ten less
+ than WeChat allows, which is the number that catches a package out. Three things are
+ deliberately not claimed yet, because this release cannot cite them: the suffix list
+ its packer accepts, `.wasm.br` for the engine binary, and a wasm loader of the host's
+ own. Each is something only a real device settles, and a package that claimed one
+ early would build clean and fail at upload or at boot. Douyin needs no separate engine
+ build — the web artifact is what a `tt` host runs.
-- **The start screen is yours: a logo, a background and a minimum display time.** The exported page has shown real boot progress for a while, but always as the game's name on the engine's own dark ground. A project can now put its logo there — inlined into the page, because an image fetched over the network arrives in the same window the engine does, with nothing left to cover — pick the colour behind it, and hold the screen for a minimum time, so a boot that finishes in 120ms stops flashing a bar that appears and vanishes. The page also emits `esengine:bootprogress` and `esengine:firstframe`, which a portal's own loading screen can listen for before the game's bundle has run.
+- **A sprite can be drawn whole even when its texture carries a 9-slice border.** The
+ texture decided, not the entity using it: import a panel image with slice borders and
+ every Sprite showing it was 9-sliced, with nothing on the entity able to say otherwise.
+ Sprites now have a **Draw Mode** — *Auto* is the old inference (tile size decides
+ tiling, the texture's border decides 9-slice) and stays the default, so nothing you
+ have drawn changes; *Simple*, *Tiled* and *9-Slice* say it outright. An override cannot
+ invent what it needs, so *Tiled* with no tile size and *9-Slice* on a texture with no
+ border both draw the plain quad, which is what the sprite would have drawn anyway.
-- **The build dialog states a platform's size caps before you package.** They were reported only after a package existed, in the size panel, so the ceiling a build had to fit under was visible only once it was too late to plan around — and the difference matters: a package that fits WeChat's 30MB is 10MB over Douyin's 20MB. Each target's caps now sit under its description, and hovering them gives the platform's own wording rather than our paraphrase. A platform a project defines itself states the caps it declared.
+- **A WeChat mini-game now carries only the optional subsystems its project uses.**
+ The engine binary was never the only thing a package paid for whether it needed it or
+ not: the JavaScript bundle carried Spine, DragonBones, 2D physics, 3D physics and video
+ in every build, because the runtime that starts your game named all of them. It no
+ longer does — the export reads the same scan that already decides which `.wasm` side
+ modules ship, and builds on an SDK entry that installs only those. *hello-world* drops
+ 91KB of a 1.4MB bundle; a project that does use Spine keeps Spine and drops what it
+ does not. There is more to win here and it is measured: `SpinePlugin` registers a named
+ resource when its module loads, which a bundler cannot remove, and that alone is 47KB
+ no package can currently shed.
-### Fixed
+- **A packaged game now says it is loading.** Between the page opening and the first frame
+ an export showed its background colour and nothing else — and on a cold start that gap is
+ the whole download of a 1.7MB engine binary, which reads to a player as a page that did
+ not work. Web and desktop packages now open on a start screen carrying the project's name
+ and a bar moving through the eight stages the boot actually has, weighted by what each one
+ costs rather than counted evenly: reading the build, scripts, the asset list, the scene,
+ the engine, the renderer, assets, ready. It fades as the first frame arrives. A start
+ screen still standing after a package settles now fails that package's check, because
+ everything else about it passes — the canvas painted underneath, nothing errored — and
+ what it leaves on screen looks exactly like a game that is still loading.
-- **The Engine Modules page no longer calls a module unused that the build then carries.** It read only the components a scene names, while the build also reads the extensions of the assets that ship and the imports your scripts write — so a behaviour tree an agent is handed at runtime, which leaves no component behind, showed as "not used by this project" in a package that had it. The page now reads the same asset table the build installs from, and says what it can see rather than what will ship.
+- **The engine can ship outside a WeChat mini-game's main package entirely.** Compressing
+ it left 0.35MB of the 4MB limit spent before any of your content; *Engine in a subpackage*
+ moves the binary into a 分包 the host loads at startup, and the main package keeps only
+ the 162KB of glue that starts it — 4% of the limit, down from 47.5% with neither setting
+ on. The two stack: compression shrinks what the 分包 downloads. Off by default, because
+ startup then waits on that load, which is a trade worth making when the main package is
+ what you are fighting and not otherwise.
-- **A Douyin package could not start.** It shipped the browser engine artifact, which is an ES module, and a mini-game host loads its JavaScript with `require` — so `game.js` threw `SyntaxError: Unexpected token 'export'` on its first line and the package never reached a frame. Every mini-game host takes the same engine build, and now every mini-game target asks for it: the two built-in vendors, and a platform a project defines itself, which had the same browser default. The export also refuses an ES module engine by reading the file rather than trusting its name, since the name was the thing that was wrong.
+- **A WeChat mini-game can ship its engine compressed, freeing a third of the main
+ package.** The engine binary is the largest single file such a package carries — 1.74MB
+ against WeChat's 4MB main-package limit, 43.6% of it spent before any of your content.
+ WeChat's loader accepts a brotli-compressed `.wasm.br` path, so turning on *Compress
+ engine binary* on the WeChat page of Package Project ships 0.35MB instead: 8.7% of the
+ limit, with 1.40MB handed back to the game. The package carries one file, not both, and
+ the host decompresses it on load. Off by default, since it costs about two seconds of
+ build time and only pays where a main-package limit is being fought. Needs WeChat base
+ library 2.14.0.
### Changed
+- **A mini-game says it is starting before it parses the game.** The host's loading indicator only appeared once `initMiniGameRuntime` ran, which is after the entry has required a megabyte of bundle — the longest silent stretch of a cold start. The generated entry now raises it on its first line.
+
+- **A mini-game's side modules compress too, not just its engine.** Brotli was applied to the engine binary alone, so a package that transcodes KTX2 textures still carried Basis at its full 1.1MB — 27% of WeChat's 4MB main-package cap on its own. They compress on the same switch now, and the loader is told which suffix the build staged instead of spelling `.wasm` itself. Measured on the platformer template: its WeChat package was 108% of the cap and is now 51.5%, with the side modules accounting for 902KB of that.
+
+- **The build's size bar stopped borrowing Play's green.** Within budget was drawn in the transport's running-green, which reads as a state the build is in rather than as a measurement — and a green bar invites "fine, keep going" where the honest message is that there is nothing to report yet. It is now the panel's own neutral, and goes amber then red, which is the whole vocabulary it needs. The two progress bars in that panel were also 6px and 8px side by side; they are one shape now.
+
- **A dialog's title now looks like one.** The editor's type scale stopped at 14px and used
it five times in the whole application, while 10px carried most of the text — so a dialog
header at 13px read as bold body text rather than as a title. Window titles now have a
step of their own, which is what every editor this size gives them.
-### Changed
-
- **A web package ships only the subsystems its project uses.** Every web package staged all eleven engine
subpaths and loaded the entry that installs every optional subsystem, so a UI-only game
carried Spine, both physics runtimes, tilemaps, script graphs, gameplay AI and
@@ -128,16 +194,19 @@ published separately; it ships inside the editor.
unchanged and all were `@beta`; the whole entry still installs everything, so anything
that imports `esengine` alone behaves as before.
-### Added
+### Fixed
-- **A UI node can keep clear of WeChat's capsule menu, which the safe area does not cover.**
- `SafeArea.avoidHostMenu` pushes the top inset past the host's own overlay. Measured on the
- iPhone 12 the simulator offers, the capsule's bottom edge is 29px *inside* the safe area,
- so a node anchored to the top of the safe area can still be under it. No engine offers
- this: every game converts the rect to layout units by hand, which is the arithmetic the
- safe area already does here.
+- **A group that failed to load says so instead of handing back an empty bundle.** `Assets.loadGroup` settled every asset and returned whatever survived, so a subpackage that downloaded but staged nothing — or a CDN answering 404 — read exactly like a group that was always empty. It now names the assets that failed, the way a scene preload already did.
-### Fixed
+- **A package whose engine ships in a 分包 now starts.** Its generated entry called the host's loading indicator on its first line without checking the host has one — and that call is optional in the API — so on a host that does not implement it the game died before reaching `loadSubpackage`. Every indicator call in a generated entry is guarded now; a progress message must never be what takes a boot down.
+
+- **When a 分包 will not come down, the package says which one and why.** The generated entry logged the vendor's error object, which reaches a device's console as `[object Object]` — the one place you get to look. It is stringified now, and the headless launcher can be told to refuse a named 分包 (`--fail-subpackage`) so the path a bad network takes is something a build can be run against rather than waited for.
+
+- **A Play session that times out now says whether it ever started.** The realm announces itself when its page runs, before a line of the engine is read — previously its only signal was the host module's last statement, so a machine still parsing the SDK and a frame that never ran gave the same ninety seconds of silence, and both were reported as the editor being broken. The two now read differently, and only one of them is the machine's.
+
+- **The Engine Modules page no longer calls a module unused that the build then carries.** It read only the components a scene names, while the build also reads the extensions of the assets that ship and the imports your scripts write — so a behaviour tree an agent is handed at runtime, which leaves no component behind, showed as "not used by this project" in a package that had it. The page now reads the same asset table the build installs from, and says what it can see rather than what will ship.
+
+- **A Douyin package could not start.** It shipped the browser engine artifact, which is an ES module, and a mini-game host loads its JavaScript with `require` — so `game.js` threw `SyntaxError: Unexpected token 'export'` on its first line and the package never reached a frame. Every mini-game host takes the same engine build, and now every mini-game target asks for it: the two built-in vendors, and a platform a project defines itself, which had the same browser default. The export also refuses an ES module engine by reading the file rather than trusting its name, since the name was the thing that was wrong.
- **A mini-game that fetches its engine from a 分包 shows the download's progress.** The host fetches it before the game
bundle is parsed, so the runtime's own loading indicator could not say anything yet and
@@ -332,81 +401,6 @@ published separately; it ships inside the editor.
minutes with zero textures loaded, zero render targets and not one warning in the whole
diagnostic bundle. The failures are now warned once, with what failed and why.
-### Added
-
-- **Douyin is selectable in the build dialog and has its own texture Import Settings tab.**
- The export existed — the same runtime as WeChat, judged against Douyin's own 20MB cap —
- but the editor's platform list was written by hand, so nothing offered the target that
- had shipped. The list is the platform registry's now, in its order.
-
-- **A mini-game says how far along its boot is, not just that it is loading.** The web
- export got a start screen with a real progress bar; a mini-game could not have one,
- because the display canvas is already the GL surface and nothing can be drawn over it.
- It now reports through the host's own loading indicator instead — *Starting the
- engine 54%* — driven by the same eight weighted stages the web overlay uses, from one
- list, so the two cannot disagree about how far along the same boot is. A host without
- that API boots exactly as before: an indicator is something a boot shows, never
- something it can fail on.
-
-- **A project can be exported as a Douyin (抖音) mini-game.** Pick *Douyin* in Package
- Project and the same content that makes a WeChat package makes a Douyin one, judged
- against Douyin's own caps — 4MB for the main package and **20MB in total**, ten less
- than WeChat allows, which is the number that catches a package out. Three things are
- deliberately not claimed yet, because this release cannot cite them: the suffix list
- its packer accepts, `.wasm.br` for the engine binary, and a wasm loader of the host's
- own. Each is something only a real device settles, and a package that claimed one
- early would build clean and fail at upload or at boot. Douyin needs no separate engine
- build — the web artifact is what a `tt` host runs.
-
-- **A sprite can be drawn whole even when its texture carries a 9-slice border.** The
- texture decided, not the entity using it: import a panel image with slice borders and
- every Sprite showing it was 9-sliced, with nothing on the entity able to say otherwise.
- Sprites now have a **Draw Mode** — *Auto* is the old inference (tile size decides
- tiling, the texture's border decides 9-slice) and stays the default, so nothing you
- have drawn changes; *Simple*, *Tiled* and *9-Slice* say it outright. An override cannot
- invent what it needs, so *Tiled* with no tile size and *9-Slice* on a texture with no
- border both draw the plain quad, which is what the sprite would have drawn anyway.
-
-- **A WeChat mini-game now carries only the optional subsystems its project uses.**
- The engine binary was never the only thing a package paid for whether it needed it or
- not: the JavaScript bundle carried Spine, DragonBones, 2D physics, 3D physics and video
- in every build, because the runtime that starts your game named all of them. It no
- longer does — the export reads the same scan that already decides which `.wasm` side
- modules ship, and builds on an SDK entry that installs only those. *hello-world* drops
- 91KB of a 1.4MB bundle; a project that does use Spine keeps Spine and drops what it
- does not. There is more to win here and it is measured: `SpinePlugin` registers a named
- resource when its module loads, which a bundler cannot remove, and that alone is 47KB
- no package can currently shed.
-
-- **A packaged game now says it is loading.** Between the page opening and the first frame
- an export showed its background colour and nothing else — and on a cold start that gap is
- the whole download of a 1.7MB engine binary, which reads to a player as a page that did
- not work. Web and desktop packages now open on a start screen carrying the project's name
- and a bar moving through the eight stages the boot actually has, weighted by what each one
- costs rather than counted evenly: reading the build, scripts, the asset list, the scene,
- the engine, the renderer, assets, ready. It fades as the first frame arrives. A start
- screen still standing after a package settles now fails that package's check, because
- everything else about it passes — the canvas painted underneath, nothing errored — and
- what it leaves on screen looks exactly like a game that is still loading.
-
-- **The engine can ship outside a WeChat mini-game's main package entirely.** Compressing
- it left 0.35MB of the 4MB limit spent before any of your content; *Engine in a subpackage*
- moves the binary into a 分包 the host loads at startup, and the main package keeps only
- the 162KB of glue that starts it — 4% of the limit, down from 47.5% with neither setting
- on. The two stack: compression shrinks what the 分包 downloads. Off by default, because
- startup then waits on that load, which is a trade worth making when the main package is
- what you are fighting and not otherwise.
-
-- **A WeChat mini-game can ship its engine compressed, freeing a third of the main
- package.** The engine binary is the largest single file such a package carries — 1.74MB
- against WeChat's 4MB main-package limit, 43.6% of it spent before any of your content.
- WeChat's loader accepts a brotli-compressed `.wasm.br` path, so turning on *Compress
- engine binary* on the WeChat page of Package Project ships 0.35MB instead: 8.7% of the
- limit, with 1.40MB handed back to the game. The package carries one file, not both, and
- the host decompresses it on load. Off by default, since it costs about two seconds of
- build time and only pays where a main-package limit is being fought. Needs WeChat base
- library 2.14.0.
-
## [0.69.0] - 2026-09-18
### Added
@@ -13591,7 +13585,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 first
commit on 2026-01-25.
-[Unreleased]: https://github.com/esengine/estella/compare/v0.69.0...HEAD
+[Unreleased]: https://github.com/esengine/estella/compare/v0.70.0...HEAD
+[0.70.0]: https://github.com/esengine/estella/compare/v0.69.0...v0.70.0
[0.69.0]: https://github.com/esengine/estella/compare/v0.68.0...v0.69.0
[0.68.0]: https://github.com/esengine/estella/compare/v0.67.0...v0.68.0
[0.67.0]: https://github.com/esengine/estella/compare/v0.66.0...v0.67.0
diff --git a/SECURITY.md b/SECURITY.md
index 2a65cda75..990e9ef9d 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.69.x | Yes |
-| < 0.69 | No |
+| 0.70.x | Yes |
+| < 0.70 | No |
`tools/check-release-metadata.mjs` fails the build if this table stops matching
the version being shipped, so it cannot quietly fall behind again.
diff --git a/desktop b/desktop
index 1e7c516d6..13fd51f30 160000
--- a/desktop
+++ b/desktop
@@ -1 +1 @@
-Subproject commit 1e7c516d60eb67283368e6726b265b71ec154153
+Subproject commit 13fd51f30226565149f41ed27d95a1d6e89a81d7
diff --git a/package.json b/package.json
index e4a12d8f6..6cb059751 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
{
"name": "estella",
- "version": "0.69.0",
+ "version": "0.70.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.mjs
index bf8c87134..12d4cc791 100644
--- a/tools/goldenProjects.mjs
+++ b/tools/goldenProjects.mjs
@@ -90,6 +90,37 @@ 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.70.0 —
+ 'A project can be exported as a Douyin (抖音) mini-game.': { certifies: 'minigame-vendor' },
+ 'A sprite can be drawn whole even when its texture carries a 9-slice border.':
+ { certifies: 'sprite-draw-mode' },
+ 'The start screen is yours: a logo, a background and a minimum display time.':
+ { notCertifiable: 'the page AROUND the game — no golden project configures one, and'
+ + ' launch-export already refuses any web package whose start screen never faded' },
+ 'A packaged game now says it is loading.':
+ { notCertifiable: 'as above: the page around the game, held by the launcher rather than'
+ + ' by a frame the game drew' },
+ 'The build dialog states a platform\'s size caps before you package.':
+ { notCertifiable: 'a number the dialog reads out of sizeBudget.ts before a package exists;'
+ + ' nothing of it ships' },
+ 'Douyin is selectable in the build dialog and has its own texture Import Settings tab.':
+ { notCertifiable: 'editor rows; what they produce is the Douyin package, which'
+ + ' input-actions packages and boots at the release tier' },
+ 'A mini-game says how far along its boot is, not just that it is loading.':
+ { notCertifiable: 'the HOST\'s indicator, which is the vendor\'s own overlay and never a'
+ + ' frame of the game; the stand-in host records the last stage for the launcher' },
+ 'A UI node can keep clear of WeChat\'s capsule menu, which the safe area does not cover.':
+ { notCertifiable: 'it moves a node only on a host that draws a capsule, and the stand-in'
+ + ' host the mini-game pairs run in draws none' },
+ 'A WeChat mini-game now carries only the optional subsystems its project uses.':
+ { notCertifiable: 'a byte count no frame shows — a package that dropped a subsystem its'
+ + ' content uses fails the wechat pairs\' pixel parity, which is where it is caught' },
+ 'The engine can ship outside a WeChat mini-game\'s main package entirely.':
+ { notCertifiable: 'where a file sits in the package, not what it draws; no tier builds a'
+ + ' project with the engine in a 分包 — it boots in the stand-in host by hand' },
+ 'A WeChat mini-game can ship its engine compressed, freeing a third of the main package.':
+ { notCertifiable: 'as above — bytes, not pixels; the compressed package boots in the'
+ + ' stand-in host and export-wechat holds the naming both halves agree on' },
// — 0.69.0 —
'`getResourceStats()` reports the memory kept to survive a lost GPU.':
{ notCertifiable: 'a byte count no frame shows; the resource census reads it as'
@@ -399,7 +430,7 @@ export const CAPABILITIES = [
'tilemap', 'tile-collision',
'touch', 'safe-area', 'pause-resume',
'texture-atlas',
- 'single-file', 'startup-size',
+ 'single-file', 'startup-size', 'minigame-vendor', 'sprite-draw-mode',
'hot-update', 'rollback', 'subpackage',
'networking',
'persistence', 'save-versioning',
@@ -514,6 +545,10 @@ export const EVIDENCE = {
'texture-atlas': null,
'single-file': null,
'startup-size': null,
+ // A package's, not a source's: the claim is that a second vendor's package
+ // boots, which only the launched package can show.
+ 'minigame-vendor': null,
+ 'sprite-draw-mode': /\bdrawMode\b/,
'hot-update': /\b(checkForUpdate|applyUpdate)\b/,
rollback: /\b(applyUpdate|rollback)\b/,
networking: /\b(Net|Replicated|NetId)\b/,
@@ -583,7 +618,7 @@ export const GOLDEN = [
// Its hull bar is a sprite cut by another sprite, drawn at an order it states
// rather than at the one its position would give it — so the draw order and the
// mask are both something a packaged game here actually does.
- certifies: ['ecs', 'texture-atlas', 'sprite-sorting', 'sprite-mask', 'velocity-motion'],
+ certifies: ['ecs', 'texture-atlas', 'sprite-sorting', 'sprite-mask', 'velocity-motion', 'sprite-draw-mode'],
targets: ['web', 'desktop', 'android'],
tier: 'pr',
interact: { keys: ['ArrowLeft'], frames: 40 },
@@ -845,7 +880,7 @@ export const GOLDEN = [
},
{
id: 'input-actions',
- certifies: ['input'],
+ certifies: ['input', 'minigame-vendor'],
// Two vendors from one project: the export is a profile over one family, and
// only a second vendor's real boot shows what the family got wrong. They take
// the same engine build, so the second costs no extra wasm build.