All versions
2.2.0
Release
Core Companion 2.2.0last month 527
Compatibility
Minecraft: Java Edition
1.21.8
Platform
Fabric
Supported environments
Client and server
Changes
Core Companion 2.2
This release makes Core Companion work on a fresh machine with nothing pre-installed, and takes the guesswork out of choosing a local AI model.
✨ Highlights
- First-run setup that just works. Install the mod, join a world, and it downloads and prepares the AI for you — no terminal, no manual model commands.
- Automatic, hardware-aware model selection. It checks the memory your machine can actually give an AI model — dedicated GPU VRAM, Apple-Silicon unified memory, or system RAM — reserves a few GB for Minecraft itself so nothing stutters, and picks the best-fitting local model (lightweight, balanced, or largest). It tells you which one it chose for your specs.
- A setup that looks intentional. No filesystem paths dumped into chat — just a clean progress bar above your hotbar, and the look/start-mode questions only appear after the model finishes downloading.
- She never spawns unable to talk. Your companion only arrives once her model is downloaded and warmed up, so her first reply is instant instead of a long cold-load stall.
- Helpful when the AI backend is missing. If Ollama isn't installed or running, you get a clear in-game "install Ollama" guide instead of a cryptic error — and following, mining, and building all keep working without it.
🛠 Fixes & polish
- Fixed first-join chat failures (
ClosedChannelException) caused by the AI client being rebuilt mid-setup. - The download progress bar now stays on screen and updates smoothly across the whole multi-GB download, instead of flashing once and vanishing.
- Dropped connections during a model download now auto-resume and retry instead of failing the whole setup.
- Default companion name is now a neutral "Companion" until you name her — and renaming her no longer leaves a stale name baked into her personality.
- Better server-side diagnostics when a model download or warm-up fails.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:RGZDEU0f:QnF4TiiA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RGZDEU0f:QnF4TiiA"
}

