Post

I don't find myself too limited, since I enjoy coming up with creative solutions with the available tools, but outside of what I'd consider the obvious (un-hardcoding legacy features to use block state providers and support other configuration), I have a small list of nice-to-haves

- A feature that can performantly apply a blockstate provider to an entire chunk - Allow Template features to use processors like Fossils do - More placement modifiers in general, particularly to test surroundings with greater accuracy and performance

- More control over jigsaw structure placement, including where they can start (underground surfaces) and where they can extend into (like Mineshafts) - Ability to define limited or guaranteed template pool entries (ala the End Portal in Strongholds) distinct from the starting structure

I'm curious on the first point - generally I would imagine that to be the role of surface rules, but maybe those are missing some capability too? For what kinds of use-cases are you missing that functionality? :)

I'm not a datapack developer, but I've been working on wyck.dev. I think the ability to define truly 'custom' placed features from a datapack might be nice. Even if it's from something as basic as `.nbt` file.

The ability to make it so mobs spawning is not controlled through biomes. Like for example: Wolves now spawn in plains BASED off its own entity_biome file, instead of me changing the actual plains biome code. It gets messy when using multiple biome overhaul packs. When I just want a mob in a biome.

I posted on the official Minecraft Discord about improvements to Data-Driven Dimensions and Biomes. - Biome Entry Data-Driven - Worldgen biome options for the End are now accessible - Biome features are now tagged objects instead of arrays of arrays discord.com/channels/113...

Check repo github.com/Hardel-DW/ex... - Extract mob spawns outside of biomes. The file is managed independently, much like the variant entities that control the spawn conditions. - Change the biome entry algorithm to reduce, for example, the desert from 354 rules to 32. (See the repo.)

Overall, more split data driven, and add new tags. - Currently, with datapacks, you can't remove a biome from the overworld or just modify a specific one. - When you add entities, it's a pain to have to add them to biomes in mods. - You can't access the End's world generation options

Individual terrain_adaptation settings for jigsaw pieces would be fantastic. Currently, either the whole structure gets buried or none of it does. It's very awkward for custom structures with large basements. (attached, an old variation of Myriad's mansion rework with this issue)

I'm mainly a datapack maker but i think having more control over the monster spawning in a biome would be nice. Something akin to SpawnPotentials in spawner blocks.

That's a great highlight! ☺️ Do I understand correct that you mean control in terms of what is being placed (e.g. equipment/variant/other entity data) as opposed to the "when/where"? (though of course there's room to improve there too)

Not actually a problem in the system itself but how vanilla uses it: If vanilla were to make use of the possibility to use named placed feature tags in biomes, that would make it much easier for data packs to add custom features to vanilla biomes (without having to override the biome itself)

The bandlands material rule is at the moment hard coded and the only ways to get bands, other than those specific terracotta ones from the badlands, is with very hacky ways I also wish we had some form to check xz coordinates for density functions

not really DIRECTLY worldgen, but sometimes i just want to change the sky/water/grass colors of a biome.. or the cosmetic environmental attributes... without a datapack? perhaps it would be nice if the cosmetic stuff was moved to resource packs. so i can make uh.. blue savannas??? resource pack??

though, i'd hope that could someday come alongside the ability for datapacks to include a forced resourcepack, because right now having to tell the player 'hey download this resource pack and enable it manually please' on top of a datapack that say, adds custom item models. is mildly inconvenient