> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/odk-docs/odk-plugin/player-profile.md).

# Player Profile

Who's who?

All player profile information about users is available within the `BPMC_ODK_PlayerProfileComponent`. This is a morpheus replicated component, and available on every player's morpheus actor. However some information is only replicated on Foreground Actors, so information for non-authoritative players will only be available dependent on the relevancy of the non-auth player to the calling player.

{% hint style="info" %}
Note: When retrieving data from the player profile, always make sure the `IsPlayerProfileLoaded` function has completed first, to ensure your data is relevant. You can also bind to the `OnPlayerProfileLoaded` event on the same component to be informed when a profile's data has been loaded.
{% endhint %}

#### Player name (foreground replicated)

A player's name is available via the `GetPlayerName` function on the component, and you can listen for updates via the `OnPlayerNameUpdated` event

#### Player profile url (foreground replicated)

A player's profile url is available via the `GetProfilePictureUrl` function on the component, and you can listen for updates via the `OnProfilePictureUrlUpdated` event.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.otherside.xyz/odk-docs/odk-plugin/player-profile.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
