# Features

## Game Features <a href="#view-game-diagram" id="view-game-diagram"></a>

* You need to send daily paper-trade orders to keep your streak and move up the stages
* Join trade-battle events to learn, level up and earn more

Battles are designed for player vs player engagement, the battle outcomes provide variables for an elo-like rating system. This scoreboard serves as one of many low level core relationship keys or archetypes that are essential in building alliances. Alliances are based upon coincidences of relationship keys or archetypes, more information about this will be found inside the archetypes section.

The goal of the game is to become the most successful investor in the nearby cities and experience the serendipity of winning a life-changing trade between a sea of coincidences. The use of an AI assistant if the player permission level is sufficient, greatly helps young venture capitalists make good trade decisions.

As players make profitable investments, they can build on the outskirts of the city based on their profits and balances. They can also link their trading journal and maintain a high elo score (based on the elo rating system) for a good global ranking position.

Mutability and speed of data expands the stages of which a game can exist on, the first data-level is the browser client. The browser’s local storage enables standalone and even offline paper-trading sessions, allowing you to send unlinked buy/sell orders and keep your daily practice even without a real internet connection.

* Local storage stations are set to their default values once the web page is reloaded or manually refreshed by a player.


---

# 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://webpov.gitbook.io/city/what-is-webcity/features.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.
