Minecraft Wiki talk:Projects/Structure Blueprints

Structure worlds
Sigma90 has discontinued his Ocean Monument project so I had an idea: Why don't we all share the worlds we found the structure in so if one of us discontinues one of our projects, another user can continue it? Or is there another way?


 * – Like, share the seed and coordinates? – Sealbudsman talk/contr 13:32, 3 July 2016 (UTC)


 * Wow, even I didn't think of that. That's perfect. Because you thought of the idea, you can start a list of the seeds and coords. | AndrewAB (talk) 13:37, 3 July 2016 (UTC)


 * Sure, the next time I work on this project I'll do that -- it might be me who does it first, it might be you, it might be a third person. – Sealbudsman talk/contr 20:19, 3 July 2016 (UTC)

Orientation
Hey all, can we agree on how to document orientable blocks? Here's what I've used (Taken from Igloo Structure): Chest = West -- Stairs = Flipped and facing Slab | AndrewAB (talk) 17:50, 8 July 2016 (UTC)

Here's one of my ideas. If you have 2 of the same blocks, you can distinguish between both using coords. A table (remove all for use):


 * In the End Ship page, I ended up just trying to use a verbal description. For instance:
 * The pillars are oriented front/back.
 * The stairs outside the ship are upside-down, facing the ship.
 * I think it might be a bit more intuitive than working with coordinates, though maybe it's just how I would build, and not everybody? – Sealbudsman talk/contr 21:18, 10 July 2016 (UTC)

End city
''"At the top of the End City, there is a gateway type of thing hanging in mid air and leading to nothing. What is it? Interesting fact: The End City is ~73 blocks tall!" -- User:AndrewAB

(moving this part of the discussion here from User talk: Anomie x)''
 * That gateway, I suppose it's open to interpretation, but I tend to think it's intended to look as if the flying ship is about to moor there, like a zeppelin on the top of the empire state building would have.
 * The end city is procedurally generated, each one has its own height.
 * As for reading the NBT file, I think you would need to

It may be possible to use a structure block to load those files, though you might want to thoroughly read the structure block page as to how. I couldn't be of any help there (just yet), it's new tech I haven't looked at. Good luck! – Sealbudsman talk/contr 17:41, 15 July 2016 (UTC)
 * 1) open it in a hex editor to read what numbers are represented in there,
 * 2) decipher what the numbers mean (we have pages on the wiki on NBT, for starters) and how they relate to the blocks layout
 * 3) hooray you've deciphered it.
 * 1) hooray you've deciphered it.

I'll just use the Structure Block. | AndrewAB (talk 17:45, 15 July 2016 (UTC)

