Players
Content Creators
Contributors
Search
Player data

Player data

Player position and rotation #

Use the PlayerEntity and the CameraEntity to know the player’s position and rotation, by checking their Transform components.

function getPlayerPosition() {
	if (!Transform.has(engine.PlayerEntity)) return
	if (!Transform.has(engine.CameraEntity)) return

	//player position
	const playerPos = Transform.get(engine.PlayerEntity).position

	//player rotation
	const playerRot = Transform.get(engine.PlayerEntity).rotation

	//camera position
	const CameraPos = Transform.get(engine.CameraEntity).position

	//camera rotation
	const CameraRot = Transform.get(engine.CameraEntity).rotation

	console.log('playerPos: ', playerPos)
	console.log('playerRot: ', playerRot)
	console.log('cameraPos: ', CameraPos)
	console.log('cameraRot: ', CameraRot)
}

engine.addSystem(getPlayerPosition)
  • PlayerEntity position: The avatar’s position, at chest height. Approximately at 0.88 cm above the ground.
  • PlayerEntity rotation: The direction in which the avatar is facing, expressed as a quaternion.
  • CameraEntity position:
    • In 1st person: Equal to the avatar’s position, but at eye-level. Approximately at 1.75 cm above the ground.
    • In 3rd person: May vary depending on camera movements.
  • PlayerEntity rotation:
    • In 1st person: Similar to the direction in which the avatar is facing, expressed as a quaternion. May be rounded slightly differently from the player’s rotation.
    • In 3rd person: May vary depending on camera movements.

📔 Note: Avoid referring to the engine.PlayerEntity or the engine.CameraEntity on the initial scene loading, because that can result in errors if the entities are not initialized yet. To avoid this problem, use these inside the main() function, or on a function indirectly called by main(). You can also encapsulate the behavior in an async executeTask block .

Another option is to refer to these entities inside a system. There they will always be available, because the first execution of the system is called once the scene is already properly initialized.

Fetch all players #

All players in the scene have a Transform component. This component is read only in avatars. To fetch the positions of all players, iterate over all entities with a PlayerIdentityData component.

import { PlayerIdentityData } from '@dcl/sdk/ecs'

for (const [entity, data, transform] of engine.getEntitiesWith(
	PlayerIdentityData,
	Transform
)) {
	console.log('Player data: ', { entity, data, transform })
}

The code above iterates over all entities with a Transform and a PlayerIdentityData component, and logs their data. You can use this same method to get any of the available data of all players.

See Event listeners to learn how to detect and react when new players join into the scene.

Get player data #

Use getPlayer() to fetch data about the current player, or any other player in the scene.

import { getPlayer } from '@dcl/sdk/src/players'

export function main() {
	createCube(5, 1, 5)

	let myPlayer = getPlayer()

	if (myPlayer) {
		console.log('Name : ', myPlayer.name)
		console.log('UserId : ', myPlayer.userId)
	}
}

getPlayer() returns the following:

  • name: (string) The player’s user name, as others see in-world
  • userId: (string) A UUID string that identifies the player. If the player has a public key, this field will have the same value as the public key.
  • isGuest: (boolean) Indicates if the player has a public key. True if the player is a guest account without a public key.
  • position: (Vector3) The position of the avatar in the scene.
  • avatar: A nested object with data about the player’s base avatar and appearance.
  • wearables: An array of identifiers for each of the wearables that the player is currently wearing. For example urn:decentraland:off-chain:base-avatars:green_hoodie. All wearables have a similar identifier, even if they’re NFTs.
  • emotes: An array of identifiers for each of the emotes that the player currently has equipped in the quick access wheel.
  • entity: A reference to the player entity. This can be handy to pass to other functions, or to add custom components to it.

The avatar object has the following nested information:

  • bodyShapeUrn: An identifier for the avatar’s general body shape. Either urn:decentraland:off-chain:base-avatars:BaseFemale for female or urn:decentraland:off-chain:base-avatars:BaseMale for male.
  • skinColor: Player skin color as a Color4
  • eyesColor: Player eye color as a Color4
  • hairColor: Player hair color as a Color4
  • name: The player’s name.
