Sandbox / type
PhysicsShape
Sandbox.PhysicsShape Overview
Declared type and relationship surface; behavioural intent is not inferred from the metadata alone.
PhysicsShape is a declared class in the pinned release metadata.
Exact identity & snapshot
Type relationships
Declarations owned by this type
- Sandbox.PhysicsShape.AddTag(System.String) method
- Sandbox.PhysicsShape.ClearTags() method
- Sandbox.PhysicsShape.DisableAllCollision() method
- Sandbox.PhysicsShape.EnableAllCollision() method
- Sandbox.PhysicsShape.HasTag(System.String) method
- Sandbox.PhysicsShape.Remove() method
- Sandbox.PhysicsShape.RemoveTag(System.String) method
- Sandbox.PhysicsShape.Triangulate(out Vector3[],out System.UInt32[]) method
- Sandbox.PhysicsShape.UpdateHull(Vector3,Rotation,System.Span`1<Vector3>) method
- Sandbox.PhysicsShape.UpdateMesh(System.Collections.Generic.List`1<Vector3>,System.Collections.Generic.List`1<System.Int32>) method
- Sandbox.PhysicsShape.UpdateMesh(System.Span`1<Vector3>,System.Span`1<System.Int32>) method
- Sandbox.PhysicsShape.UpdatePlane(Vector3,Rotation,Vector2) method
- Sandbox.PhysicsShape.Body property
- Sandbox.PhysicsShape.Capsule property
- Sandbox.PhysicsShape.Collider property
- Sandbox.PhysicsShape.EnableSolidCollisions property
- Sandbox.PhysicsShape.EnableTouch property
- Sandbox.PhysicsShape.EnableTouchPersists property
- Sandbox.PhysicsShape.Friction property
- Sandbox.PhysicsShape.IsCapsuleShape property
- Sandbox.PhysicsShape.IsHeightfieldShape property
- Sandbox.PhysicsShape.IsHullShape property
- Sandbox.PhysicsShape.IsMeshShape property
- Sandbox.PhysicsShape.IsSphereShape property
- Sandbox.PhysicsShape.IsTrigger property
- Sandbox.PhysicsShape.IsValid property
- Sandbox.PhysicsShape.Scale property
- Sandbox.PhysicsShape.Sphere property
- Sandbox.PhysicsShape.Surface property
- Sandbox.PhysicsShape.SurfaceMaterial property
- Sandbox.PhysicsShape.SurfaceVelocity property
- Sandbox.PhysicsShape.Surfaces property
- Sandbox.PhysicsShape.Tags 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: 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
Upstream documentation availability
Documentation text is not copied into this export because the release metadata redistribution licence is unresolved.
Evidence and verification
pinned metadata source correspondence unverified
- declaration: pinned-release-metadata
- implementation-source: engine/Sandbox.Engine/Systems/Physics/PhysicsShape.cs
Installed-build compile/runtime state: not run.
Related workflows
None selected.
Related diagrams
None selected.