DPB2Class · World, character and items

PlayerClass

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

Namespace: DreamPoeBot.Loki.Components

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

Use this API

Useful members available through base types — open a member to read its exact contract:

Members and overloads

4 declared here

Search includes inherited members below. 1 matching inherited member →

PlayerClass

MethodLink ↗
public PlayerClass.PlayerClass()

Creates a new PlayerClass instance.

ToString

MethodLink ↗
public override string PlayerClass.ToString()

Returns a text representation of this value.

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

Returns: The string result.

AscendencyClass

PropertyLink ↗
public AscendancyClass PlayerClass.AscendencyClass { get; }

Reads ascendency class on PlayerClass as AscendancyClass. Open the value type below for its members and accepted values.

Value type: AscendancyClass
Explore AscendancyClass → members & methods

Named values for ascendancy class. Select a value when an API accepts or returns AscendancyClass.

Class

PropertyLink ↗
public CharacterClass PlayerClass.Class { get; }

Reads class on PlayerClass as CharacterClass. Open the value type below for its members and accepted values.

Value type: CharacterClass
Explore CharacterClass → members & methods

Named values for character class. Select a value when an API accepts or returns CharacterClass.

Inherited members and contracts

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

public override bool Component.IsValid { get; } Declared by Component

Whether this component is valid.

DPB2 0.4.5.103 · 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.