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: the changelog had none of today, and the download page had the slow link
yhhdcd95bbe2ac9
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 86be39941..5a5473856 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -16,6 +16,37 @@ published separately; it ships inside the editor.### Added+- **Spine, from a 2015 editor to the current one.** A project authored in Spine+ **2.1** or **4.3** used to open as nothing: the runtime reads the version out of+ the skeleton, and neither matched anything the engine vendored. Both now do, so+ the supported set is **2.1 / 3.8 / 4.1 / 4.2 / 4.3** — each a WebAssembly backend+ loaded only by a project that uses it. 4.3 could not simply be added: that+ release deleted the hand-written C runtime and regenerated it as a wrapper over+ the C++ one, so the module binds spine-cpp directly and renders through spine's+ own `SkeletonRenderer`. 2.1 is the opposite end — colour as loose floats,+ weighted meshes as their own attachment type, no clipping and no transform or+ path constraints — and its runtime shipped **no binary reader**, so a `.skel`+ from that era is refused by naming the export setting to change rather than+ failing as a corrupt file. Export 2.1 skeletons as JSON.+- **Android: export the project, not only the package.** *Package as* in the+ Android section now offers an **Android Studio project** beside the installable+ APK — the route for a game that has to add an SDK, a permission, a service or an+ Activity of its own, which an APK is a dead end for. It is an ordinary Gradle+ project: your content under `app/src/main/assets`, the engine's prebuilt+ libraries under `jniLibs`, the host's Java shim as source, and identity in+ `app/build.gradle.kts` where AGP reads it. Both outputs come from the same+ runtime template, so the choice costs nothing. **Re-exporting rewrites the game+ and leaves the build scripts alone** — a project that has grown an SDK survives+ its game being rebuilt.+- **Downloads come from a mirror, and prove themselves before being trusted.** The+ editor asks a Cloudflare copy of each release before GitHub — measured at **3.0+ MB/s against 2.0** from Shanghai — for both the runtime templates and the update+ check. Preferring a mirror is safe because trusting one never was: every archive+ is checked against the size and SHA-256 the release's index states, and a copy+ that is missing, stale, truncated or substituted fails that check and hands the+ download to the next source, ending at GitHub. `ESTELLA_RELEASE_MIRROR` points+ the editor at a company share, an offline copy, or nothing at all.+- **One package installs on a phone AND in an emulator.** A runtime template isnow one artifact per PLATFORM rather than one per architecture — iOS alreadyworked that way, with both slices inside one xcframework — so the Android@@ -103,6 +134,12 @@ published separately; it ships inside the editor.### Fixed+- **Spine: a mesh weighted to more than three bones corrupted the heap.** The+ vendored spine-c read a weighted mesh's vertices into a buffer sized for three+ bones per vertex, and a fourth wrote past the end — so a binary skeleton whose+ meshes bind more bones than that could take out whatever was next to it in+ memory. Upstream's fix grows both buffers; the 4.2 runtime is updated to it.+- **The iOS host did not compile.** A `__weak` reference had landed in`platform/ios.mm`, which builds under manual reference counting — so every iOSbuild had been failing since. Now `__unsafe_unretained`, which is what adiff --git a/docs/astro/src/content/docs/getting-started/installation.mdx b/docs/astro/src/content/docs/getting-started/installation.mdxindex ac1c99432..6267af5d7 100644--- a/docs/astro/src/content/docs/getting-started/installation.mdx+++ b/docs/astro/src/content/docs/getting-started/installation.mdx@@ -9,8 +9,11 @@ import { Tabs, TabItem, Steps, Aside } from '@astrojs/starlight/components';<TabItem label="Use the editor"><Steps>- 1. Download the latest editor from the- [releases page](https://github.com/esengine/estella/releases).+ 1. Download the latest editor — from the+ [mirror](https://dl.estella.games/latest.json) if GitHub is slow where you+ are, or from the+ [releases page](https://github.com/esengine/estella/releases), which is+ where every release is published.2. Install and open it, then click **New project**.@@ -21,6 +24,12 @@ import { Tabs, TabItem, Steps, Aside } from '@astrojs/starlight/components';</Steps>+ <Aside type="tip">+ **Help → Check for Updates…** reads the same mirror (`dl.estella.games`) and+ hands back a download from it, falling back to GitHub when the mirror has no+ answer or a staler one — the origin stays the authority on what exists.+ </Aside>+<Aside type="note">Installers are currently unsigned, so on first launch Windows SmartScreenor macOS Gatekeeper may warn about an unknown developer — choose **Rundiff --git a/docs/astro/src/content/docs/guides/mobile.mdx b/docs/astro/src/content/docs/guides/mobile.mdxindex c7b2d4df5..7f8cd55de 100644--- a/docs/astro/src/content/docs/guides/mobile.mdx+++ b/docs/astro/src/content/docs/guides/mobile.mdx@@ -74,7 +74,8 @@ are not the same severity:editor, on whatever OS it is running on.:::tip[Where the download comes from]- Releases are mirrored, and the editor asks the mirror before the origin — a+ Releases are mirrored to `dl.estella.games`, and the editor asks it before the+ origin — atemplate is hundreds of megabytes, and GitHub's speed is not the sameeverywhere. The mirror is a shortcut and never an authority: every archive ischecked against the size and SHA-256 the release's index states, so a copy thatdiff --git a/docs/astro/src/content/docs/zh-cn/getting-started/installation.mdx b/docs/astro/src/content/docs/zh-cn/getting-started/installation.mdxindex 8392f9654..ab30e68cb 100644--- a/docs/astro/src/content/docs/zh-cn/getting-started/installation.mdx+++ b/docs/astro/src/content/docs/zh-cn/getting-started/installation.mdx@@ -9,7 +9,8 @@ import { Tabs, TabItem, Steps, Aside } from '@astrojs/starlight/components';<TabItem label="使用编辑器"><Steps>- 1. 从[发布页](https://github.com/esengine/estella/releases)下载最新版编辑器。+ 1. 下载最新版编辑器:GitHub 慢的话走[镜像](https://dl.estella.games/latest.json),+ 或者用[发布页](https://github.com/esengine/estella/releases)——所有版本都发布在那里。2. 安装并打开,点击 **New project**(新建项目)。@@ -19,6 +20,11 @@ import { Tabs, TabItem, Steps, Aside } from '@astrojs/starlight/components';</Steps>+ <Aside type="tip">+ **帮助 → 检查更新…** 读的是同一个镜像(`dl.estella.games`),给出的下载链接也+ 指向它;镜像没答案或答案更旧时回落 GitHub —— 「有没有新版本」始终以源站为准。+ </Aside>+<Aside type="note">安装包目前尚未签名,因此首次启动时 Windows SmartScreen 或 macOS Gatekeeper可能提示「未知开发者」——请选择**仍要运行**,或在**系统设置 → 隐私与安全性**中diff --git a/docs/astro/src/content/docs/zh-cn/guides/mobile.mdx b/docs/astro/src/content/docs/zh-cn/guides/mobile.mdxindex 123510d85..70faac674 100644--- a/docs/astro/src/content/docs/zh-cn/guides/mobile.mdx+++ b/docs/astro/src/content/docs/zh-cn/guides/mobile.mdx@@ -61,7 +61,7 @@ Android 两者都给,是因为它两者都做得到:编辑器既能直接装配Android 此外别无所需:APK 的编译、对齐与签名都由编辑器在它所运行的任何操作系统上完成。:::tip[下载走的是哪儿]- 发布会同步一份到镜像,编辑器**先问镜像再问源站**——一个模板几百 MB,而 GitHub 的+ 发布会同步一份到镜像 `dl.estella.games`,编辑器**先问镜像再问源站**——一个模板几百 MB,而 GitHub 的速度并非各地一致。镜像只是捷径,从来不是权威:每个归档都会按发布索引里写的大小与SHA-256 校验,缺失、过期或被替换的副本过不了这一关,下载会自动回落到 GitHub。要指到别处(公司共享、自建 CDN,或者干脆不用镜像),设 `ESTELLA_RELEASE_MIRROR`(逗号