
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.27+26.3
Compatibility
Required content
Changes
Changed
- BuildPrint's cards keep one column under a minimap in the top left, and the look-at card at the top moves aside before it moves down. On a small screen the second card used to go beside the map, towards the middle, and the look-at card dropped down instead of shifting a little to the side.
Fixed
- Easy place keeps working after you die, change dimension or rejoin a server. It could stop placing anything for as long as you'd been playing before, and the printer could skip blocks the same way.
- A build no longer stays hidden after coming back from another dimension. BuildPrint could take it for a build from another world while the area was still loading, and only showed it again after a rejoin. It now waits for the whole area, and looks again as the ground under the build loads.
- Raw materials go all the way back, through recipes with several ingredients and through the furnace. Sea lanterns become shards and crystals, concrete sand and gravel, glass sand, stone cobblestone; chests and other blocks that take any wood count the wood your build uses.
- On a server, raw materials go as far back as in single-player.
- With layer view on, the look-at card only names blocks in the layers you can see. It could say a block was missing from a layer above or below, which you couldn't see.
- Opening BuildPrint's settings from the title screen no longer crashes the game. It happened from Mod Menu or the mod list before joining a world, since 0.1.23.
- Text and switches in BuildPrint's screens stay readable with dark or light GUI resource packs. On the Minecraft look, titles and labels follow the pack's panels and buttons, so they no longer vanish on a dark pack such as Sleek UI; with vanilla's textures nothing changes.
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:6ehzsCHO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pa8th8fX:6ehzsCHO"
}
