> For the complete documentation index, see [llms.txt](https://docs.pyreplay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyreplay.com/development/bi-weekly-dev-updates/05-12-2024.md).
# 05/12/2024
**Backend:**
* Since the Alephium explorer is lacking the ability to check for the owner of a specific NFT address, I've initially implemented a snpashot approach which crawls through Pyreplays database and checks the NFTs of every registered user. This works totally fine, but is a bit computational expensive. With the development of by 0xreed they keep track of all NFT transfers and offer an API for receiving exactly that data. I'm looking forward to using that API instead of the databse crawler from now on.
* Additional tests were implemented.
**Game Development:**
* The core gameplay is working within a local environment in Unity:
**Upcoming**:
* Moving the gameplay logic to the server side: This is a crucial part, since Client sided applications can always be hacked and cheated on. Moving the logic to the server side is the only possible way to prevent this. This means the Frontend Client is "dumb" so to say, and every player action is validated on the server.
* UX enhancements and sounds for Battleship.
* Frontend User Profile + Customization options
---
# 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.pyreplay.com/development/bi-weekly-dev-updates/05-12-2024.md?ask=&goal=
```
`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.