Links
Tags
Creators
Details
Licensed MIT
Published 5 months ago
Updated last month
All versions
1.1.0
Release
1.1.0last month 34
Compatibility
Minecraft: Java Edition
26.2
26.1.2
Platform
Fabric
Supported environments
Client and server
Required content
Changes
Changelog
All notable changes to CzechCraft are documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
Unreleased
1.1.0 - 2026-09-06
Added
- Minecraft 26.2 support. A single jar now covers 26.1.2 and 26.2 — no second download. Verified by running the published jar as a real mod on a dedicated server for each version: the item registers and resolves via
give, and an A/B recipe count (mod present vs absent) confirms the recipe and its advancement load on both.
Fixed
- Modrinth no longer advertises versions the mod rejects. 26.1 and 26.1.1 were listed but never worked — the declared range has always been
>=26.1.2, so the loader refused them. They are removed from the listing rather than silently handed a jar that cannot start. - Declared Fabric API dependency tightened from
*(any version at all) to a real minimum.
Changed
- The supported Minecraft range is now
minecraft_supported_rangeingradle.properties, separate fromminecraft_version(the compile target). Conflating the two produced the original "requires 26.1.2 but 26.2 is present" report. The Modrinth game-version list is generated from the same property, andSupportedVersionsTestasserts — using Fabric Loader's ownVersionPredicate— that everything advertised is actually accepted, and that versions known to break stay excluded.
Not supported
- Minecraft 26.3. The Java code runs there, but 26.3 renamed the
recipe_unlockedadvancement trigger field (recipe→recipes), so our generated advancement fails to parse and the game refuses to load its datapacks at all. Supporting 26.3 requires regenerating datagen against it, not widening a range.
Fixed
release.ymlnow retries the Modrinth version-ID lookup instead of failing on the first miss. Modrinth is not read-your-writes consistent: during the 1.0.1 release the lookup ran ~300 ms after upload, found nothing, and aborted the workflow after the jar was already public — skipping GitHub Release creation.release.ymlrefuses to publish a version number that already exists on Modrinth. Re-running a release previously re-uploaded silently, which is how 1.0.0 came to be listed twice.
1.0.1 - 2026-09-06
Fixed
- The mod now actually loads. v1.0.0 shipped without any of the
commonmodule's classes (CzechCraft,RegistryHelper,ModItems,ModItemGroups,FoodItems), so Fabric crashed withNoClassDefFoundErroron the first line ofCzechCraftFabric.onInitialize()— on every Minecraft version, for every player.implementation project(":common")is a compile/runtime dependency and does not bundle classes into the jar; the loader jar now includes common's compiled output.
Added
JarPackagingTest— verifies the built artifact contains every class compiled intocommon, and that eachcz.czechcraft.*class links using the jar alone. Runs on everybuild, so a release can no longer ship a jar that cannot start. The existing checks all resolvedcommonthrough the dev classpath and were structurally blind to this.
1.0.0 - 2026-04-25
Added
- Rohlík — Czech bread roll. Crafted from 2 wheat placed horizontally adjacent on a crafting table or 2×2 inventory grid. Restores 2 hunger drumsticks (nutrition 4, saturation modifier 0.3).
- CzechCraft creative tab containing all CzechCraft items.
- English (
en_us) and Czech (cs_cz) translations. - Fabric loader support for Minecraft 26.1.x (Java 25, Mojang Mappings).
- MultiLoader-Template architecture:
common/module compiles against vanilla Minecraft only;fabric/is a thin entry layer. Future loader modules (NeoForge planned for v3) drop in without touchingcommon/source. - GitHub Actions:
build.ymlruns Spotless + tests + datagen verification on every push/PR;release.ymlpublishes to Modrinth and creates a GitHub Release onv*tags.
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:WVnPxPsR:hvlCIDNR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WVnPxPsR:hvlCIDNR"
}

