All versions
1.0.0
Release
MekaCrafter 1.0.0 - NeoForge 1.21.15 days ago 62
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
MekaCrafter 1.0.0 for NeoForge 1.21.1
Requirements
- Minecraft 1.21.1, NeoForge 21.1.100 or newer, Java 21
- Mekanism 10.7.19 or newer
- Mekanism Extras (optional)
Changes
- First release.
- Autocrafting machine bound to a QIO frequency: plans the full recipe tree from base materials and crafts every intermediate step, storing the result back into the QIO.
- Crafting table and stonecutter recipes.
- Complete and precise missing-materials list in a pinnable Mekanism-style window. Each entry shows what it is needed for and whether it must be made in another machine (control circuits, alloys...).
- Item variants in the QIO (charged energy tablets, renamed items...) count as stock.
- Energy model like a Mekanism machine: configurable usage per tick (400 FE/t by default), energy upgrades, pause and resume without losing progress or materials.
- Job queue with intermediate sub-jobs, progress bar with total energy and time left, cancel and clear buttons.
- Planning runs off the server thread, so big recipe trees do not freeze the tick.
- Animated machine model with active LED, Minecraft-style buttons, energy gauge and energy tab.
- Settings in
config/mekacrafter-server.toml: energy usage, storage, ticks per craft, job overhead.
Notes
- Only crafting table and stonecutter recipes are automated. Items made in Mekanism machines are listed as materials to supply.
- Binding needs a Portable QIO Dashboard set to your frequency; there is no frequency selector in the GUI yet.
- This replaces QIOAutocrafter 0.2.0 (Forge 1.20.1), which is no longer maintained.
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:JWRNtiLD:pfzmR0rM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JWRNtiLD:pfzmR0rM"
}