Template for compacting and improving visualisation of blueprints
I created layered blueprint, which displays all the blueprint layers on top of one another, allowing the user to select which layer is displayed, with lower layers displayed partially transparent. –Majr ᐸ Talk Contribs 11:44, 17 July 2016 (UTC)


 * Very interesting. How about you make the lower layers shaded? | AndrewAB (talkAndrewAB.png 11:45, 17 July 2016 (UTC)


 * There's no way to apply styling to layers under the current one, only ones above (which is used to hide them). –Majr ᐸ Talk Contribs 12:13, 17 July 2016 (UTC)

Wow, Majr! Its better than I imagined! | AndrewAB (talk 12:25, 17 July 2016 (UTC)

Nether fortress
The page for the Nether Fortress is Lacking in info, with 3 of the 4 bridge designs, and the first terribly simplistic. also, the "living" half should be a separate tutorial. I suggest DanyBoi1986's video on the topic. UPDATE: I (numberguy6) just added the Cauldron Room blueprints for the Nether Fortress.


 * Problems solved. Danyboi's videos were very helpful, thanks!
 * Gregatron6000 (talk) 08:00, 17 January 2017 (UTC)

Woodland mansion
Sence all rooms in a mansion are diffrent, it would be a good idia to make a page for showing how to build it. –Preceding unsigned comment was added by 172.68.55.156 (talk) at 14:13, 11 November 2016 (UTC). Please sign your posts with


 * Great idea! I've started work on it!
 * Gregatron6000 (talk) 08:02, 17 January 2017 (UTC)

Woodland Mansion Structure
The mansion rooms can individually be spawned using structure blocks, but the mansion itself has a set size. This is like an ocean monument (set size and random rooms) with the convenience of an End city (structure blocks). Therefore, there should be a set seed for mansions, just like there is a set seed for ocean monuments, and the blueprint should cover the entire mansion. Preferably, this mansion should have at least one of every room.

Gregatron6000 (talk) 09:55, 29 December 2016 (UTC)
 * While there is a specific size, there are also specific rooms. To recreate this, the first thing you do would be to make the boundary in the appropriate size. Then, you can make rooms. The BlobsPaper.png 16:35, 29 December 2016 (UTC)


 * I was wrong. As I came to find out in one of my survival worlds, woodland mansions can have a different size. In the page, I'm going to have the blueprints for each room individually. Not sure what to do about the walls, hallways, or roof…
 * Gregatron6000 (talk) 08:06, 17 January 2017 (UTC)

Links from mainspace and (mostly) completed articles
I discovered a link to MCW:Projects/Structure Blueprints/Village from the mainspace article Village via a [ redirect]. The redirect was created when Village Blueprints was moved from the mainspace to this project. It didn't seem right to me to be linking from the user-facing wiki into what I call the "background machinery", so I searched for prior discussion but didn't find any. What I did find was that the redirect has been maintained by none other than, which made me question whether I'm being too strict about such links.

So I looked at all the other 51 blueprints in this project to see if any other links from mainspace articles exist. There is only one other, from Tutorials/Nether fortresses to MCW:Projects/Structure Blueprints/Nether Fortress. This raises 2 questions: Please discuss. --– Auldrick (talk &middot; contribs) 15:48, 17 October 2017 (UTC)
 * 1) Should these mainspace articles retain the links to the blueprint pages herein? If not, do we resolve it by
 * 2) removing the links, or
 * 3) moving the linked pages into the mainspace and fixing the redirects?
 * 4) What about all the other completed and mostly-complete blueprints? They seem like valuable information that's currently inaccessible to our readers. Shouldn't they be moved to the mainspace and linked appropriately?


 * "none other than" -- do I have some notoriety I am unaware of? : P
 * In what sense was I "maintaining" those links? I don't have any memory of favoring or disfavoring them, at this late date.
 * I'm treating them as main space content, and moved, though that would require probably some cleanup. I think getting the blueprints into the main space was always the intention of the project, but I may have just assumed that.
 * – Sealbudsman talk/contr 16:03, 17 October 2017 (UTC)


 * "None other than" because you're an administrator and second only to Majr in contributions, so it can be assumed you wouldn't make [ this edit] without noticing its oddness. --– Auldrick (talk &middot; contribs) 16:14, 17 October 2017 (UTC)


 * I'm not an administrator, but yeah, my edit count is up there. That edit was purely for the sake of fixing a double redirect, i.e. page A was redirecting to B which was redirecting to C, in which I edited A to instead point to C.  I didn't intend for that edit to imply taking a position on mainspace linking to the project. –  Sealbudsman talk/contr 17:21, 17 October 2017 (UTC)


 * First of all, the reason of movement of these mainspace articles to this project is due to the organization of blueprints. This means that mainspace redirects to their respective blueprint must not be retained, and must be deleted, because only less than 5 pages link to their mainspace redirects. This also means that they should not be moved to mainspace articles. Note: these are just my opinions! – Dentedharp90041tce 16:49, 17 October 2017 (UTC)


 * I'm assuming you don't mean they should never be moved to mainspace, since if that were the plan there would be no purpose in them existing. But I don't see why perfectly good articles that have been marked "Completed" on the project page should be held back from our readers for an indeterminate amount of time. What purpose does that serve? Organization doesn't explain it to me, since a list of links is organized the same whatever namespace they point to. --– Auldrick (talk &middot; contribs) 01:03, 18 October 2017 (UTC)


 * How about we put in an “extra notes” annotation in the structure mainspace articles that they correspond to? For example, the mainspace article on woodland mansions can have a link to the project on mansion blueprints. Maybe?


 * Gregatron6000 (talk) 05:31, 18 October 2017 (UTC)


 * So you're advocating adding more links from mainspace to the "background machinery"? I'm against such links. I think a normal reader who followed one could end up confused and lost. --– Auldrick (talk &middot; contribs) 15:41, 18 October 2017 (UTC)


 * Or, after the project has been completed, the blueprints will be moved to Tutorials/Structure Blueprints. – Dentedharp90041tce 11:31, 18 October 2017 (UTC)


 * And when will that be, another two years? Sequestering pages, especially completed pages, violates a core wiki principle and hides information from the people who need it. I'm fine with leaving them here if it serves some purpose important enough to override policy, but "due to the organization of blueprints" is vague and doesn't explain anything to me. Virtually all projects work from a list of links to pages in mainspace. Why should this one be different? --– Auldrick (talk &middot; contribs) 15:41, 18 October 2017 (UTC)