> For the complete documentation index, see [llms.txt](https://kap35.gitbook.io/kap-engine-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kap35.gitbook.io/kap-engine-wiki/kapengine/getting-started.md).

# Getting Started

### What is KapEngine ?

KapEngine is an ECS game engine in C++. Show source code in [github](https://github.com/benji-35/KapEngine).

Made by [benji-35](https://github.com/benji-35) (Benjamin Delvert) and helped by [Chaika9](https://github.com/Chaika9) for compilation and other tips.

### Why use KapEngine ?

As some game engines, KapEngine is made to create your own game. But the difference is in graphical library. The power of KapEngine is your free hands to choose your own graphical library. You can also use several graphical library and change it while your game is running.

We also chose to make this engine easy to use. Including the ECS, KapEngine work like Unity3D with GameObjects and Components.

### Which language ?

KapEngine is made and use C++ language. All basics things you want to add in your game should be in C++.


---

# 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://kap35.gitbook.io/kap-engine-wiki/kapengine/getting-started.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.