Overview
This project is in a heavy pre-production state. All information on this wiki is subject to change!
Please leave any feedback at https://discord.gg/archipelago
(find us in
#minecraft in the Minecraft Client 2.0 thread).
Summary
This is a total rewrite of the original Archipelago client for Minecraft. The goal is to provide a core foundation of tools for writing Minecraft vanilla and modpack implementations, focusing on futureproof maintainability, as well as modularity and extendability.
Currently, this project is in a planning/pre-production phase, with no release date.
Priority is currently being placed on one extendable implementation for NeoForge 1.21.8. Backports to older versions and loaders will be created by request later down the line.
Feel free to contact us with any feedback you might have. If you'd like to contribute, definitely reach out.
Also, feel free to check out the Archipelago Minecraft GitHub organization.
Goals
Extendability
The APWorld and the Minecraft Archipelago client are designed to be completely modular.
Grab the APWorld template, export your modpack's raw data, and pick which batteries to include.
The Minecraft client is versatile and built to be portable.
See Architecture Overview.
Robust Tooling
An .apmcbundle patch with mod files generated by the APWorld,
for running headless servers and patching local instances.
See Archipelago Architecture.
KubeJS support integrates Archipelago with an expressive, easy-to-use JavaScript API.
See KubeJS.
One extendable core Minecraft client,
tailored for portability between modpacks for different mod loaders and game versions.
See Client Architecture.
A featureful vanilla implementation that keeps parity with the original randomizer,
also adding many new features and fixing specific gameplay problems.
See Roadmap.
Click an article on the sidebar for more information.