> 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-26-2024.md).
# 05/26/2024
**Frontend:**
* Implemented a Game History viewer, every game is recorded
* Implemented a live websocket stream, so you can view how many Battle Rooms are currenlty open
**Backend:**
* The Game logic was fully rewritten to the server side, the whole game state is managed by the server now
* Implemented a game history record in the database
* Additional tests were implemented
**Game Development:**
* Rules and Controls Manual
* Bugfixing
* Sound integration
**Upcoming**:
* Further Battleship Bugfixing and stability tests
* Pre-Alpha phase with selected users to collect first feedback on the game and UX flow.
* Timers for Battleship and the Server
* Touch controls for mobile devices
---
# 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://docs.pyreplay.com/development/bi-weekly-dev-updates/05-26-2024.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.