Differences

This shows you the differences between two versions of the page.

--- tutorial:1.15:jigsaw [2020/08/14 18:10] – ↷ Page moved from tutorial:jigsaw to tutorial:1.15:jigsaw emmanuelmess
+++ tutorial:1.15:jigsaw [2021/12/28 19:44] (current) – simplify link to code banana
@@ Line 2: / Line 2: @@
 Jigsaws are good for advanced structures such as dungeons & villages, and allow you to spend more time on actually building content vs. messing with procedural generation code.
-A repository with finished code can be found [[https://github.com/Draylar/jigsaw-example-mod|here for 1.14]], [[https://github.com/Draylar/jigsaw-example-mod/tree/1.15|here for 1.15]], [[https://github.com/EmmanuelMess/jigsaw-example-mod/tree/1.16.1|here for 1.16]]
+A repository with finished code can be found [[https://github.com/Draylar/jigsaw-example-mod|here]]. Switch branches to select a version from 1.14 to 1.16.
-===== Creating a StructureFeature (for 1.15) =====
+===== Creating a StructureFeature =====
 A ''StructureFeature'' is an advanced ''Feature'': it keeps track of its location and bounds, and also has the ability to generate itself from a structure file((While you can generate your StructureFeature from a ''.nbt'' file, most vanilla StructureFeatures simply override the ''generate'' method inside their given Piece class.)). If it helps, you can think of it as a ''Structure'' + ''Feature''. We'll need to create one for our jigsaw generated structure. To start, create a class that extends ''StructureFeature<DefaultFeatureConfig>''((AbstractTempleFeature is another option. It automatically spaces out the structures similar to the existing temples-- this logic is also used by villages.)). Feature naming convention is "structure name" + "Feature"; a few vanilla examples are ''EndCityFeature'', ''OceanRuinFeature'', and ''VillageFeature''.