All versions
1.1-7.3_04
Release
Blueprints BTA 1.1-7.3_046 months ago 61
Compatibility
Minecraft: Java Edition
b1.7.3
Platform
BTA (Babric)
Supported environments
Client-side
Changes
ADDITIONS
Configurable "Interaction Mode" keybind (default X) and button in the Blueprints menu:
- Fulfill: Right-clicking a hologram with a block in hand will replace the hologram
- Ignore: Clicks pass through holograms, allowing you to place/break blocks through them
CHANGES
- Non-placeable items (e.g. crafting materials, food, tools) no longer appear in the design mode item page
- Replaceable blocks (e.g. long grass, snow layers, ferns) no longer block the rendering of holograms when they occupy the same space
FIXED BUGS
- [MULTIPLAYER/SINGLEPLAYER] Pressing Ctrl (flight toggle) at the same time as exiting design mode causes the player to fly in survival mode
- [MULTIPLAYER/SINGLEPLAYER] Moving blueprints inside solid blocks produces x-ray glitch which allows you to see caves
- [MULTIPLAYER/SINGLEPLAYER] The design mode camera can collide with the survival player, allowing you to push yourself
- [MULTIPLAYER/SINGLEPLAYER] Hologram blocks can suffocate the player while rendered in design mode
- [MULTIPLAYER/SINGLEPLAYER] The survival player is pushed out of hologram blocks while they're rendered in design mode
- [MULTIPLAYER/SINGLEPLAYER] Cobweb holograms slow down the player and allow illegal movement
- [MULTIPLAYER/SINGLEPLAYER] Liquid holograms allow player interaction, including floating (another illegal movement vector for the server)
- [MULTIPLAYER/SINGLEPLAYER] The placement of positional/orientable blocks like logs, stairs and slabs in design mode is inconsistent with vanilla placement mechanics
- [MULTIPLAYER/SINGLEPLAYER] The fulfilment of positional/orientable blocks is also broken, and often doesn't render the actual state until we relog
- [MULTIPLAYER/SINGLEPLAYER] Holograms in the same space as replaceable blocks (e.g. long grass, snow layers, ferns) don't fulfil with the right orientation
- [MULTIPLAYER/SINGLEPLAYER] Hologram blocks don't reappear if they were correctly fulfilled and then the block is removed
- [MULTIPLAYER/SINGLEPLAYER] Typing in the design mode item search bar passes movement through to the survival player
- [MULTIPLAYER/SINGLEPLAYER] Grass/long grass/leaves don't render with foliage/biome colour
- [MULTIPLAYER/SINGLEPLAYER] Hologram redstone dust doesn't render with the correct (red) colour
- [MULTIPLAYER/SINGLEPLAYER] Holograms cause dark AO shadows against real blocks
- [MULTIPLAYER/SINGLEPLAYER] Fulfilling holograms can cause nearby holograms to have increased opacity
- [MULTIPLAYER/SINGLEPLAYER] Blocks with transparency (e.g. glass, leaves, etc.) don't properly cull faces when placed as holograms
- [MULTIPLAYER/SINGLEPLAYER] Blocks with transparency (e.g. glass, leaves, etc.) don't render with the configured opacity when placed as holograms
- [SINGLEPLAYER] After touching a nether portal block in design mode, you will instantly teleport to the nether the next time you press Ctrl (flight toggle)
- [SINGLEPLAYER] Items can be picked up in design mode
- [SINGLEPLAYER] Gravity-affected blocks like sand and gravel don't fall when placed above a hologram, and if they do fall into a hologram, they break and drop as items
- [SINGLEPLAYER] Hologram blocks can be broken by real TNT explosions
- [SINGLEPLAYER] Hologram TNT can be ignited by a real explosion, causing another real explosion
- [SINGLEPLAYER] Hologram blocks drop real items when broken by unintended means (e.g. explosions, pistons, etc.)
- [SINGLEPLAYER] Hologram blocks can be broken by pistons, which also causes them to drop as real items
- [SINGLEPLAYER] "Supported" hologram blocks (e.g. torches, redstone dust) will break and drop as real items if their supporting block is broken
- [SINGLEPLAYER] Fire and spike holograms damage mobs and the survival mode player
- [SINGLEPLAYER] TNT placed in design mode can be ignited by various means and cause real explosions
- [SINGLEPLAYER] Hologram dirt/grass blocks become real farmland when tilled with a hoe in survival mode
- [SINGLEPLAYER] Redstone placed in design mode can be powered by real redstone
- [SINGLEPLAYER] Real TNT blocks can be ignited by redstone placed in design mode, causing real explosions
- [SINGLEPLAYER] Real blocks can be placed on hologram blocks, allowing for illegal placements
- [SINGLEPLAYER] Buckets used in design mode can pickup real liquids
- [SINGLEPLAYER] Jukebox holograms can have discs put in them, which can then be removed, creating a real disc item
- [SINGLEPLAYER] Cake and pumpkin pie holograms can be eaten in survival mode, which heals the player
- [SINGLEPLAYER] Fishing rods can be used in design mode when right-clicking blocks, which allows you to catch real fish
- [SINGLEPLAYER] Hologram beds can be slept in by the player in survival mode
- [SINGLEPLAYER] Hologram seats can be sat in by the player in survival mode
- [SINGLEPLAYER] Tile entity holograms can have their inventories accessed by the player in survival mode
- [SINGLEPLAYER] Bows and hand cannons can be used in design mode, which can cause them to shoot real arrows and explosives
- [SINGLEPLAYER] Summoning Wand can be used in design mode, which allows you to spawn real mobs
- [SINGLEPLAYER] Ice holograms can melt and create real water blocks
- [SINGLEPLAYER] Snowballs and eggs can be thrown in design mode (which can create real chickens)
- [SINGLEPLAYER] Right-clicking a hologram of a gold mesh block with an item in survival mode crashes the game
- [SINGLEPLAYER] Blocks with changeable stats (doors, trapdoors, levers, buttons, braziers, repeaters etc.) can be placed as holograms and then have their state changed in survival, which also then allows them to be broken and dropped as real items
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:po1RraSI:Der9mpk0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:po1RraSI:Der9mpk0"
}

