Tags
Creators
Details
5.1.5
Compatibility
Changes
v5.1.5 (2026-08-17) — Enchant Crafting, Jetpacks, Infinite Generators, Ender Links
Four new gameplay modules, drawn recipe images, a Data Handler that can edit every property it shows, and two electric transport bugs that had been quietly breaking wire runs.
Supported versions: 1.21.9 – 26.2 (data pack formats 88 – 107).
New modules
- Enchant Crafting — sacrifice items on a vanilla
enchanting table for a small chance at an upgrade. Extensible through the
#ra_enchanting:recipesfunction tag. - Jetpacks — Iron and Infinite Iron upgrade kits that fit onto
any chestplate. Classic and hover flight, switched with
/trigger ra.jp.mode; hover holds station with a servo that reads your vertical speed and aims gravity against it./trigger ra.jp.powerswitches the whole thing off, and landing does it for you. - Infinite Generators — a crafted Generator Casing plus a Core gambled off an enchanting table build the Mineral, Nether and Poppy generators, which regrow their own material in front of themselves.
- Ender Links — vaults that link two places by channel for
items, fluids and EU, plus Teleport Anchors with a string id and a table of
fifteen targets, one per redstone strength. Item vaults are
sharedby default: the contents follow whoever walks up, since mirroring one stack into two barrels would give it two extraction points.
Tooling
- Recipe pictures are drawn from vanilla assets by
tools/recipe_renderinstead of being screenshotted, with blocks rendered from their real models. All 58 regenerated. - The Creative Data Handler builds its
rows from a registry and picks the editor from each value's actual type, so
properties it used to display but could not change — a wire's
transfer_rate, a tank'stier, an anchor's id — are editable, lists included.
Documentation
- The home page warned that redstone on the Boxer and Unboxer had become a lock and told players to remove the signal from existing builds. Both have always shipped running while powered — the inversion was a mid-v5.1.4 workaround, reverted in that same release. Following the warning would have broken working builds.
Fixed
- Electric charge only ever reached the first two blocks of a run: a node handed EU back to the neighbour that had just supplied it, and a transfer latch was never released. Charge now moves downhill only, half the gap at a time.
- A
enabledflag written as1rather than1bsilently disabled a whole wire run or pipe line. The runtime gates are tolerant now. - Poppy Generators planted nothing: 26.2 narrowed
#minecraft:dirt, which no longer contains grass blocks. - Block skins rendered black inside the block they cover.
- Eight multiblock library functions had never been committed, because the directory
they live in is called
build.
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:52z5jQjy:EQvnfwxe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:52z5jQjy:EQvnfwxe"
}

