Editor / type

AssetType

Editor.AssetType

Overview

Declared type and relationship surface; behavioural intent is not inferred from the metadata alone.

Type relationships

Base type

—

Interfaces

—

Declarations owned by this type

• Editor.AssetType..ctor() constructor
• Editor.AssetType.Find(System.String,System.Boolean) method
• Editor.AssetType.FromExtension(System.String) method
• Editor.AssetType.FromType(System.Type) method
• Editor.AssetType.All property
• Editor.AssetType.Animation property
• Editor.AssetType.AnimationGraph property
• Editor.AssetType.Category property
• Editor.AssetType.Color property
• Editor.AssetType.FileExtension property
• Editor.AssetType.FileExtensions property
• Editor.AssetType.Flags property
• Editor.AssetType.FriendlyName property
• Editor.AssetType.HasDependencies property
• Editor.AssetType.HasEditor property
• Editor.AssetType.HiddenByDefault property
• Editor.AssetType.Icon128 property
• Editor.AssetType.Icon16 property
• Editor.AssetType.Icon256 property
• Editor.AssetType.Icon64 property
• Editor.AssetType.ImageFile property
• Editor.AssetType.IsGameResource property
• Editor.AssetType.IsSimpleAsset property
• Editor.AssetType.MapFile property
• Editor.AssetType.Material property
• Editor.AssetType.Model property
• Editor.AssetType.PrefersIconThumbnail property
• Editor.AssetType.ResourceType property
• Editor.AssetType.Shader property
• Editor.AssetType.SoundEvent property
• Editor.AssetType.SoundFile property
• Editor.AssetType.Soundscape property
• Editor.AssetType.Texture property

Inherited members

Direct inherited members are not expanded here because the pinned record does not establish a complete inheritance closure.

Flow

The diagram separates the declared inputs, operation and result. Connections describe the recorded relationship; they do not establish execution order or lifecycle behaviour.

Open this operation in the flow explorer →

Examples

No reviewed code example or workflow covers this declaration. Use the exact declaration and inputs/outputs flow as the available local teaching surface, then run a bounded installed-build probe before relying on behaviour. Open the exact declaration flow.

Constraints and pitfalls

• Execution context: editor
• A public declaration is not proof of sandbox allowlisting.
• No compile/runtime verification was run.

Prerequisites and limits

• Resolve the type identity in the pinned release before relying on its declaration.

Still unknown

• Installed-build callability, compile behaviour and runtime effects are not established by this snapshot.
• No indexed implementation-source chunk is linked to this declaration; the entry is declaration-only.

declaration-onlymetadata-only

Evidence and verification

Related workflows

None selected.

Related diagrams

None selected.