Talk:Structure Block

Speculating that the structure block's blast resistance is the same as bedrock or obsidian
The structure block's blast resistance is probably the same thing as bedrock or obsidian. It's just a speculation, I'm not really sure that it is but it might be. RosalinaFan573 (talk) 18:41, 31 July 2015 (UTC)
 * Blew up one with some TNT. It's still there. Dittoslash (talk) 13:06, 12 August 2015 (UTC)
 * New (more reliable) test: ~300 TNT minecarts (in this) failed to blow up the new(?) Structure Block, obsidian, and bedrock. Dittoslash (talk) 06:25, 21 May 2016 (UTC)
 * Multiple explosions aren't cumulative; if one TNT isn't able to break a block, it can't be broken with any amount of TNT. -- Orthotopetalk 06:38, 21 May 2016 (UTC)
 * Use the command /summon Fireball ~ ~ ~ {ExplosionPower:100}} (or more than 100) to create a fire ball with a high explosion power and punch it into the direction of the structure block. Only that can destroy it. I didn't look at any wiki page (online with phone) to create the command, could please someone check if it's correct? Fabian42 (talk) 07:54, 21 May 2016 (UTC)
 * There's no point to continuing to speculate when people have looked at the code and determined the exact value. Anomie x (talk) 14:43, 21 May 2016 (UTC)

Where do structures save?
I have created (and saved) several structures, but I can't seem to find the file. I heard once that they would save in the "structures" folder in the world files, but I can't seem to find this folder. I have even searched the entire minecraft directory for one of my structures (using the search function), but still no luck. -- Luke18033 (talk) 00:31, 19 May 2016 (UTC)


 * Saving doesn't work on windows. See mcbug:102052. –Majr ᐸ Talk Contribs 07:31, 20 May 2016 (UTC)


 * Then why am I still able to load the structures in the same world, even after I quit and re-enter? The structures are saving somewhere, probably in the world folder, I just can't find it. -- Luke18033 (talk) 20:35, 20 May 2016 (UTC)


 * It's saved in memory until you close the game entirely; it will remain in memory if you only exit the world. Skylinerw (talk) 19:22, 20 May 2016 (UTC)


 * I'm pretty sure I've exited the game too, but idk. I'll have to test it later. -- Luke18033 (talk) 20:34, 20 May 2016 (UTC)


 * Just found that the structures aren't saved on relaunch. What was happening before is I was saving the structure again every time I opened the world. -- Luke18033 (talk) 22:55, 20 May 2016 (UTC)

"Blank" structure block?
The gallery, fourth from last image, says it shows a 'blank' structure block from 1.9 and then 1.10. Are these unused textures or something, or are they used in some circumstances? – Sealbudsman talk/contr 21:12, 21 May 2016 (UTC)


 * These are just the textures of structure blocks that are still in the Player's inventory but haven't been placed and assigned a mode yet. There currently isn't a way to place these "blank" structure blocks without using a custom resource pack, since it doesn't have a known data value. Superspace (talk) 07:19, 23 May 2016 (UTC)

Just a mess
This should say added in 1.9 OlidogMC (talk) 07:00, 23 May 2016 (UTC)
 * It's as clear as it can be. Did you even read the page? Fabian42 (talk) 09:46, 23 May 2016 (UTC)

Huge Discovery for Map Makers
So I just figured something out in the game, and I don't know if anyone else knows as well, but as far as I know I am the first to find out. The structure block can be activated by redstone. This means it can be used to create automated structures in custom maps. –Preceding unsigned comment was added by 121.217.2.180 (talk) at 3:07, 08 July 2016 (UTC). Please sign your posts with

Structure Blocks Save feature
In a lot of youtube videos I've seen, it's stated that only the Load option of structure blocks work with redstone. I have discovered that you can also Save structures with redstone, but only if the structure file already exists. There doesn't seem to be a good section to add this, so I'm just dropping this here. This is as of 1.10.2 72.224.250.183 10:10, 10 August 2016 (UTC)


 * Slight correction: saving via redstone signal only saves the structure to memory. It doesn't matter whether or not a file existed prior. Structures are only saved to file when using the interface. Skylinerw (talk) 10:32, 10 August 2016 (UTC)

Self-loading/Recursive Structures
Using redstone it is possible, with slight difficulty, to create self loading and even recursive structures. In other words, you can have a Load structure 'A' inside of structure 'A' and auto-load it via auto activated redstone. The cavit is that structures are loaded when their powered state switches from off to on. In other words, if you save it with redstone powering the load block, it will not auto-load itself.

The easiest solution is to use a observer block. the observer block always sends a pulse when it's initially loaded. Note however, that the observer block will not send another pulse after that even if you push load again, It must be replaced or updated.

Using this approach you can load several different structures from within your structure. This is useful when your structure has alot of a custom structure in it, such as a statue or red stone timings. And especially useful for oversized structures(larger than 32x32x32) since it allows you to load all the associated structures in one click.

Potential Pitfalls and Workarounds

Attempting to load many structures simultaneously may freeze low end PCs. Instead of calling a large group of load blocks at once from within one load block, try creating a load block chain or tree.

Most redstone triggers must be destroyed in order to reload contained structures. The best solution is to have the structure replace its trigger, command blocks erase the trigger, or use self replacing command blocks as the trigger. I prefer using a self replacing command block. Create by placing a command block down away from your structure and set it to chain, unconditional, always active (chain stops it from running now). Then type 'setblock ~ ~0 ~ minecraft:redstone_block'. cntrl + middle click it and place it next to all your load blocks, preferably (though not required) inside the region it will load into. Set the newly placed command blocks to impulse.

Embedded Load Block's structures will not be rotated/mirrored with the containing load block.

Self Recursive Structure

Be extra careful when creating recursive structures, it is very easy to make a runaway recursive structure loader which will recursively load the structure over 1,000 blocks per second (depending on computer speed/structure size). And once done its very hard to stop it. I recommend using command block triggers with a testfor condition, such as 'testfor @p[r=10]'. You can then follow the generated structure to generate more, You could also use the scoreboard and control the generation that way. (eg. testfor @p[r=30,gen_struct_min=1])

This works reasonably well when the load area and save area do not overlap. When they do overlap, I have had instances where the structure doesn't fully load. This can be used for recursive structures, useful for building staircases and towers spanning from the top to the bottom of the world. Multiple repeaters can be used to slow down generation, and you can break the load block before it is called to stop it. The torch can be replaced with a pressure plate or tripwire to make an trigger based expanding structure, for instance generating a bridge by flying through the tripwire. Similar method can be used for a piston-less/soundless moving path. With additional effort, the structure blocks and redstone can be auto-removed. For instance by loading the structure over it, or by deleting it with command blocks

This can probably be used in conjunction with command blocks and/or hoppers to create chunk loaders, load chunks dynamically, or (although its a really bad idea) even load chunks unconditionally with little effort.

!firefish5000 75.64.41.204 21:39, 17 February 2017 (UTC)