DPB1Class · Interface and panels

SingleSlotUiElement

Reads single slot ui element state and exposes the listed interface operations. Check visibility before using panel-specific values or actions.

Namespace: DreamPoeBot.Loki.Elements

public class SingleSlotUiElement
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

10 declared here

Search includes inherited members below. 37 matching inherited members →

SingleSlotUiElement

MethodLink ↗
public SingleSlotUiElement.SingleSlotUiElement()

Creates a new SingleSlotUiElement instance.

SingleSlotUiElement

MethodLink ↗
public SingleSlotUiElement.SingleSlotUiElement(Element element, SingleSlotUiElement.SingleSlotType slotType = SingleSlotUiElement.SingleSlotType.inventory)

Creates a new SingleSlotUiElement instance using the supplied arguments.

Parameters

element

Specifies element.

slotType
Parameter type: SingleSlotTypeNo current DPB page is linked for this built-in, external, generic or compatibility-only type.

Specifies slot type. Optional; the default is shown in the signature.

CenterClickLocation

MethodLink ↗
public Vector2i SingleSlotUiElement.CenterClickLocation()

Calls CenterClickLocation on SingleSlotUiElement without arguments and returns Vector2i. Open the return contract below before using the result.

Return type: Vector2i
Explore Vector2i → members & methods

A two-dimensional integer position. Used by grid-position and pathfinding APIs; screen-position APIs may expect a different coordinate type.

Returns: The Vector2i result.

SlotClickLocation

MethodLink ↗
public Vector2i SingleSlotUiElement.SlotClickLocation(Vector2i slot)

Calls SlotClickLocation on SingleSlotUiElement with slot and returns Vector2i. Open the return contract below before using the result.

Return type: Vector2i
Explore Vector2i → members & methods

A two-dimensional integer position. Used by grid-position and pathfinding APIs; screen-position APIs may expect a different coordinate type.

Parameters

slot

Specifies slot.

Returns: The Vector2i result.

ItemElement

PropertyLink ↗
public Element SingleSlotUiElement.ItemElement { get; }

Reads item element on SingleSlotUiElement as Element. Open the value type below for its members and accepted values.

Value type: Element
Explore Element → members & methods

A game-interface element. Inspect text, visibility, geometry and child elements; follow the individual members for their signatures and result types. Prefer a named panel wrapper when one is available.

SocketCount

PropertyLink ↗
public int SingleSlotUiElement.SocketCount { get; }

Reads socket count on SingleSlotUiElement as int. The exact type and accessors are shown below.

Value type: intNo current DPB page is linked for this built-in, external, generic or compatibility-only type.

Inherited members and contracts

37 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 float Element.Width { get; } Declared by Element

Reads width on Element as float. The exact type and accessors are shown below.

public void Element.WriteVisibleFlag(int flag) Declared by Element

Writes visible flag using the supplied arguments.

public float Element.X { get; } Declared by Element

Reads x on Element as float. The exact type and accessors are shown below.

public long Element.XAddress { get; } Declared by Element

Reads xaddress on Element as long. The exact type and accessors are shown below.

public float Element.Y { get; } Declared by Element

Reads y on Element as float. The exact type and accessors are shown below.

public long Element.YAddress { get; } Declared by Element

Reads yaddress on Element as long. The exact type and accessors are shown below.

public long Element.zoomAddress { get; } Declared by Element

Reads zoom address on Element as long. The exact type and accessors are shown below.

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.