import { getPlayer } from '@dcl/sdk/src/players'

export function main() {
	createCube(5, 1, 5)

	let myPlayer = getPlayer()

	if (myPlayer) {
		console.log('Is Guest: ', myPlayer.isGuest)
		console.log('Name : ', myPlayer.name)
		console.log('UserId : ', myPlayer.userId)
		console.log('Avatar shape : ', myPlayer.position)
		console.log('Avatar shape : ', myPlayer.avatar?.bodyShapeUrn)
		console.log('Avatar eyes color : ', myPlayer.avatar?.eyesColor)
		console.log('Avatar hair color : ', myPlayer.avatar?.hairColor)
		console.log('Wearables on : ', myPlayer.wearables)
		console.log('Emotes available : ', myPlayer.emotes)
	}
}
💡 Tip: When testing in preview, to avoid using a random avatar, run the scene in the browser connected with your Metamask wallet. In the Decentraland Editor, open the Decentraland tab and hover your mouse over it to display the three dots icon on the top-right. Click this icon and select Open in browser with Web3.

To get the data for a specific player in the scene, different from the current player, run getPlayer() with an object with a userId property.

import { getPlayer } from '@dcl/sdk/src/players'

for (const [entity, data, transform] of engine.getEntitiesWith(
	PlayerIdentityData,
	Transform
)) {
	let player = getPlayer({ userId: data.address })
	console.log('PLAYER : ', player?.name)
}

The snippet above iterates over all the entities with a PlayerIdentityData component, meaning all the avatar entities in the scene. It then runs the getPlayer() for that entity.

getPlayer() can only fetch data from players who are currently standing in the same scene, they don’t have to necessarily be in visual range, but they should be connected to the same comms island. To try this out in preview, open a second tab and log in with a different account, and have both players stand inside the scene.

📔 Note: User IDs must always be lowercase. If copying a wallet address, make sure all the characters are set to lowercase.

Data from any player #

To obtain information from any player, make a REST API call to the content servers.

This information is exposed in the following URL, appending the player’s user id to the url parameter.

https://peer.decentraland.org/lambdas/profile/<player user id>

💡 Tip: Try the URL out in a browser to see how the response is structured.

The following information is available from this API:

  • displayName: (string) The player’s user name, as others see in-world
  • userId: (string) A UUID string that identifies the player. If the player has a public key, this field will have the same value as the public key.
  • hasConnectedWeb3: (boolean) Indicates if the player has a public key. True if the player has one.
  • publicKey: (string) The public key of the player’s Ethereum wallet. If the player logs in as a guest, with no linked wallet, this field will be null.
  • avatar: A nested object with data about the player’s appearance.
  • version: (number) A version number that increases by one every time the player changes any of their settings. Use this if you encounter conflicting data, to know what version is more recent.
📔 Note: For any Ethereum transactions with the player, always use the publicKey field, instead of the userId, to avoid dealing with non-existing wallets.

The avatar object has the following nested information:

  • wearables: WearableId[] An array of identifiers for each of the wearables that the player is currently wearing. For example urn:decentraland:off-chain:base-avatars:green_hoodie. All wearables have a similar identifier, even if they’re NFTs.

  • bodyShape: An identifier for the avatar’s general body shape. Either urn:decentraland:off-chain:base-avatars:BaseFemale for female or urn:decentraland:off-chain:base-avatars:BaseMale for male.

  • skinColor: ColorString A hex value for the player’s skin color.

  • hairColor: ColorString A hex value for the player’s hair color.

  • eyeColor: ColorString A hex value for the player’s eye color.

  • snapshots: A nested object with base64 representations of .jpg images of the player in various resolutions.

    • face256: string The player’s face as a 256x256 pixel image.
    • body: string The full resolution image of the player standing straight, with 512x1024 pixels.
