> For the complete documentation index, see [llms.txt](https://dr1cryptodr1ver.gitbook.io/dr1ver-dr1usd-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dr1cryptodr1ver.gitbook.io/dr1ver-dr1usd-whitepaper/player-vs-players-mode.md).

# Player Vs Players mode

![](/files/B3GBDNd0g6Byas2O1ult)

In player vs player mode the users can select at the garage a car to play with, the users can run against others unlimited times a day, regarding that every types of cars need a repair after 10 races.

After select a cars users need to aprove the transaction in the wallet, after 30 seconds if don’t find a adversary to Mach the display show’s:&#x20;

to come back later no restaurant is open for delivery in the moment!

The player who makes a high score by the correct delivery for the buildings wins 90% of the pot! The remaining Balance goes back to free mode Play2earn.


---

# 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://dr1cryptodr1ver.gitbook.io/dr1ver-dr1usd-whitepaper/player-vs-players-mode.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.
