Links
Tags
Creators
Details
3.0.2
Compatibility
Changes
Voltex 3.0.2 for NeoForge 1.21.1
First release on NeoForge 1.21.1. The content is the same as Voltex 3.0.2 for Forge 1.20.1: every machine, multiblock, the heat network, the cryo chamber, the electromagnet, nanites, ME ports and the in-game guide.
- Worlds from 1.20.1 do not carry over. Minecraft 1.21 changed how items and blocks store their data, so tool charge, machine contents and other saved values would be lost. Start a new world for 1.21.1, and keep a backup if you try an old one anyway.
- Requires NeoForge 21.1.259 or newer.
- Optional integrations: JEI, Jade, Applied Energistics 2 (ME ports) and KubeJS 7.
For pack makers
- Tags follow the 1.21
c:convention (c:ingots/copper,c:dusts/iron, ...) instead offorge:. - KubeJS recipe syntax is the same as on 1.20.1, every Voltex machine has its schema.
- Fluids in datapack recipes use the 1.21 format
{"id": "...", "amount": 1000}. The old{"fluid": "...", "amount": 1000}still loads.
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:5uzIB1sd:5V3O7R10"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5uzIB1sd:5V3O7R10"
}