❗Warning The snapshots of the avatar will be deprecated in the future and will no longer be returned as part of an avatar’s data. The recommended approach is to use AvatarTexture instead, see Avatar Portraits .

Unlike getPlayer(), this option is not limited to just the players who are currently in the same scene, or even in the same server. With this approach you can fetch data from any player that has logged onto the servers in the past.

If you know which server the player you want to query is connected to, you can get more up-to-date data by sending your requests to that specific server. For example, if the player changes clothes, this information will be available instantly in the player’s server, but will likely take a couple of minutes to propagate to the peer.decentraland.org server.

https://<player server>/lambdas/profile/<player user id>

💡 Tip: You can obtain the current player’s server by fetching getRealm().domain.

This example combines myProfile.userId and getRealm() to obtain the player’s data directly from the server that the player is on:

import { getRealm } from '~system/Runtime'
import { myProfile } from '@dcl/sdk/network'

async function fetchPlayerData() {
	const { realmInfo } = await getRealm({})

	const url = `${realmInfo.baseUrl}/lambdas/profile/${myProfile.userId}`
	console.log('using URL: ', url)

	try {
		const json = (await fetch(url)).json()

		console.log('full response: ', json)
		console.log(
			'player is wearing :',
			json[0].metadata.avatars[0].avatar.wearables
		)
		console.log('player owns :', json[0].metadata.avatars[0].inventory)
	} catch {
		console.log('an error occurred while reaching for player data')
	}
}

fetchPlayerData()

Player data components #

Instead of using getPlayer(), you can read data directly from a series of components that store the data on each player entity. The following components exist:

  • PlayerIdentityData: Stores the player address and an isGuest property to flag guest accounts.
  • AvatarBase: Stores data about the base avatar, including:
    • name: The player’s name.
    • bodyShapeUrn: The ids corresponding to male or female body type.
    • skinColor: Player skin color as a Color4
    • eyeColor: Player eye color as a Color4
    • hairColor: Player hair color as a Color4
  • AvatarEquippedData: The list of equipped wearables and emotes.
    • wearableUrns: The list of wearables that the player currently has equipped.
    • emoteUrns: The list of emotes that the player currently has equipped in the quick access wheel.
  • AvatarEmoteCommand: Info about emotes that the player is currently playing. It includes:
    • emoteUrn: The URN for the last emote played by the player, since they entered the scene
    • loop: True if the emote is being looped
    • timestamp: The time when this emote was triggered
for (const [entity, data, base, attach, transform] of engine.getEntitiesWith(
	PlayerIdentityData,
	AvatarBase,
	AvatarEquippedData,
	Transform
)) {
	console.log('PLAYER DATA: ', { entity, data, transform, base, attach })
}
📔 Note: All of these components are read-only. You cannot change their values from the scene.

Get Portable Experiences #

Portable experiences are essentially scenes that are not constrained to parcels of land. Players can carry these with them anywhere they go in Decentraland, adding a new layer of content over the world. Smart Wearables are examples of portable experiences. You may want to know if a player is wearing one of these, since a smart wearable may enable players to have abilities that could be considered cheating in a competitive game. For example, in a platform game, a player that wears a jetpack has a very unfair advantage over others.

As a scene creator, you may want to limit what players wearing portable experiences can do in your scene. Use getPortableExperiencesLoaded() to check if the player has any portable experiences currently activated.

import { getPortableExperiencesLoaded } from '~system/PortableExperiences'

executeTask(async () => {
	let portableExperiences = await getPortableExperiencesLoaded({})
	console.log(portableExperiences.loaded)
})

getPortableExperiencesLoaded() returns an array of objects, each of these objects includes an id attribute. In the case of wearables, the id is the wearable’s URN.

Get detailed info about a player’s wearables #

The getPlayer() function returns only a list of wearable ids, without information about each wearable. Maybe you want to check for any wearable of a specific category (eg: hats), or any wearable of a specific rarity (eg: Mythic), for that you’ll need to fetch more detailed information about the player’s wearables.

