> For the complete documentation index, see [llms.txt](https://docs.ares-alpha.com/ares-alpha-props-manual-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ares-alpha.com/ares-alpha-props-manual-en/player-tag.md).

# Player tag

<table data-header-hidden><thead><tr><th></th><th></th><th data-hidden></th></tr></thead><tbody><tr><td><img src="/files/LP3fB4bs5apWObJuKVe8" alt=""></td><td><img src="/files/r6ObvMkbAg3Cmc9VSDTO" alt=""></td><td></td></tr></tbody></table>

{% hint style="danger" %}
**From Spring 2024 onward**, all new props come equipped with our latest RFID NFC reader, fully compatible with the new player tags.\
If you have an older prop, a hardware upgrade is required to enable NFC tag support.

To check compatibility, take a look at your prop RFID reader:

* **Red** reader = new, NFC-compatible
* **Blue** reader = older model, upgrade needed

Need an upgrade? The new NFC reader is available in our shop to bring your prop up to date.

Player tags works with ATB Pro, ATB Mini and Minibox PRO
{% endhint %}

Personal player tags (wristbands or cards) are programmed in the Ares Alpha app with the player's details and selected team. This is why the tag needs to be rewritten each time the player uses it with a different team.&#x20;

There are two write modes available:&#x20;

**Personal Write:** Each player programs their own tag with their personal profile. Since the tag's ID corresponds to a real Ares Alpha player, points earned during the game will also appear in the Ares Alpha app.

**Mass Write:** Game Masters can quickly program multiple tags using NATO-style names (e.g., Alpha, Bravo, etc.). This method is ideal when tags are owned by the Game Master and temporarily assigned to players for individual games. In this mode, player points are recorded only on the local prop and **will not appear in the Ares Alpha app**.

<figure><img src="/files/0Rbo24wjhIUd7LckiA1A" alt="" width="185"><figcaption></figcaption></figure>

In contrast to team tags, when player tags are used, the prop will display points for both individual players and teams. This addition enhances the experience by giving players a personal stake in the game, encouraging greater engagement and motivating them to actively use the prop. By tracking and showcasing individual achievements, players are more likely to feel a sense of accomplishment and competition, which can further drive their involvement and enjoyment throughout the game.

Player tags can be used in game modes: Domination, Factory/Depot, Collect tags and Players checkpoint.

Additionally, there is a new game mode: [Players checkpoint](/ares-alpha-props-manual-en/configuration-and-game-modes/game-modes/players-checkpoint.md), specifically designed for the new player tags.&#x20;


---

# 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 dynamically by asking a question.

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

```
GET https://docs.ares-alpha.com/ares-alpha-props-manual-en/player-tag.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
