> 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 %}