> For the complete documentation index, see [llms.txt](https://doctor-pepe.gitbook.io/doctor-pepe-or-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doctor-pepe.gitbook.io/doctor-pepe-or-white-paper/doctor-pepe-features/game.md).
# Game
Time for fun!
DPEPE is an incredibly addictive and easy-to-play game where you get to choose the scenario and face exciting challenges in order to earn rewards.
The game revolves around the daily routine of a doctor, including consultations, emergencies, and operating procedures, all with a delightful Pepe charm!
Designed with 20 levels, each level consists of 9 rounds that need to be completed to progress.
Level 1 - Scenario: Waking up to Consultants Round
1 - Dressing up and getting the proper equipment Round
2 - Bringing coffee to attendants Round
3 - Taking care of patients Round
4 - Visiting patients at the hospital Round
5 - Preparing a class for students Round
6 - Checking messages Round
7 - Dinner time Round
8 - Receiving an emergency call Round
9 - Performing a surgery in the hospital OR
Once you successfully complete Level 1, you can advance to Level 2.\
\
It is not a play to earn game. It is just Pepe fun!!!
---
# 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:
```
GET https://doctor-pepe.gitbook.io/doctor-pepe-or-white-paper/doctor-pepe-features/game.md?ask=
```
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.