#Custom Noise Settings causes custom biomes to not be detected via /locate command (1.21.7)

1 messages · Page 1 of 1 (latest)

ruby crag
#

I created a custom noise setting file for a custom dimension. The problem is that now my custom biomes can't be detected with the /locate command. I have no clue what's causing all of this. I will be posting my noise settings file and other necessary files if needed.

ruby crag
true crest
#

What did you set for the continents, temperature, and etc. dfs in the noise_settings noise_router?

ruby crag
#

Mostly 0, only 1 for vegetation

true crest
#

That's why

#

Those are what become the noise maps that the biome placement parameters use, so if there isn't enough diversity in those, then the parameters you set for your biomes won't exist

ruby crag
#

So, do I simply change it to different values?

true crest
#

No, you don't want them to be integers

ruby crag
#

Decimals then?

true crest
#

They need to be density functions that create noise maps or gradients of values, typically from -1 to 1

ruby crag
#

So what I did with the final density, then

#

It's not meant to be a singular value, is that what you are saying?

#

I'm relatively new to this so I was unaware those values had major importance

#

Alright I changed up the noise router values to be more diverse, while my biome "voidlands" and "voidforest" now do generate, it still can't find my biome "voidcaverns", which is meant to be an underground biome

#

I set the voidcaverns paramets in the void dim file to -1 because I want it to spawn underground

#

The "voidforest" trees still aren't spawning in oddly

ruby crag
#

Hello?

ruby crag
true crest
ruby crag
#

Never knew this guide existed

true crest
ruby crag
#

It isn’t

#

Oh

#

I see now

#

Depth, as in the “dimension” file?

#

Should I just try to avoid utilizing single values on all of those parameters?

true crest
#

No, the density function in your noise router

#

Single values for parameters are fine, though if you're making a complex, terrain-conforming biome source, list entries are inevitable

ruby crag
#

I’m referring to the dimension file

true crest
#

Ok

ruby crag
true crest
#

Does your depth density function produce -1 values in its range?

ruby crag
#

How can I check that?

true crest
#

And does the area that those values generate at correspond to what is considered underground in your world?

true crest
ruby crag
#

I have used the generator

true crest
#

Which you can use to see a 2D visual representation of the output

true crest
#

But of course, if you don't even know if it does, it's not out of the question that where your depth density function does generate -1 values, if it even does, that those may not correspond to low Y areas of the world, aka underground

#

So again, I do recommend reading the guide as it gives a rough idea of how these concepts mesh together

ruby crag
#

I’ll check it out, try your fix and then come back

ruby crag
#

Okay... I'm starting to understand what's happening..

#

The noise settings depth field is defining the depth for the void dimension file?

#

-1 is shown to be really high up, so I changed the value to be different

#

It appears to have fixed the caverns issue.. now the caverns only spawn where I want them to be. However features still aren't showing up

true crest
#

But it's probably just issues with your placements

ruby crag
#

Yeah I’ll check

ruby crag
#

Sorry for the radio silence, I decided to check my "configured_feature" and "placed_feature" to try and see if something is wrong. But nothing appears to be wrong at all

#

I also still don't know why caves wont appear in the void caverns biome, as the carvers have been defined correctly

#

but maybe im doing something wrong

true crest
#

Can you paste the contents directly in here? Currently just need the placed feature

#

And again also just need details as to in what way they aren't generating as expected

ruby crag
#

I think I'll be abandoning this for now. Maybe in the future I'll revisit it