Make a REST API call to the following URL, to obtain a full updated list of all wearables that are currently usable, with details about each.

${playerRealm.realmInfo.baseUrl}/lambdas/collections/wearables-by-owner/${userData.userId}?includeDefinitions

📔 Note: To construct this URL, you must obtain the realm (likely with with getRealm()) and the player’s id (likely with getPlayer())

This feature could be used together with fetching info about the player, to for example only allow players to enter a place if they are wearing any wearable from the halloween collection, or any wearable that is of legendary rarity.

💡 Tip: Try the URL out in a browser to see how the response is structured. 
import { getPlayer } from '@dcl/sdk/src/players'
import { getRealm } from '~system/Runtime'

async function fetchWearablesData() {
	try {
		let userData = getPlayer({})
		const realm = await getRealm({})

		const url =
			`${realm.realmInfo?.baseUrl}/lambdas/collections/wearables-by-owner/${userData.userId}?includeDefinitions`.toString()
		console.log('using URL: ', url)

		let response = await fetch(url)
		let json = await response.json()

		console.log('full response: ', json)
	} catch {
		console.log('an error occurred while reaching for wearables data')
	}
}

executeTask(fetchWearablesData)

TODO: Update snippet

Check the player’s camera mode #

Players can either be using a 1st or 3rd person camera when exploring Decentraland. Check which of these the player is using by checking the value CameraMode component of the engine.CameraEntity entity.

function checkCameraMode() {
	if (!Transform.has(engine.CameraEntity)) return

	let cameraEntity = CameraMode.get(engine.CameraEntity)

	if (cameraEntity.mode == CameraType.CT_THIRD_PERSON) {
		console.log('The player is using the 3rd person camera')
	} else {
		console.log('The player is using the 1st person camera')
	}
}

engine.addSystem(checkCameraMode)
📔 Note: Camera information is only available for the current player running the scene. You can’t query for the camera data of any other player.

The camera mode uses a value from the CameraType enum. The following values are possible:

  • CameraType.CT_FIRST_PERSON
  • CameraType.CT_THIRD_PERSON

The CameraMode component of the engine.CameraEntity is read-only, you can’t force the player to change camera mode through this.

💡 Tip: To change the player’s camera mode, use a Camera modifier area .

Knowing the camera mode can be very useful to fine-tune the mechanics of your scene to better adjust to what’s more comfortable using this mode. For example, small targets are harder to click when in 3rd person.

📔 Note: Avoid referring to the engine.CameraEntity on the initial scene loading, because that can result in errors if the entities are not initialized yet. To avoid this problem, use these inside the main() function, or on a function indirectly called by main(). You can also encapsulate the behavior in an async executeTask block .

Another option is to refer to this entity inside a system. It will always be available, because the first execution of the system is called once the scene is already properly initialized.

Check if the player has the cursor locked #

Players can switch between two cursor modes: locked cursor mode to control the camera or unlocked cursor mode for moving the cursor freely over the UI.

Players unlock the cursor by clicking the Right mouse button or pressing the Esc key, and lock the cursor back by clicking anywhere in the screen.

Check the PointerLock component of the scene’s camera entity to find out what the current cursor mode is.

export function main() {
	const isLocked = PointerLock.get(engine.CameraEntity).isPointerLocked
	console.log(isLocked)
}

See Event listeners to see how to easily react to changes in the cursor state.

The PointerLock component of the engine.CameraEntity is read-only, you can’t force the player to lock or unlock the cursor.

📔 Note: Avoid referring to the engine.CameraEntity on the initial scene loading, because that can result in errors if the entities are not initialized yet. To avoid this problem, use these inside the main() function, or on a function indirectly called by main(). You can also encapsulate the behavior in an async executeTask block .

Another option is to refer to the entity inside a system. It will always be available, because the first execution of the system is called once the scene is already properly initialized.

Calendar April 17, 2024
Edit Edit this page
Home Privacy Policy Terms of Use Content Policy Code of Ethics
© 2023 Decentraland