Ported version of Minecraft Legacy Console edition to other systems
4JCraft is a modified version of the Minecraft Console Legacy Edition aimed on porting old Minecraft to different platforms (such as Linux, Android, Emscripten, etc.) and refactoring the codebase to improve organization and use modern C++ features.
Join our community:
At the moment, we're aiming to support the following platforms:
- Linux (~85%, rough estimate)
- Emscripten (not started)
- macOS (not started)
- iOS (not started)
- Android (not started)
All efforts are focused towards a native Linux port, OpenGL rendering pipeline, and modernizing the existing LCE codebase/tooling to make future platform ports easier.
Windows64and other platforms originally supported by LCE are currently unsupported, since the original Visual Studio tooling has been stripped from this repository and replaced with our own.
Install the following packages before building:
apt install \
build-essential cmake \
libglfw3-dev libgl-dev libglu1-mesa-dev \
libopenal-dev libvorbis-dev \
libpng-dev libpthread-stubs0-devpacman -Syu base-devel gcc pkgconf cmake glfw mesa openal libvorbis gludnf install @development-tools cmake glfw-devel mesa-libGL-devel mesa-libGLU-devel openal-soft-devel libvorbis-devel libpng-devel openssl-develIf you don't want to deal with installing dependencies, you can use the included devcontainer. Open the project in VS Code with the Dev Containers extension and it will set everything up for you - GCC 15, Meson, Ninja, lld, and all the libraries.
Alternatively, you can build and use the container manually:
docker build -t 4jcraft-dev .devcontainer/
docker run -it -v $(pwd):/workspaces/4jcraft -w /workspaces/4jcraft 4jcraft-dev bashThis project uses the Meson build system (with Ninja).
Important
If you are using GCC, then GCC 15 or newer is currently required to build this project. Ubuntu installations in particular may have older versions preinstalled, so verify your compiler version with gcc --version.
Follow this Quickstart guide for installing or building Meson and Ninja on your respective distro.
# 1. Configure a build directory (we'll name it `build`)
meson setup build
# 2. Compile the project
meson compile -C buildTip
For the fastest compilation speeds, you may want to use the compilers and linkers provided by an LLVM toolchain (clang/lld) over your system compiler and linker. To do this, install clang and lld, and configure your build using the llvm_native.txt nativescript in /scripts:
meson setup --native-file ./scripts/llvm_native.txt build...or if you've already configured a build directory:
meson setup --native-file ./scripts/llvm_native.txt build --reconfigureThe binary is output to:
./build/Minecraft.Client/Minecraft.Client
To perform a clean compilation:
meson compile --clean -C build...or to reconfigure an existing build directory:
meson setup build --reconfigure ...or to hard reset the build directory:
rm -rf ./build
meson setup buildIn order to run the compiled binary, you have a compiled copy of the game's assets in your current working directory. These assets are automatically copied to the Minecraft.Client folder in your build directory. To run the game, your current working directory must be in this folder.
cd build/Minecraft.Client
./Minecraft.ClientSubmitting code to this repository authored by generative AI tools (LLMs, agentic coding tools, etc...) is strictly forbidden (see CONTRIBUTING.md). Pull requests that are clearly vibe-coded or written by an LLM will be closed. Contributors are expected to both fully understand the code that they write and have the necessary skills to maintain it.