DPB1Class · World, character and items

Beam

Provides beam data and the operations listed below. Related types link to the values this API consumes or returns.

Namespace: DreamPoeBot.Loki.Components

public class Beam
Reference: DPB1 0.3.29.56Compare the DPB2 reference → Check signatures and usage notes separately; a matching type is not a compatibility guarantee.

Members and overloads

1 declared here

Search includes inherited members below. 2 matching inherited members →

Show all members

StartObject

PropertyLink ↗
public NetworkObject Beam.StartObject { get; }

Gets the object referenced by the beam's start anchor, or null when unavailable or expired. This identifies an anchor, not whether the beam is visible or deals damage.

Value type: NetworkObject
Explore NetworkObject → members & methods

Common view of an object in the current area, including its identity, position and interaction state.

Added in public DPB1 0.3.29.56. Resolve the beam's actual start/end anchor objects rather than choosing nearby objects. Either link may be null when unavailable or expired. The beam's Owner is the effect object, not necessarily its emitter. Anchor links and visual endpoints do not establish damage, active trap state or a safe path.

Inherited members and contracts

2 public members from documented base types and interfaces. Links open the original declaration; overrides are shown only once. Search using the member field above.

public NetworkObject Component.Owner { get; } Declared by Component

Entity that owns this component, resolved through the validated component layout.

public Entity Component.OwnerEntity { get; } Declared by Component

Lifetime-aware owner when the component was obtained through Entity.GetComponent. Falls back to the validated owner backlink for directly-created component wrappers.

No dedicated example has been reviewed for this member. Browse the class reference; its examples may demonstrate other operations.

DPB1 0.3.29.56 · Reference reviewed 2026-10-30. Descriptions use source summaries where available, otherwise concise signature-based descriptions. Examples illustrate usage; they are not a live-game test.