Sandbox / type

TerrainMaterial

Sandbox.TerrainMaterial

Overview

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

TerrainMaterial is a declared class in the pinned release metadata.

Type relationships

Base type

Sandbox.GameResource

Interfaces

—

Declarations owned by this type

• Sandbox.TerrainMaterial..ctor() constructor
• Sandbox.TerrainMaterial.AOImage property
• Sandbox.TerrainMaterial.AlbedoImage property
• Sandbox.TerrainMaterial.BCRTexture property
• Sandbox.TerrainMaterial.DisplacementScale property
• Sandbox.TerrainMaterial.Flags property
• Sandbox.TerrainMaterial.HasHeightTexture property
• Sandbox.TerrainMaterial.HeightBlendStrength property
• Sandbox.TerrainMaterial.HeightImage property
• Sandbox.TerrainMaterial.Metalness property
• Sandbox.TerrainMaterial.NHOTexture property
• Sandbox.TerrainMaterial.NoTiling property
• Sandbox.TerrainMaterial.NormalImage property
• Sandbox.TerrainMaterial.NormalStrength property
• Sandbox.TerrainMaterial.RoughnessImage property
• Sandbox.TerrainMaterial.Surface property
• Sandbox.TerrainMaterial.UVScale property

Inherited members

• Sandbox.GameResource.CopyFrom(Sandbox.GameResource)
• Sandbox.GameResource.Deserialize(System.Text.Json.Nodes.JsonObject)
• Sandbox.GameResource.GetReferencedPackages()
• Sandbox.GameResource.LoadFromJson(System.String)
• Sandbox.GameResource.Serialize()
• Sandbox.GameResource.StateHasChanged()
• Sandbox.GameResource.HasUnsavedChanges
• Sandbox.GameResource.IsRemote
• Sandbox.GameResource.IsValid
• Sandbox.GameResource.ResourceVersion

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: game-or-shared-unknown
• 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.

declaration-and-sourcemetadata-and-source-only

Evidence and verification

Related workflows

None selected.

Related diagrams

None selected.