Block data component
This manual details the control functions and usage provided by the Block data component in the Unity editor.
Note
Starting from version 2.13, you should use the block editor tool for Unity application development.
Version note
Starting from custom map version 9.4, the Block Mesh data format has been upgraded from eme to gltfx.
All features in this document that only support the new format are marked as [>=9.4]. If your data version is lower than 9.4, the related UI controls will not take effect.
All features in this document that only support the old format are marked as [<9.4]. If your data version is 9.4 or above, the related UI controls will not take effect.
Initial state
The initial state of the component refers to the state of the Block data component when the tool is just created, no service is selected and no data is loaded.

| number | control name | control type | function description |
|---|---|---|---|
| clear | clear cache file | button | clear all locally cached Block data. |
Selected service state
The selected service state of the component refers to the state of the Block data component after a service (Mega Block localization service, Mega Block storage service, etc.) is selected in the tool.

| number | control name | control type | function description |
|---|---|---|---|
| 7 | refresh Block list | button | refresh the information on the current Block tool and synchronize with cloud service data. |
| 8 | select ray detection precision | dropdown menu | [>=9.4]set the model precision of the Block's Mesh when used for ray detection. lowering the precision will speed up LOD loading in the editor, but sacrifice editing precision: Min LOD (default): use the simplest model for ray detection. None: do not load collision model, do not perform ray detection. Match LOD: load collision model according to LOD. |

