CommandStructures

<location> – Where to spawn the structure. Can do ~ ~ ~ to spawn it where you currently are or ~50 ~ ~ to spawn it 50 blocks away from you.

<startpoolresourcelocation> -  The path to the template pool to use to start the structure gen from. For plains vanilla village, this would be "minecraft:village/plains/town_centers" which is the start pool for villages. You can choose other pools for testing purposes. This is a required argument. The rest of the arguments past this one are optional.

<depth> – How many pieces outward from the starting piece should the jigsaw structure generate. Think of it like how long a branch should go in length. Not how many pieces in the structure total. Villages are 6 in depth.

<heightmapsnap> – Whether the structure should generate at top land or should spawn where the player is.

<legacyboundingboxrule> – Special internal rule that fiddles with bounding boxes of the pieces. This is required to be true for villages to generate properly. All other structures should have this be false.

<disableprocessors> – Whether structure processors should be turned off for this structure generation or not. Processors are often used to randomized a structure's block or replace blocks based on conditions like how village roads turns into planks when it goes into water.

<randomseed> – Use this and pass in a seed if you want to keep generating the same structure layout over and over every time you run the command anywhere. Great for testing to see if you fixed why a piece wasn't spawning in your structure.

 <resourcelocationpath> – The path to search under for all nbt pieces to spawn in a grid. This command can target a single nbt piece as well. This is the only required argument. All other arguments are optional.

<location> – Where to start placing the pieces down at. ~ ~ ~ is the default which is where the player is standing. 

<savepieces> – Whether to auto save every nbt piece spawned into the "generated" folder in the world's save folder.

<floorblock> – What block to place on the floor that the nbt pieces will sit on. This is usually Barrier blocks or Stone.

<fillerblock> – What block to place to clear the area for the nbt piece. Common blocks chosen here are Air or Structure Void.

<rowlength> – How many nbt pieces should be placed per row before the next row of pieces is started.

 <configuredfeatureresourcelocation> – The resourcelocation of the configuredfeature to spawn. Do note, some features have internal checks to know if a spot is valid such as Desert Wells requiring to be placed on sand.

<location> – Where to spawn the configuredfeature at.

 <placedfeatureresourcelocation> -  The resourcelocation of the placedfeature to spawn. Do note, some placedfeatures have internal checks to know if a spot is valid or rarity placements. For example, Desert Wells have a 1/1000 rarity placement so you could be doing this command around a 1000 times before a Desert Well decides to spawn.

<location> – Where to spawn the placedfeature at. NOTE: to better simulate worldgen, the location here will pass the bottommost corner position of the chunk it is in to the placedfeature. So using this command is like normal worldgen spawning without the biome checking being done. If your placedfeature has a "minecraft:biome" placement check, it will be ignored to help with debugging easier without needing to be in the right biome.