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
docs(changelog): the Engine Modules page
esengine50b561dfa744
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 9480aa0d5..6900eb32c 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -33,6 +33,14 @@ published separately; it ships inside the editor.install it. A project using a subsystem no subpath installs (video today) takes the wholeentry as before. Measured on the UI-game template: 1,305KB → 1,090KB, 57 files → 32.+- **Project Settings has an Engine Modules page: force a module into the build, or refuse one.** A build works out which+ subsystems a package needs from what the content uses, which is right for almost+ everything — but not for a module only a script reaches, and not when a build must not+ carry one at all. `physics.enabled` was that answer for exactly one module; every module+ has it now. Refusing one is enforced: an export whose content uses an excluded module+ fails and names the scene, asset or script that argued, rather than shipping a package+ quietly missing the subsystem its own scene needs.+- **The gameplay runtime is a subpath: `import { Health } from 'esengine/gameplay'`.** The third-person controller, thecamera, health, melee and the hunter were in every package: 10,567 bytes of a WeChatbuild with no character in it. What stays on `esengine` is the vocabulary — the animatordiff --git a/tools/releaseNotes.mjs b/tools/releaseNotes.mjsindex 7643e7bc8..3f7a71e25 100644--- a/tools/releaseNotes.mjs+++ b/tools/releaseNotes.mjs@@ -698,6 +698,12 @@ export const NOTED = {{ internal: "a manual page's import line, following the move it documents" },'refactor(play): the play realm asks for the whole import map by name':{ internal: "the editor's preview page names the same subpaths it always did" },+ 'feat(project): a project can force an engine module in, or refuse one':+ { note: "Project Settings has an Engine Modules page: force a module into the build, or refuse one." },+ 'feat(settings): an Engine Modules page, one row per module':+ { note: "Project Settings has an Engine Modules page: force a module into the build, or refuse one." },+ 'refactor(bundle): the published subpaths move to a module the renderer can read':+ { internal: "where one table lives; the list it holds is unchanged" },'fix(engine): two of the four subsystem switches did not build with them off':{ internal: "CMake options no shipped build changes; every release has all four ON" },'fix(editor-checks): a realm that never came up is unanswered, not a verdict':