这个适用于 Neoforge、Forge、Fabric 和 Quilt 的实用模组非常适合任何希望创建自定义拼图结构(jigsaw structures)但想要快速生成这些结构或整齐排列所有 NBT 片段的模组开发者或数据包制作者。它还提供了一种生成配置化特性(configuredfeatures)和放置特性(placedfeatures)的方法,从而简化对这些特性的调试工作。
该模组的作用是创建了 /spawnstructure、/spawnpieces、/spawnfeature 和 /spawnplacedfeature 命令供你使用。这些命令的完整参数如下:
/spawnstructure <location> <startpoolresourcelocation> <depth> <heightmapsnap> <legacyboundingboxrule> <disableprocessors> <sendchunklightingpacket> <randomseed>
<location> - 结构的生成位置。可以使用 ~ ~ ~ 在当前所在位置生成,或使用 ~50 ~ ~ 在距离你 50 格的位置生成。
<startpoolresourcelocation> - 用于启动结构生成的模板池路径。例如,对于平原原版村庄,这将是 "minecraft:village/plains/town_centers",即村庄的起始池。你可以选择其他池以进行测试。这是唯一必需的参数。所有其他参数均为可选。
<depth> - 从起始片段向外延伸,拼图结构应生成多少层片段。可以将其理解为分支的长度,而不是结构中片段的总数。村庄的深度为 6。
<heightmapsnap> - 结构是否应在最高陆地表面生成,还是在玩家所在位置生成。
<legacyboundingboxrule> - 一个特殊的内部规则,用于调整片段的边界框。为了使村庄正确生成,此值必须为 true。其他所有结构都应将其设为 false。
<disableprocessors> - 是否在此结构生成过程中关闭结构处理器。处理器通常用于根据条件随机化结构的方块或替换方块,例如当道路进入水中时变为木板。
<sendchunklightingpacket> - 如果为 true,游戏将发送一个数据包,尝试导致玩家重新加载所有可见区块。如果关闭,可能会提供显著的性能提升,但如果结构或特性以非常奇怪的方式放置方块,这些方块可能直到区块重新加载后才会显示。例如,minecraft:forest_rock 特性在不向客户端发送更改的情况下放置方块。大多数特性和结构都能正常工作,因此 sendchunklightingpacket 可以设置为 false。(默认为 false)
<randomseed> - 如果你想每次在任何地方运行命令时都保持生成相同的结构布局,请使用此参数并传入一个种子值。这对于测试是否修复了某个片段未在结构中生成的问题非常有用。
(仅限 1.20.4+) /fillstructurevoid <size>
<size> - 从你站立处向外扩展的球体大小。球体内的空气将被结构虚空(structure void)替换。它是通过递归扩散来实现的,因此不会替换房屋或封闭空间内部的空气。这是一种快速且粗糙地用结构虚空填充房屋外部的好方法。建议与 Structure Void Toggle 模组配合使用效果最佳。
(仅限 1.18) spawnrawstructure <location> <configuredstructure> <savestructurebounds> <sendchunklightingpacket> <randomseed>
<location> - 结构的生成位置。可以使用 ~ ~ ~ 进行生成。注意:ConfigureStructures 可能会忽略此参数的 Y 值,请知悉。例如,海洋纪念碑总是生成在海平面以下。
<configuredstructure> - 要生成的 ConfiguredStructure。请注意,许多结构具有特殊的硬编码内部检查,可能会阻止生成。例如,末地城如果在指定位置低于 60 则不会生成,沙漠神殿和丛林神庙如果在海平面或以下也不会生成,其他结构可能有更严格的检查。生物群系检查已被绕过,并且对于许多原版结构,我添加了代码来绕过它们许多严格的检查,以便在执行此命令时矿洞总是生成。模组结构可能有极其严格的检查以防止生成。此参数是必需的参数。此参数之后的其余参数均为可选。
<savestructurebounds> - 是否将结构的边界保存到区块本身。此边界用于触发成就、随时间生成特定于结构的生物(如守卫者和掠夺者)以及各种其他与边界相关的事物。
<sendchunklightingpacket> - 如果为 true,游戏将发送一个数据包,尝试导致玩家重新加载所有可见区块。如果关闭,可能会提供显著的性能提升,但如果结构或特性以非常奇怪的方式放置方块,这些方块可能直到区块重新加载后才会显示。例如,minecraft:forest_rock 特性在不向客户端发送更改的情况下放置方块。大多数特性和结构都能正常工作,因此 sendchunklightingpacket 可以设置为 false。(默认为 true)
<randomseed> - 如果你想每次在任何地方运行命令时都保持生成相同的结构布局,请使用此参数并传入一个种子值。这对于测试是否修复了某个片段未在结构中生成的问题非常有用。
/spawnpieces <resourcelocationpath> <location> <savepieces> <floorblock> <fillerblock> <rowlength> <spacing (1.20.4+)>
<resourcelocationpath> - 用于搜索所有要在网格中生成的 NBT 片段的路径。此命令也可以针对单个 NBT 片段。这是唯一必需的参数。所有其他参数均为可选。
<location> - 开始放置片段的起始位置。~ ~ ~ 是默认值,即玩家站立的位置。
<savepieces> - 是否自动将生成的每个 NBT 片段保存到世界保存文件夹中的 "generated" 文件夹内。
<floorblock> - 放置在地面上供 NBT 片段所在的方块。通常是 Barrier(屏障)方块或 Stone(石头)。
<fillerblock> - 用于清除区域以容纳 NBT 片段的方块。此处常用的方块是 Air(空气)或 Structure Void(结构空位)。
<rowlength> - 在开始下一行之前,每行应放置多少个 NBT 片段。
<spacing> - 仅适用于 1.20.4 及更高版本。片段之间的间距。
(仅限 1.18) /spawnfeature <configuredfeatureresourcelocation> <location> <sendchunklightingpacket>
<configuredfeatureresourcelocation> - 要生成的 ConfiguredFeature 的资源位置。请注意,某些特性具有内部检查以确定某位置是否有效,例如 Desert Wells(沙漠水井)需要放置在沙子上。
<location> - 生成 ConfiguredFeature 的位置。
<sendchunklightingpacket> - 如果为 true,游戏将发送一个数据包,尝试让玩家重新加载所有可见的区块。如果关闭,可能会提供显著的性能提升,但如果结构或特性以非常奇怪的方式放置方块,这些方块可能直到区块重新加载后才会显示。例如,minecraft:forest_rock 特性在不向客户端发送更改的情况下放置方块。大多数特性和结构都可以正常工作,此时可以将 sendchunklightingpacket 设置为 false。(默认为 true)
(仅限 1.18) /spawnplacedfeature <placedfeatureresourcelocation> <location> <sendchunklightingpacket>
<placedfeatureresourcelocation> - 要生成的 PlacedFeature 的资源位置。请注意,某些 PlacedFeature 具有内部检查以确定某位置是否有效或进行稀有度放置。例如,Desert Wells(沙漠水井)的稀有度放置概率为 1/1000,因此你可能需要执行约 1000 次此命令,Desert Well 才会决定生成。
<location> - 生成 PlacedFeature 的位置。注意:为了更好地模拟世界生成,此处的位置会将该 PlacedFeature 所在区块的最底角位置传递给 PlacedFeature。因此,使用此命令就像正常的世界生成一样,只是跳过了生物群系检查。如果你的 PlacedFeature 有 "minecraft:biome" 放置检查,它将不起作用,这有助于在没有处于正确生物群系的情况下更轻松地进行调试。
<sendchunklightingpacket> - 如果为 true,游戏将发送一个数据包,尝试让玩家重新加载所有可见的区块。如果关闭,可能会提供显著的性能提升,但如果结构或特性以非常奇怪的方式放置方块,这些方块可能直到区块重新加载后才会显示。例如,minecraft:forest_rock 特性在不向客户端发送更改的情况下放置方块。大多数特性和结构都可以正常工作,此时可以将 sendchunklightingpacket 设置为 false。(默认为 true)
This utility mod for Neoforge, Forge, Fabric, and Quilt is great for any modder or datapacker that is looking to create custom jigsaw structures but wants a way to spawn the structures quickly or have all nbt pieces laid out neatly. It also provides a way to spawn configuredfeatures and placedfeatures to make debugging those easier.
What this mod does is it created the /spawnstructure, /spawnpieces, /spawnfeature/ and spawnplacedfeature command that you can use. The full args for the commands are:
/spawnstructure <location> <startpoolresourcelocation> <depth> <heightmapsnap> <legacyboundingboxrule> <disableprocessors> <sendchunklightingpacket> <randomseed>
<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 the only required argument. All other arguments 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.
<sendchunklightingpacket> - If true, the game will send a packet to try and cause players to reload all visible chunks. If off, it may provide significant performance boost but if the structure or feature places blocks in a very weird way, those blocks may not show up until the chunk is reloaded. Example, minecraft:forest_rock feature places blocks without sending changes to client. Most features and structures will be fine and sendchunklightingpacket can be set to false. (default is false)
<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.
(1.20.4+ only) /fillstructurevoid <size>
<size> - The size of the sphere outward from where you're standing. The air in the sphere will be replaced with structure void. It does so by recursively spreading out, so it won't replace air inside house or enclosed spaces. Good for filling outside of houses with structure void in a quick and dirty way. Used best with Structure Void Toggle mod.
(1.18 only) spawnrawstructure <location> <configuredstructure> <savestructurebounds> <sendchunklightingpacket> <randomseed>
<location> - Where to spawn the structure. Can do ~ ~ ~ to spawn it. Note: ConfigureStructures may ignore the y value of this argument so be aware of that. Ocean Monuments always spawn below sealevel for example.
<configuredstructure> - The ConfiguredStructure to spawn. Note, many structures have special hardcoded internal checks that may prevent generation. For example, End Cities will not spawn is land at spot is below 60, Desert Temple and Jungle temples will not spawn at or below sealevel, and other structures may have more strict checks. The biome checks has been bypassed and for many vanilla structures, I have added code to bypass many of their strict checks so that Mineshafts always spawn when doing this command for example. Modded structures may have extremely strict checks that prevent generation. This argument is a required argument. The rest of the arguments past this one are optional.
<savestructurebounds> - Whether to save the structure's boundaries to the chunk itself. This bounds is for triggering advancements, spawning structure specific mobs over time like guardians and pillagers, and various other bounds related stuff.
<sendchunklightingpacket> - If true, the game will send a packet to try and cause players to reload all visible chunks. If off, it may provide significant performance boost but if the structure or feature places blocks in a very weird way, those blocks may not show up until the chunk is reloaded. Example, minecraft:forest_rock feature places blocks without sending changes to client. Most features and structures will be fine and sendchunklightingpacket can be set to false. (default is true)
<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.
/spawnpieces <resourcelocationpath> <location> <savepieces> <floorblock> <fillerblock> <rowlength> <spacing (1.20.4+)>
<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.
<spacing> - Only in 1.20.4 and newer. How far apart the pieces should be.
(1.18 only) /spawnfeature <configuredfeatureresourcelocation> <location> <sendchunklightingpacket>
<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.
<sendchunklightingpacket> - If true, the game will send a packet to try and cause players to reload all visible chunks. If off, it may provide significant performance boost but if the structure or feature places blocks in a very weird way, those blocks may not show up until the chunk is reloaded. Example, minecraft:forest_rock feature places blocks without sending changes to client. Most features and structures will be fine and sendchunklightingpacket can be set to false. (default is true)
(1.18 only) /spawnplacedfeature <placedfeatureresourcelocation> <location> <sendchunklightingpacket>
<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.
<sendchunklightingpacket> - If true, the game will send a packet to try and cause players to reload all visible chunks. If off, it may provide significant performance boost but if the structure or feature places blocks in a very weird way, those blocks may not show up until the chunk is reloaded. Example, minecraft:forest_rock feature places blocks without sending changes to client. Most features and structures will be fine and sendchunklightingpacket can be set to false. (default is true)
评论 0
登录后参与评分
还没有评论,来抢沙发吧