@dcl-regenesislabs/web-editor 0.3.22-41448555429.commit-da528c6 → 0.3.22

package/prefabs/pickup-item/data.json

@@ -13,8 +13,12 @@
     "multiplayer"
   ],
   "requiresSdk": "auth-server",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "changelog": [
+    {
+      "version": "1.0.1",
+      "notes": "The assistant's guide says how the phone buttons the item declares combine with the ones a game's own scripts declare."
+    },
     {
       "version": "1.0.0",
       "notes": "Initial release: one holder at a time decided by the Multiplayer Server, held in the right hand and shown at once, a floating prompt with the device's own control, drop, optional throw, endless supply crates, and a script API to read, give and take what players carry."

package/prefabs/run-progress/ai.md

@@ -68,9 +68,12 @@ Confirmed finishes also publish a persisted top-25 board at
 first. Place Leaderboard, choose Source "Run best times" and the same Course Id.
 It works without another script; restart and player departure retain the board.
 
-For a moving deck, attach `scripts/moving-platform.ts` from this prefab's actual
-project folder to an authored platform with a MeshCollider. Its `axis` is x/y/z,
-`distance` is the travel amplitude in metres, and `periodSeconds` is one cycle.
+For a moving deck: attachScript takes only src/scripts/, so write a class there
+that extends `MovingPlatform` from this folder's `scripts/moving-platform.ts`
+(from src/scripts/: `../../custom/run_progress/scripts/moving-platform`, check the
+folder) with the same constructor, `super(src, entity, axis, distance,
+periodSeconds)`, and attach it to an authored platform with a MeshCollider.
+`axis` is x/y/z, `distance` the travel amplitude in metres, `periodSeconds` one cycle.
 Keep its whole path inside the parcels. Every player uses the same shared clock;
 test riding and jumping from it in the engine before treating it as reachable.
 
@@ -93,10 +96,3 @@ Start Spawn and Spawn 1–3. Place Health & Respawn with respawnAt Start Spawn a
 dieBelowHeight below the platforms. Place Run Progress with its default names.
 The HUD and full run loop then work without another scene script.
 
-## Creator workflow
-
-Add and name Trigger Areas, then place Run Progress. In its inspector choose Start Area, Finish Area and
-Start Marker, and use **+ Add** in the checkpoint, spawn-marker and collectible lists; row order is the
-matching order. These are scene entity pickers, so no CSV or generated script is needed; names have no commas.
-Place **UI Theme**, choose one accent color and Dark or Light, and Play. The HUD, result dialog, progress,
-buttons and Announcer use that theme. Keep one UI Theme per scene; its settings override the fallback accent.

package/prefabs/run-progress/data.json

@@ -14,8 +14,12 @@
     "restart"
   ],
   "requiresSdk": "auth-server",
-  "version": "1.4.0",
+  "version": "1.4.1",
   "changelog": [
+    {
+      "version": "1.4.1",
+      "notes": "The assistant's guide sets up a moving platform the way the assistant can attach it: a script of its own that extends the bundled one."
+    },
     {
       "version": "1.4.0",
       "notes": "The run HUD fits phones: Restart moves from the bottom-right corner (under the jump button) to under the clock, panels stack in the shared HUD layout instead of overlapping other HUDs, the controls hint matches the device, and the completion screen hides the touch controls while it is open."

package/prefabs/spawner/ai.md

@@ -13,7 +13,10 @@ copy is custom/spawner_2/.
 
 ## When to use
 
-Anything that shows up DURING play: an enemy, a pickup, a crate, a vehicle.
+Anything that shows up DURING play for the player who set it off: an enemy, a
+crate, a target, a vehicle. Copies exist only on that player's client, so a thing
+players share or carry (a coin they race for, an item to pick up) is never one:
+that is a Pickup Item or a placed entity.
 By default a copy is built at the Spawner's own spot, so place it where the
 thing belongs — the `where` param below covers the other landings.
 

package/prefabs/spawner/data.json

@@ -6,11 +6,14 @@
   "tags": [
     "spawner",
     "spawn",
-    "pickup",
     "enemy"
   ],
-  "version": "1.0.0",
+  "version": "1.0.1",
   "changelog": [
+    {
+      "version": "1.0.1",
+      "notes": "The assistant's guide says copies are for one player only, so something players share or carry is never a Spawner copy, and a search for \"pickup\" no longer lists it."
+    },
     {
       "version": "1.0.0",
       "notes": "Initial release: copies of a prefab appear while playing — on a click, when a player walks in, on a timer, or when another Script asks — made on that player's own client, with a per-spot cap, a lifetime and scatter."

package/prefabs/ui-theme/ai.md

@@ -13,15 +13,15 @@ Place one UI Theme from the library. Pick Accent Color and Dark or Light in its
 - `accentColor`: six-digit hex color, edited with a color picker.
 - `appearance`: Dark or Light.
 
-For custom UI, import `sceneUiTheme` from `~runtime/uiTheme`, `UiPanel`, `UiText`, `UiButton`, `ProgressPips`, `UiNotice` from `~runtime/uiComponents`, and place every panel with `addHudItem(slot, render)` from `~runtime/hudLayout` (its header documents the slots) instead of `ReactEcsRenderer.addUiRenderer`. Each panel declares width and height and is at most `HUD_COLUMN_WIDTH` wide; handlers go on actual buttons. Inspect a screenshot in the real preview, including completion.
+For custom UI, import `sceneUiTheme` from `~runtime/uiTheme`, `UiPanel`, `UiText`, `UiButton`, `ProgressPips`, `UiNotice` and `uiSizes` from `~runtime/uiComponents`, the compact HUD pieces from `~runtime/hudKit` and windows (shop, dialog, results) from `~runtime/uiWindow`, and place every panel with `addHudItem(slot, render)` from `~runtime/hudLayout` (its header documents the slots) instead of `ReactEcsRenderer.addUiRenderer`. Each panel declares width and height and is at most `HUD_COLUMN_WIDTH` wide; handlers go on actual buttons. Inspect a screenshot in the real preview, including completion.
 
 `ColorHex`, `EntityName`, `EntityNames`, `ZoneName` and `ZoneNames` from `~runtime/authoring` are string aliases that give constructor parameters color or entity pickers. Plural references are ordered comma-separated names; creators pick and reorder them in the inspector. Names must be unique and contain no commas. The assistant can provide arrays to the plural parameters.
 
 ## Do / Don't
 
-- Use one theme per scene, readable text (16 px or more) and small non-blocking HUDs.
-- Never put UI in the bottom corners or the screen's left edge: phones draw the joystick and the jump/E/F buttons there. Results, shops and rule cards use the `modal` slot, which hides the touch controls while open.
-- No hover-only states and no emoji in text; buttons at least 48 px tall.
+- Use one theme per scene and small non-blocking HUDs; take text and button sizes from `uiSizes('hud' | 'window')` (on phones text 20 or more and presses 80 or more).
+- Never put UI in the bottom corners or the screen's left edge: phones draw the joystick and the jump/E/F buttons there. Results, shops and rule cards are windows in the `modal` slot, which hides the touch controls while open.
+- No hover-only states and no emoji in text.
 - Do not write a separate palette for each prefab or use default pink SDK buttons.
 - Verify running and finished states in a real preview screenshot.
 

package/prefabs/ui-theme/data.json

@@ -11,8 +11,12 @@
     "hud",
     "design"
   ],
-  "version": "1.1.0",
+  "version": "1.2.0",
   "changelog": [
+    {
+      "version": "1.2.0",
+      "notes": "The guide points custom UI at the shared size set (uiSizes), the compact HUD pieces and the ready-made windows, so a HUD stays small and a shop or dialog is comfortable to tap on a phone."
+    },
     {
       "version": "1.1.0",
       "notes": "Custom HUDs are placed through the shared HUD layout, which keeps them clear of the phone touch controls and of each other."

package/scene/about

@@ -5,7 +5,7 @@
     "networkId": 0,
     "globalScenesUrn": [],
     "scenesUrn": [
-      "urn:decentraland:entity:bafkreihd3gtmg3p2azy5yfmzwihyk2pwunwuqkhrjybqzdp6vavsosna4y"
+      "urn:decentraland:entity:bafkreiggnrw7rgpjgljpbnvnppvxysckstguvp4s7zf65nfsm34vsenit4"
     ],
     "realmName": "editor-scene"
   },

package/scene/{bafkreihd3gtmg3p2azy5yfmzwihyk2pwunwuqkhrjybqzdp6vavsosna4y → bafkreiggnrw7rgpjgljpbnvnppvxysckstguvp4s7zf65nfsm34vsenit4}

@@ -1 +1 @@
-{"content":[{"file":"scene.json","hash":"bafkreiby2gmthtauf7cckttphmhpecsueyypi2hzlke4lcodg7fm4cm2sq"},{"file":"bin/index.js","hash":"bafybeifiaotfpb4kis6f46xdw6a2rm6c534wewr55bq7zwcidmthvd4y7m"}],"pointers":[],"timestamp":0,"type":"scene","metadata":{"ecs7":true,"runtimeVersion":"7","display":{"title":"Component Inspector","description":"Inspect and modify component state of the current scene"},"owner":"","contact":{"name":"","email":""},"main":"bin/index.js","tags":[],"scene":{"parcels":["0,0"],"base":"0,0"},"spawnPoints":[],"featureToggles":{"portableExperiences":"enabled"}},"version":"v3"}
+{"content":[{"file":"scene.json","hash":"bafkreiby2gmthtauf7cckttphmhpecsueyypi2hzlke4lcodg7fm4cm2sq"},{"file":"bin/index.js","hash":"bafybeig5grcn3rsku5eccniexikk7dwggcvdjbzdmx5lguwjiz742x7yfu"}],"pointers":[],"timestamp":0,"type":"scene","metadata":{"ecs7":true,"runtimeVersion":"7","display":{"title":"Component Inspector","description":"Inspect and modify component state of the current scene"},"owner":"","contact":{"name":"","email":""},"main":"bin/index.js","tags":[],"scene":{"parcels":["0,0"],"base":"0,0"},"spawnPoints":[],"featureToggles":{"portableExperiences":"enabled"}},"version":"v3"}