# Players

## Description

Players in r4nkt are your end-users. They are the individuals that use your software or play your game.

## Properties

Players have the following properties:

| Name         |  Type  | Default |
| ------------ | :----: | :-----: |
| custom\_id   | string |    -    |
| time\_zone   | string |   UTC   |
| custom\_data |  json  | *empty* |

{% hint style="info" %}
Click [here](/concepts/overview.md#common-properties) for information about common properties.
{% endhint %}

### Time Zone

This property represents your player's time zone. Any date/time-related calculations for your player will take this value into account.

If you have criteria that must be met between specified hours or on a specified day, then this is how you make sure that your individual players' actions are interpreted accurately for each individual player. When it's 5 PM for your players in New York, New York, US, it's not 5 PM in Sydney, Australia. In fact, it's not even the same day.

Setting this property correctly for each of your individual players solves this problem. Then, each of your players' actions are interpreted according to the criteria you have specified but in the context of their own time zone.

We use time zones from the [tz database](https://en.wikipedia.org/wiki/Tz_database).

Here is a list of some common or recognizable time zone values:

* `Europe/Copenhagen`
* `Europe/London`
* `America/New_York`
* `America/Los_Angeles`
* `Asia/Tokyo`
* `Australia/Sydney`

You can [look here](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) for a complete listing of possible values.

{% hint style="info" %}
This property defaults to `UTC`.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.r4nkt.com/concepts/players.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.