> For the complete documentation index, see [llms.txt](https://hashguardians-2.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hashguardians-2.gitbook.io/whitepaper/directory/dynamic-development.md).

# Dynamic Development

We are committed to creating a dynamic game design and development process.  As a result, HashGuardians will have a dynamic, expanding world.

**The HashGuardians world map will change throughout the playing cycle.** 

* As developers, this gives us the opportunity to integrate new elements into the HashGuardians universe, such as buildings, quests, mini-games, and a few exciting things we aren’t quite ready to talk about quite yet.
* As players, this will provide a dynamic gaming experience.  There will always be new things to discover and new adventures to experience. 

We feel that a dynamic world map, backed by our dynamic development process, will give our players the best possible blockchain gaming experience while keeping things fresh and interesting.


---

# 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://hashguardians-2.gitbook.io/whitepaper/directory/dynamic-development.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.