> For the complete documentation index, see [llms.txt](https://docs.hyperplay.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperplay.xyz/developer-docs/design-considerations.md).

# Design Considerations

## Security

### Requesting a Transaction from the Player

We highly recommend making it clear to the player that the game will be requesting a transaction from them prior to requesting it. HyperPlay also helps with this by overlaying notifications if a transaction is pending on mobile.

All requests must be made from client side code in your game.

### Reading Blockchain State

If your game is multiplayer, we highly recommend reading blockchain state from your server side code. Otherwise the player might be able to fake a transaction to obtain an in-game item.

## Game Engine Integrations

There are several methods of integrating HyperPlay into your game depending on which engine you using.

{% content-ref url="/pages/jfoqDZZMweYbSndyK3TA" %}
[Unreal Engine Integration](/developer-docs/design-considerations/unreal-engine-integration.md)
{% endcontent-ref %}

{% content-ref url="/pages/BvfiSfW4cQUYQSobkGys" %}
[Unity Integration](/developer-docs/design-considerations/unity-integration.md)
{% endcontent-ref %}


---

# 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://docs.hyperplay.xyz/developer-docs/design-considerations.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.