# The Player Structure

**Goals:** 

* Being able to link a mirror wallet to a real player EOA
* Being able to track its token allowance without holding any tokens on the mirror wallet

```solidity
    /// @notice Player storage structure
    struct Player {
            /// @notice mirror address used to sign txns
        address internalAddress;
            /// @notice amount of GLMB loaded inside the game contract
        uint glmbAvailable;
            /// @notice amount of shakes available
        uint16 shakesAvailable;
            /// @notice counter for games played by this player
        uint gamesPlayed;
    }
```

Once we have this structure defined, we simply need to map it to the real EOA of the player.

```solidity
    /// @notice Real Player Wallet -> Player Data
    mapping(address => Player) public players;
```

Now we can simply access the mapping from our back or front-end using ethers:

```javascript
gameV2Contract.players(walletAddress)
```

Every property such as `internalAddress`, `glmbAvailable` or `gamesPlayed` will now be accessible!


---

# 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://jungle-toolkit.gitbook.io/evm-xcm-jungle-toolkit/examples-of-working-cross-chain-dapps-made-using-the-jungle-toolkit/case-study-the-great-escape/the-player-structure.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.