> For the complete documentation index, see [llms.txt](https://abzi.noxen.b0se.liloche.docs.rtype.liloche.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://abzi.noxen.b0se.liloche.docs.rtype.liloche.dev/overview.md).

# Overview

A networked R-Type clone built for the Epitech G-ING-500 unit: a multithreaded authoritative server and a graphical client, built on a game engine of our own design.

> Status: greenfield. The repository is being scaffolded; build instructions land once the stack is chosen (see [Technical Choices](/technical-choices.md)).

## Supported platforms

* Linux — mandatory, for both client and server.
* Windows — cross-platform target (cross-play between Linux and Windows clients).

## Binaries

* `r-type_server`
* `r-type_client`

## Build

TODO: prerequisites and package-manager setup, then the CMake preset commands.

```sh
# TODO: cmake --preset <preset>
# TODO: cmake --build --preset <preset>
```

## Run

```sh
# TODO: r-type_server <port>
# TODO: r-type_client <host> <port>
```

## Tests

Unit tests run through CTest:

```sh
# TODO: ctest --preset <preset>
```

## Documentation

* [Technical Choices](/technical-choices.md) — major technical choices and the dependency allowlist.
* `docs/` — developer documentation and design notes (TODO).

## Authors

TODO.

## License

TODO.


---

# 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://abzi.noxen.b0se.liloche.docs.rtype.liloche.dev/overview.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.