Tags
Creators
Details
1.3.3
Compatibility
Changes
Added Wire Cutter Function
Custom wire properties added to Grid Engineering Custom wires can now be added through datapacks or KubeJS. Available properties: - name The display name of the wire. Used in item names, Jade, and tooltips. - voltage The maximum voltage tier the wire can handle. Examples: LV, MV, HV, SHV, CHV If voltage values are changed in the config, custom wires using tier names will automatically use the updated values. - base_amps / .baseAmps() The amperage capacity of the 1mm version of the wire. Larger wire thicknesses automatically multiply this value. Example: if base_amps is 4: - 1mm: 4A - 2mm: 8A - 4mm: 16A - 8mm: 32A - 16mm: 64A - loss_per_meter_per_amp_ppm / .lossPerMeterPerAmpPpm() Power loss per block per ampere, measured in ppm. - 10000 = 1% - 5000 = 0.5% - 2000 = 0.2% - color / .color() The render tint color of the wire. Examples: - "0xff00ff" - "#ff00ff" - 0xff00ff - only_one / .onlyOne() / .onlyone() By default, custom wires generate 1mm, 2mm, 4mm, 8mm, and 16mm variants. This option makes the wire generate only one thickness variant. - mm / .mm() Sets the thickness used when only_one is enabled. Valid values: 1, 2, 4, 8, 16 - coated / .coated() Also generates coated versions of the custom wire. Coated wires render thicker and use the normal coated-wire loss behavior. KubeJS example: js GEEvent.wire(event => { event.create("example_wire") .name("Example Wire") .voltage("HV") .baseAmps(8) .lossPerMeterPerAmpPpm(2500) .color(0xff55aa) .coated() }) Datapack JSON example: json { "name": "Example Wire", "voltage": "HV", "base_amps": 8, "loss_per_meter_per_amp_ppm": 2500, "color": "0xff55aa", "coated": true }
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:JxMiHpWK:ukpCq8MT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JxMiHpWK:ukpCq8MT"
}

