> For the complete documentation index, see [llms.txt](https://dinodash.gitbook.io/copy-of-dinodash-tm-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dinodash.gitbook.io/copy-of-dinodash-tm-whitepaper/developments/computer-gaming.md).

# Computer Gaming

In 2020, the global revenue from the PC gaming industry was estimated to be $37 billion. Tapping into and revolutionizing this market is a key goal for the team. Another significant reason for starting with a PC game is that the majority of blockchain user interactions occur through computers. While the initial launch will be on the PC platform, the team does not plan to stop there. The aim is to create a game that can be played on a wide range of computers, including Macs, Windows, and Linux devices, eventually integrating cross-console play and additional features in the near future.

Computer/Game info: 

Blockchain: Polygon

<mark style="color:red;">Minimum Specs:</mark> <mark style="color:red;">TBD</mark>&#x20;

<mark style="color:red;">Internet Speed:</mark> <mark style="color:red;">TBD</mark>


---

# 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://dinodash.gitbook.io/copy-of-dinodash-tm-whitepaper/developments/computer-gaming.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.