Instance workflows
Create, inspect, import, export, repair and manage Minecraft instances.
Built as a reusable Core
The project keeps GUI concerns outside the Core and exposes a stable consumer boundary through mcw_core, mcw_core.rpc (JSON-RPC 2.0), and granular mcw_core.api.* modules.
Loader support
Vanilla and mod-loader oriented workflows through Core services.
Java & launch
Runtime selection, launch preparation, diagnostics and launch orchestration.
Content ecosystem
Modrinth, CurseForge, modpack and content-management integrations.
Download
Release assets are resolved automatically from GitHub when available. Source ZIP always falls back to the current main branch.
Python wheel
Use the exact release wheel for local installation or launcher integration.
mcw_core-1.8.0-py3-none-any.whl
Full source archive
Use the release full-source bundle when available, otherwise download the latest repository source.
MCW-Core-v1.8.0-full-source.zip
Docs & API reference
Read Markdown directly from the Core repository below. If a docs ZIP exists in a release, its download button appears automatically.
docs/ · README.md · RELEASE.md
Installation
Pick the workflow that matches how you consume MCW Core.
python -m pip install ./mcw_core-1.8.0-py3-none-any.whl
Download the wheel from the latest release first. A virtual environment is recommended.
git clone https://github.com/mahiru7229/mcw-launcher-core.git cd mcw-launcher-core python -m venv .venv python -m pip install -e '.[dev]' python -m pytest test -q
Activate the venv before installing. On Windows PowerShell use .\.venv\Scripts\Activate.ps1.
mcw-core-launch --root ./mcw-data --list mcw-core-rpc --stdio mcw-core-rpc --http --port 38475
The CLI can list/launch instances or start the headless JSON-RPC 2.0 daemon without the MCW Launcher GUI.
Documentation reader
Markdown files are discovered from mahiru7229/mcw-launcher-core and rendered here. Commit new docs to the Core repo and this reader picks them up automatically.
Select a document
Loading documentation…
FAQ
Quick notes about downloads, docs and background customization.
How does the docs reader stay updated?
It queries the public Core repository tree, finds Markdown files under docs/ plus key root docs, then fetches and renders the selected file from the repository's main branch.
How do I change this Core page background?
Add or replace mcw_core/assets/background.jpg in this website repository. If the file exists, it is used automatically. If it is absent or cannot load, the original gradient background is kept. There is no upload button on the website.
How do I change the main card background?
Add assets/img/bg/custom_bg.jpg. If it exists it overrides the card background; otherwise assets/img/bg/user_bg.jpg remains the default.
Where should release downloads live?
The page tries GitHub Releases first. A wheel, full-source archive, and docs bundle are matched by filename. If no matching release asset is available, source download falls back to the repository ZIP and other buttons direct users to Releases or live docs.