![]() New tags are stored in datapacks under tags directory (same as old ones).Tags can now be defined for any registry (blocks, items, biomes, etc.The exploration_map loot table function no longer automatically sets the display name of the map.The exploration_map loot table function destination field is now a configured feature tag id.The feature field in location predicates now references a configured feature.Experimental datapacks can add new structure sets.The game now generates and stores data-driven configured structures. Noise router wires data-driven parts of the cave generation with the rest of the code.Noise settings got a new field noise_router (and lost a couple of flags), see worldgen/noise_settings folder in the worldgen report.A new registry was added for Density functions (caves are created by combining those together).pos: The position to use as the origin for the feature placement (if omitted, ~ ~ ~ is used).id: The namespaced id of a configured feature to place.New command that places a configured feature at a given location. Any type present in registries (blocks, items, biomes, etc.) can now have tags.A lot of the cave generation is now configurable through experimental datapacks.It is now possible to add custom structures in experimental datapacks.locate and locatebiome commands now support tags (prefix with # to distinguish from normal ids).For instance, you can now use /locate village_desert or /locate shipwreck_beached The locate command parameter is now a configured structure rather than a structure type. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |