DPB2Class · Game state and actions

LokiPoe.TerrainData

This class let you retrieve information about the Terrain layout in the current area. This is exactly how the game use some specific graphic elements, to draw the area map. This graphic elements are placed in the zone as you enter the area, for the entire zone and are static elements. This mean that you can know where exactly they are (theyr coordinates), without exploring the area. You can use this information to recognize specific spot in a zone, since some special graphic elements, always describe a specific game element, like a stair, a gate, a special door. Please bear in mind that usually there are more than 1 elements of the same kinde placed in a area, and not all of them are placed in walkable space, so you need to iterate all the specific element you want, and check if a path exist to them.

Namespace: DreamPoeBot.Loki.Game

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

Members and overloads

1 declared here
Show all members

Layer0

PropertyLink ↗
public static byte[] LokiPoe.TerrainData.Layer0 { get; }

Retrieve a array of bytes representing the current area bytes layout used by the game to calculate ground (object that can only move on the ground and need to account for terrain obstacle) walkable area. The bytes goes from 0 to 5, representing the min size of a object that can wal on this location, players and Networkobject have usually a size of 3, this mean that they can only walk on location where bytes are 3 or higher. Items or various modificator that change the size o NetworkObjects can change their ability to move on different locations.

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

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

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.