• Assets: Individual entities or groups of entities in a world can be added to your personal Asset Library for use in other worlds.
• Scripts: You can copy scripts or parts of scripts from one world into a text editor for insertion into the scripts in other worlds.

Note: These worlds are non-FBS (File Backed Scripts) worlds, which means that asset templates created from these worlds are not compatible with FBS worlds.

Note: If you create an asset template from one of these non-FBS tutorial worlds and the template contains scripts, the scripts are included in the asset template. When you deploy an asset template into a non-FBS world, you create a separate instance of the script for each instance of the asset template, even though the scripts are identical. You can end up with many script instances to manage. More information is provided below.

1. In the desktop editor, locate the entity in the world. Select it.
2. In the Hierarchy panel, verify that you have selected all sub-entities of the entity that you wish to add to your Library.
   1. For example, you may find an entity that is composed of a model and a sound entity. Make sure that you select both of them.
3. Right-click the entity in the Hierarchy panel and select Create Asset.
4. Add a meaningful name and description for the asset.
5. Choose the appropriate folder where you would like to store the asset.
   1. Tip: For assets that you would like to share with your team or across multiple worlds, you should store them in a shared folder. For more information, see Shared Folders.
6. Click Create. The asset template is created in the selected folder.

Note: The tutorial worlds are built using TypeScript v2.0.0. If your world is using TypeScript v1.0.0, these scripts will not work directly in your world. Some syntax and reference fixes are required.

• Review the list of imports.
  • Imports from the Meta Horizon Worlds APIs must be included in your scripts to use the code. Be sure to verify that the imports are actually used in the current script.
  • Some import lines may be pulling in references in other script files in the world. You should review those files to determine if you need to import the entire file or some elements of them.
• Review the list of exports.
  • Entities that are exported from the script may have implications on your code.
• Review the list of events.
  • Events defined within the code need to be supported in your code.
  • Events that are referenced in the code may have an equivalent event under a different name in your code.
• Review the script properties.
  • In some cases, the script properties may refer to assets in the Asset Library or entities in the world. These references may need to be fixed in your world.
• You may want to insert test code, such as console messages into the functions and methods that you are trying to use. These can be used to assess that the system is processing data correctly.

Note: You cannot copy and paste files from one world’s directory to another. These files are not automatically picked up by the desktop editor and integrated into the world’s codebase. Instead, you must open the files and copy out the contents, pasting them into new or existing script files associated with the target world.

Note: These worlds are non-FBS worlds. In a non-FBS world, the option to Spawn New Gizmo from a script in the Script panel is not available. For more information, see Tutorial Assumptions.

1. In the desktop editor, open the Scripts panel.
2. Click the Gear icon.
3. In the Script Settings window, click Script editing.
4. Locate the value for the External Editor Directory.
5. Navigate your local environment to find this directory. Scripts for individual worlds are stored as sub-directories.

Note: Scripts in asset templates from non-FBS worlds do not behave like other assets.

• The deployed script is a completely independent asset from the original script.
  • It is not a versioned instance of the original.
  • Changes made to the script in the world cannot be deployed back to the original asset.
• References related to the script may be broken:
  • The script may not be attached to the entity to which it is supposed to be attached, which is caused by the script being created as an entirely new asset.
  • When the script is re-attached, script-based properties must be defined again.

Tip: You may find it easier to create scripts as asset templates containing a single asset (the script). This effectively turns scripts in the Asset Library as read-only assets that can be deployed and then connected to the entities in your world.