Global / Sandbox.Component/IPressable

Event

Sandbox.Component.IPressable.Event

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

• Sandbox.Component.IPressable.Event..ctor(Sandbox.Component,System.Nullable`1<Ray>) constructor
• Sandbox.Component.IPressable.Event.Deconstruct(out Sandbox.Component,out System.Nullable`1<Ray>) method
• Sandbox.Component.IPressable.Event.Ray property
• Sandbox.Component.IPressable.Event.Source 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

Workflow: Coordinate a feature component with update ordering and explicit state ownership (evidence-backed, not runtime verified)

No standalone code example is linked; the evidence-backed workflow is the bounded example surface for this declaration.

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.
• No indexed implementation-source chunk is linked to this declaration; the entry is declaration-only.

declaration-onlymetadata-only

Evidence and verification

Related workflows

Coordinate a feature component with update ordering and explicit state ownership

Related diagrams

None selected.