Tags
Creators
Details
Licensed Apache-2.0
Published 11 months ago
Updated 4 months ago
All versions
fabric-1.20.1-2.0.0
Release
Buildstone Toolkit 2.0.0 [Fabric 1.20.1]4 months ago 14
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Create compat:
- Added schematic support. If a proxy's target is within the schematic's bounding box, its position will be saved and loaded via a relative offset.
- This means that you can safely save schematics of entire redstone systems without the proxy targets breaking.
- Proxies targeting outside the bounding box will still save their targets in world space, which means you can safely copy stable "receiver" systems.
- Proxy targets follow contraption assembly/disassembly. This means you can "move" a target using create contraptions.
- Even unloaded proxies!
Sable compat:
- Proxies can now target into and out of sublevels.
- Proxy targets (loaded or unloaded) also properly move into the sublevels on assembly.
- Even unloaded proxies!
- If you don't care for the technical jargon, this essentially means that most things you can imagine should work now work.
- Proxy targets (loaded or unloaded) also properly move into the sublevels on assembly.
Features:
- Redstone proxies have been upgraded. They now have two modes:
- Read and Write (You can switch between them by smacking the proxy with the tuner).
- Additionally, they can target a specific face instead of the whole block, allowing more precise control.
- If you select a block with the Tuner then Shift + Scroll, you can shift your selection towards/away from you. Useful when your contraptions are compact.
- Proxy targets can be stored via relative offset in NBT. This means structures/worldgen can properly use them now!
Bugs/Performance
- Made mixins less invasive by using modern MixinExtras features, improving compatibility with other mods.
- Improved performance overall for all systems (redstone, rendering, etc.)
Old worlds
- Won't break, and migration is automatic as you load in the proxies.
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:m5tBeIGD:4IMtRpCn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:m5tBeIGD:4IMtRpCn"
}

