[kpal81xd]

What's Changed

• The MCP settings:modify, project:settings:modify and scene:settings:modify methods now save values written under a parent that doesn't exist yet. Before, { "layers.1000": { name: "Water" } } or layers.1000.name became leaf writes such as layers.1000.name. The realtime server rejects those (Referenced element not an object), so the method returned success but the layer only existed until reload.
• Edits whose parent is missing are merged into a single write of the first missing ancestor (nestEdits). Edits whose parent exists are applied as before.
• Added tests that run the real ObserverSync against an in-memory ShareDB: leaf writes lose the layer, nested writes keep it.

The MCP server already sends whole objects for modify_project_settings (playcanvas/editor-mcp-server#124). This fixes the same problem for any client and for explicit leaf paths sent through modify_settings.

Smoke test

1. Open a test project and connect an MCP client.
2. Call modify_settings with scope project and edits [{ "path": "layers.1001.name", "value": "Foam" }, { "path": "layers.1001.opaqueSortMode", "value": 2 }]. Expected: success, and no Referenced element not an object error in the browser console.
3. Reload the Editor and open Settings > Layers. Expected: Foam is listed and can be deleted.

Checks

• I confirm I have read the contributing guidelines

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
editor	Ready	Preview	Oct 29, 2026 6:12pm UTC