
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.19+26.x
Compatibility
Required content
Changes
Released as a beta: a lot changed in this one. If something broke for you, please report it.
Added
- A smaller build status panel. It switches to a one-line view while you place blocks and back to the full panel when you stop. H switches between Auto, Full, Compact and Hidden; the new HUD tab in the settings sets where it sits and how big it is.
- A walkthrough for new players, with small live scenes for the basics.
/buildprint onboardingshows it again. - Selection commands.
/buildprint pos1,pos2,expand,save <name>and more let you select and save from chat./buildprint load <file>loads a schematic. - See through solid blocks, a setting under Ghost appearance. Off by default.
- More of the API for mod developers.
Changed
- The name is written BuildPrint now. Commands and your saved builds stay the same.
/buildprinthelp is clickable. The debug tools moved to/buildprintdebug.- Big builds appear sooner and run smoother. The ghost is prepared on spare CPU cores, builds spread over a large area draw much faster, and very big builds no longer freeze the game when they appear.
Fixed
- The next-block marker and the Extra view's purple boxes show with a shader pack.
- No more crash or long stutters with dense builds full of fences, glass panes, plants or redstone.
- See-through blocks like leaves and glass draw in the right order across a whole build.
- Layer view and the Mistakes view keep occlusion culling.
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:RJ3uTCda"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pa8th8fX:RJ3uTCda"
}
