Put SDL2 soruce code inside your SDK folder, like this:
```
/contrib/sdk/sources/SDL2
```
Run make inside this folder, to build SDL2 for KolibriOS
Put M4KC source code into your SDK folder, like this:
```
/contrib/sdk/sources/m4kc
```
Build it using provided xmake.lua:
```
xmake build m4kc-kolibri
```
Or use your preferred build system.

FAQ

I've either been asked these, or I expect to be at some point.

What's with the cryptic variable names like f22 and i6?

A lot of this code is decompiled from the original java version, and those are names the decompiler assigned to the variables. Much of the code is extremely obfuscated due to what are probably compiler optimizations, and some variables have not been deciphered and renamed yet. This is why they mostly appear in the gameLoop function.

Why is it so slow?

The game uses a 3D voxel raycaster to render things, which is a lot slower than more traditional methods of rendering. Luckily, C provides more powerful ways to optimize something like this than Java - and optimizations will keep coming.

Will you add in _____ from Minecraft?

I plan to port over a lot of user interface features, controls, and gameplay mechanics from the official game. However, this game will be taken in its own direction content-wise. For example, crafting will be a part of the game eventually, but creepers will not. New features will be added if they fit with the aesthetic and feel of the game, and make sense from a technichal and gameplay perspective.

Where does it put saves in KolibriOS

Game will save it's data into same folder as executable, if placed on disk with write support. Otherwise, all data will be saved into /tmp0/1/m4kc.

Screenshots

What this actually looks like.

Languages

C 98.5%

Objective-C 0.5%

M4 0.4%

Shell 0.3%

CMake 0.1%