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 component-name rule is a breaking change a project can hit
esengine43e4140abb21
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 42ba4b085..dce6dd435 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -317,6 +317,24 @@ published separately; it ships inside the editor.relying on a non-replicated component reaching clients must declare anarchetype for it, or declare the fields replicated and mean it.+- **BREAKING: a component name is claimed once.** `defineComponent` returned the+ existing definition when a name was already taken, which is right for a tag and+ silent data loss for a component with fields: the loser's fields are dropped+ wherever a scene carries them, and nothing says so.++ The engine keeps taking new names — this release alone added `MeleeAttack`,+ `Health`, `Hunter`, `Perception` and more to the SDK — so a project that+ declared one of them first stopped receiving its own fields. In the flagship+ example that read as a boss dying from 916 units away: `reach` and `cooldown`+ were not in the winning schema, so `overlapCircle` got `undefined` for a radius+ and no swing was ever on cooldown.++ Declaring the same name twice with the SAME fields is still a reuse — one+ module reached through two import paths, or a hot reload re-running a+ declaration. Different fields now throws, naming both field lists. If you hit+ it, rename your component: the two shipped examples that collided became+ `Vitality`/`Swing` and `Hull`.+- **Interest is prepare-once, query-many.** An `InterestPolicy` is handed thepopulation per connection, so whatever it reads it reads C times — and theshipped radius policy reads a position through the builtin Transform. Measured,