
Buildprint - Schematics & Printer (Litematica Alternative)
Load any schematic as a ghost in your world, see what's missing, and build it with easy place or the printer. Opens .litematic, .schem, .schematic, .nbt and Axiom .bp. A client-side alternative to Litematica.
Tags
Creators
Details
0.1.10+26.x
Compatibility
Required content
Changes
Servers with several worlds
- Builds only show in the world you placed them in. On servers with a lobby, survival and creative world behind one address, a build no longer shows up in all of them. Buildprint tells the worlds apart by their bedrock. In another world the build is hidden, not removed, and shows as "(other world)" in the Loaded list.
- Works in the overworld and the nether. Not in the End, superflat or void worlds.
- Builds from before this update pick it up once you place or move them again.
- Can be turned off under Schematics → "World fingerprinting".
Shared builds
- Several builds in one session. "Build this together…" lets you pick more than one build, or add builds to a session you already have.
- Each session has its own colour in the Loaded list, so you can see which builds belong where.
- Block swaps are shared with everyone in the session. Only admins can swap.
- Choose how a swapped block is placed, like top or bottom slabs, or which way stairs face.
- Admins can manage a session from voxelsprout.com: swap blocks, remove builds and make others admin. Sign in with the account you linked in the game.
- The live page shows each build in a session separately.
- Removing one build no longer ends the whole session.
- You get a chat message when a build is removed from a session, with who removed it.
- If your sign-in isn't accepted when starting a session, you can sign in again or start as a guest.
Optional dependencies
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:pa8th8fX:fI3IEnbY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pa8th8fX:fI3IEnbY"
}
