Wonderland Editor Views

Find editor views in the top menu bar “Views”.

Essential Views 

You will need the following views very frequently:

• Scene View
  • Hotkeys
• Asset Browser
• Console
• Scene Outline
  • Hotkeys
• Properties
• Project Settings
• Resources
• Project Data
• Profile
• Preferences
• Plugins

Additional Views 

Less frequently used but handy tools:

• Benchmark
• Localization
• Resource Tree
• Animation Editor

Global Hotkeys 

Hotkeys that work anywhere in the editor.

Scene View 

Shows a 3D view of the current project’s scene.

Drag and drop a material from Resources onto an object to change the first mesh component’s material. Drag and drop a texture from Resources onto an object to set the first texture slot of the first material. You can also drag resources directly into component property slots.

Hotkeys 

While holding down Shift + right mouse button, viewport navigation is enabled:

While holding down middle mouse button, you are panning the camera:

Asset Browser 

Shows files in the project directory.

Right-click empty space to create a new JavaScript component.

To combine PBR textures, select them and use Right Click > Tools > Combine PBR textures.

Right-click in a “shaders” folder to create custom shaders and in a “plugins” folder for plugins.

Hotkeys 

Console 

Logs messages of current events in the editor.

Disable “Info”, “Warnings” or “Errors” to see other messages more clearly.

Scene Outline 

Shows the hierarchy of the objects in the scene.

Drag and drop objects to reparent.

Drag and drop objects from here onto object resource slots in component properties.

Hotkeys 

Properties 

Shows properties of selected objects.

For any component, you can click the three dots and its documentation will open in the browser. You can also open the JavaScript source files of the components from here.

Project Settings 

Settings for the entire project.

Ranges from rendering settings, paths from which JavaScript files will be taken, VR and AR setup options, Physics and Runtime settings.

Resources 

Shows tables for all the resources currently managed in the project.

Contains additional optimization options for some resources, allows renaming by double-click on the resource name, some can be deleted and duplicated by right-clicking on the resource.

You can drag and drop resources into component properties from here.

You can drag and drop materials and textures onto objects in the Scene View from here.

Project Data 

A debug view that shows the internal JSON files for the project.

Profile 

When a runtime is active in a browser and is able to connect via WebSocket to localhost:8080, the runtime will send profiling data every 30 frames. This will also work for Android clients connected via adb with port forwarding enabled (e.g. for Oculus Quest or smartphones).

The data is presented by this view in a graph.

You can switch the connected runtime via the dropdown at the top.

Preferences 

Global editor preferences stored per computer.

• Configure shortcuts and learn available hotkeys
• Toggle “Force full page reloads” to disable fast live-reload
• Manage server options (port, SSL certificates)
• Tweak startup and notifications

Plugins 

Manage editor and project plugins.

Open via Views > Plugins. Use the “Enable plugins for this project” checkbox to allow plugin execution for the current project. The view has two tabs:

• Editor Scope: Plugins bundled with or installed for the editor itself. These typically add views or tooling that is available regardless of the current project.
• Project Scope: Plugins that are part of your project (installed via devDependencies or placed in the plugins/ folder). These can read and modify your project files and participate in packaging.

Toggle individual plugins via the checkbox on the right. Some plugins may require a project reload after enabling.

Benchmark 

Capture performance on a benchmark scene, including on external devices.

• Open via Views > Benchmark.
• Choose a benchmark file and select the target device (local or an attached external device), then start the benchmark. Use “Refresh devices” if your device list changed.
• Results are summarized in the view after completion; use them to compare performance across devices or after changes to your project.

Tip: There’s also a CLI option for automated runs; see the Editor CLI page for --benchmark in the CLI docs.

Localization 

Translate strings in your project into multiple languages.

• Open via Views > Localization.
• “Strings” tab lists translatable terms found in your project; use the checkboxes to include them.
• “Languages” tab lets you add languages and edit translations.
• On project save, translations export to JSON at <project-root>/languages/<Scene>/<lang-code>.json, which you can process with industry‑standard translation tools. Use “Reimport all” or “Reimport non‑default” to bring edited JSON back into the project.

Resource Tree 

Visualize which resources reference others, and quickly spot unused or unexpectedly linked assets.

• Open via Views > Resource Tree.
• “Only selection” limits the view to the current selection; “Reverse” switches the direction of the reference graph.
• Expand nodes to inspect relationships between objects, meshes, materials, pipelines, shaders and more. Use this to track down where a resource is used before removing or changing it.

Animation Editor 

Edit animation tracks and add “Custom Event” keyframes.

• Open via Views > Animation Editor.

• Insert Custom Event keyframes on a track to emit events during playback. Your runtime code can listen for these events to trigger gameplay cues such as footsteps, sound effects or attaching / detaching items.

  Hotkeys 

  Hotkey	Description
  Space	Add event